You open the Google Ads dashboard and it says 40 conversions this month. You check your call log or your booking system and count 22 actual customers. Same campaign, same month, two different numbers. One of them is wrong, and figuring out which one is wrong determines whether you keep spending or pull the plug.
The gap almost never means Google is lying to you. More often, an account setting is counting something other than what you think it's counting. A single form gets submitted twice because the confirmation page was slow to load, and Google counts that as two leads instead of one. A phone call and a form fill from the same customer both get logged as separate conversions. The tag meant to fire once on a thank-you page fires every time someone lands on the page, including people who never converted.
That doesn't mean your ads aren't working. It means the number on the dashboard isn't the number you think it is, and until you know why, you can't trust it to make budget decisions.
The settings to check
Inside every Google Ads conversion action there's a counting rule that decides whether one customer can generate multiple conversions.
Google gives you two options: "One" to count only one conversion per ad click, or "Every" to count all conversions. For lead generation, you almost always want "One" because counting every form submission inflates your numbers when someone submits more than once.
Someone picks this setting during setup, and then rarely revisits it.
If someone submits the same contact form three times because they weren't sure it went through, that's still one lead. If the form is set to "Every," Google counts all three submissions as separate conversions, which inflates the lead count and makes cost-per-lead look artificially low. It slips by because the dashboard just shows a number, and a lower cost-per-lead looks like good news, not a red flag.
There are legitimate cases for "Every." An online store where each purchase is real revenue should use it. A booking form where one person schedules appointments for themselves and two family members might genuinely represent three conversions. The point isn't that one setting is always right, it's that whichever one you have was probably chosen once, and someone should double check that it's still accurate.
Phone calls and form fills often run on different clocks
If your campaign tracks both phone calls and web form submissions as separate conversion actions, each one can have its own attribution window. That window controls how long after someone clicks your ad Google will still credit a conversion to that click.
If one conversion action has a 90-day window and another has a 30-day window, a conversion on day 60 gets attributed for one action but not the other. Now you can't accurately compare how phone calls are performing versus form submissions because they're operating on different attribution rules.
If you're comparing "which ad group brings in calls versus forms," the comparison is broken before you even look at the results. Lining up both actions to the same window is a five-minute fix and it removes an entire category of confusion.
The tag firing more often than it should
A conversion tag meant to trigger only on a "thank you" or confirmation page sometimes gets set to trigger on all pages instead, usually from a rushed setup or a plugin installed on top of an existing tracking code.
A conversion trigger set to "All Pages" fires your conversion tag on every page load — product pages, homepages, blog posts — not just your thank-you page. That creates phantom conversions that vastly overstate performance.
Check this directly in the account, under the conversions section, by looking for a conversion count that's higher than your total number of actual sales or leads for the same period. If the tag is firing on every page, the fix is scoping it back down to the confirmation step where a real conversion actually happens.
Cookie restrictions and cross-device gaps
Even a perfectly configured account will undercount some real conversions, because browser privacy changes have made it harder for Google to connect a click to what happens afterward.
When someone blocks cookies, declines a consent prompt, or switches from their phone to their laptop between clicking the ad and filling out a form, Google can't directly observe the conversion. It happened, but Google doesn't know it happened.
Cookie restrictions and cross-device gaps usually push dashboard numbers lower than reality, which is the opposite direction of the counting and duplicate-tag problems above. That's why a single "fix this one thing" answer doesn't exist: the same account can be overcounting in one place and undercounting in another at the same time.
A smaller factor: clicks that were never a real customer
Lunio's 2026 Global Invalid Traffic Report found that 8.51% of all paid traffic is invalid, meaning almost one in every 12 paid clicks does not come from a real person who could become a customer.
Google's own systems filter a large share of obviously invalid clicks before they ever hit your bill, and search campaigns targeting a specific local service tend to see less of this than broad display or app placements. Invalid traffic is real, but for most small, locally-targeted campaigns it's a smaller piece of the mismatch than a counting setting or a duplicate tag.
How to actually check which number is real
Pull your actual customer count for the last 30 days from the place you actually use: your call log, your booking calendar, or your CRM. Compare that number directly to the Ads dashboard for the same window and same conversion actions.
If the two numbers are close, you probably have a performance problem, not a tracking problem, and the next step is improving the ads or the offer. If Ads is reporting a number noticeably higher than your real customer count, work through the counting setting first, then check for a tag firing on the wrong pages. If Ads is reporting noticeably lower than your real count, look at attribution windows and whether cookie or cross-device gaps are hiding conversions that did happen.
The number matters because every bidding decision the platform makes downstream is based on it. A campaign "optimizing" toward inflated or miscounted conversions is optimizing toward the wrong target, no matter how good the ad copy or targeting is underneath it.
Key Takeaways
- A gap between Google Ads' reported conversions and your actual customer count almost always traces to a tracking setting, not to whether the ads themselves are working.
- The most common cause is a conversion action set to count "Every" submission instead of "One" per customer, which inflates lead counts and makes cost-per-lead look artificially low.
- Phone call and form conversions running on different attribution windows will produce numbers that can't be honestly compared to each other.
- A conversion tag set to fire on every page instead of just the confirmation page creates phantom conversions that overstate real performance.
- Compare your real customer count from your call log or CRM to the Ads dashboard for the same 30-day period before making any budget decision based on the reported number.
If your ad numbers and actual customer count don't agree, the fix usually lives inside the account settings, not the campaign strategy. Get that right before spending another dollar on it. Mindstate Strategy manages paid ad campaigns with tracking built to match real business outcomes, not just dashboard totals, so reach out through our contact page to have your account checked.
