Why Google Ads reports more conversions than you have leads
By Ahmed Imran · Updated August 2026 · 8 min read
If your Google Ads dashboard reports far more conversions than your office can find real enquiries for, the gap is not a reporting quirk you can ignore. Smart Bidding is being trained on that gap, and it will keep buying more of whatever is inflating it.
The gap is the whole problem
This is the single most common thing I find when I take over an account. The dashboard says the campaigns produced 70 conversions last month. The owner asks the front desk how many real enquiries came in and the answer is 19.
Most people treat that as a reporting annoyance. It is not. Google's automated bidding spends your money chasing whatever you defined as a conversion. If 51 of those 70 were something that never becomes a customer, you have spent a month paying the algorithm to find you more of them, and it has been very good at it.
The four things usually inflating the count
Phone taps counted as leads
A tap on a click to call button is a conversion by default in most accounts. It is not a lead. Somebody can tap, hear a ring, change their mind and hang up in four seconds. Unless you are counting calls that lasted long enough to be a conversation, usually 30 to 60 seconds, you are counting intent to dial rather than a conversation.
Direction clicks counted as leads
A click for driving directions tells you somebody wanted your address. For a retail shop that means something. For a contractor who drives to the customer, it means almost nothing, and it is usually the cheapest conversion in the account, which is exactly why bidding gravitates to it.
Every micro action set to primary
Newsletter signups, PDF downloads, a click on the pricing page. These are useful to watch. They should sit in the secondary column, where you can see them without bidding optimising toward them. If everything is primary, nothing is.
The same lead counted more than once
A visitor who fills the form and then calls to check you got it produces two conversions from one enquiry. Set the counting method to one per click for lead generation actions, not every, and this stops.
The tracking problems nobody checks
The count can also be wrong in the other direction, where real leads never reach the report at all. These take about an hour to check and they are usually the reason your numbers never quite tie out.
- ›A caching or speed plugin configured to delay JavaScript until the visitor interacts with the page. That includes every tracking tag, so anyone who called straight from the ad without scrolling is never attributed. I found exactly this on one account where roughly half of all leads arrived with no campaign identity attached.
- ›More than one tag manager container loading on the same page, left behind by a previous vendor, while the container the client actually owns was never installed.
- ›Call tracking that swaps the number after the tracking script has already read the page, so the click identity is lost in the middle.
- ›Consent banners that block tags until accepted, with no consent mode configured, so a meaningful share of conversions silently disappear.
How to fix it, in the right order
| Step | What you do | Why it comes here |
|---|---|---|
| 1 | Agree what a lead is, in writing, with the person who answers the phone | Everything downstream depends on this definition |
| 2 | Demote every action that is not that definition to secondary | Stops bidding chasing the cheap stuff immediately |
| 3 | Set call conversions to a minimum duration, usually 30 to 60 seconds | Separates conversations from taps |
| 4 | Set lead actions to count one per click | Removes double counting |
| 5 | Verify tags actually fire, on a real device, without interacting first | Catches caching and consent problems |
| 6 | Feed the outcome back in, marking each lead qualified or not | Bidding starts optimising toward customers |
Fixing the definition of a conversion costs nothing and changes everything downstream of it. Do it before you touch a single budget.
What it looked like when I did this
On a foundation repair account this year, the fix was exactly this sequence. Phone taps and direction clicks came out of the bidding signal, the call tracking platform became the single source of truth, and the client's own sales team started marking every lead quotable or not.
The reported conversion count went down. Quoted work went from $93,078 to $312,390 in the following six weeks, cost per quotable lead fell 34 percent, and the share of leads worth quoting went from 40 percent to 69 percent. Nothing about the market changed. The account just stopped lying to the algorithm.
How to tell if this is you
Ask the person who answers your phone how many real enquiries came in last month. Then open Google Ads and look at the conversion count for the same period. If the two numbers are within about 15 percent of each other, your tracking is broadly honest. If the dashboard is double the reality, your bidding has been training on noise, and that is fixable this week.
Almost always because the account counts actions that are not enquiries. Phone taps with no minimum duration, driving direction clicks, newsletter signups and page views set as primary conversions all inflate the number. Double counting from a visitor who both submits a form and calls is the other common cause.
Yes, but only calls that lasted long enough to be a real conversation. Set a minimum duration, usually 30 to 60 seconds depending on your trade. A tap that never connects is not a lead and should not be teaching your bidding what to buy.
Primary conversions are what Smart Bidding optimises toward. Secondary conversions are recorded and visible in reporting but do not influence bidding. Anything you want to watch but do not want the algorithm chasing belongs in secondary.
The reported figure usually does, because you stopped counting things that were never leads. That is the point. What should also happen is that revenue per dollar of spend improves, because the budget moves toward the searches that produce real enquiries.
Load your site on a real phone, do not scroll or tap anything first, then trigger a conversion and watch whether the tag fires. Caching plugins that delay JavaScript until interaction are a common culprit and they will not show up in any Google Ads report, because the report only knows about what reached it.
Want this run on your account?
Book a call. I look at your account live and tell you what I would change first.