Why Is Google Ads Counting More Conversions Than I'm Getting?

Your Google Ads Conversions column says it was a good month, but your CRM or your order list says otherwise. Smart Bidding never sees that second count. It spends against the bigger one, and every phantom conversion teaches it to buy more of the same traffic.
When Google Ads is counting too many conversions, the cause is nearly always configuration. Two conversion actions may be recording the same outcome, a lead action may be set to count every conversion rather than one, or a tag may fire before a sale or form is actually complete. Modeled conversions and click-date reporting widen the gap further, but those differences are about credit and timing, not duplicates.
Are two actions counting the same conversion?
The Conversions column is the total of your primary conversion actions, and nothing else. Google's conversion reporting documentation notes that most conversion actions are included in account-default goals unless you change that. If two actions describe the same real-world event and both are primary, both get counted, and both feed bidding.
The usual pattern is layering, not a broken tag. A native Google Ads tag sits on the thank-you page, and then someone imports a GA4 key event for the same form submission. On e-commerce accounts, it is often a platform's auto-created purchase action running alongside one somebody added by hand. Each action looks correct in isolation. Together, they count every sale twice. Since the tag itself works, Tag Assistant will not catch it.
To check, open Goals, filter to primary actions, and write down the real-world event each one records. Any two lines with the same answer are a duplicate. Keep the action closest to the actual outcome. For sales, that is usually the native tag carrying a transaction ID. For leads, it is whichever fires only on a confirmed submission. Then demote the other one. It keeps reporting but stops steering bids. This is exactly the job of the difference between primary and secondary conversions, and it is the cleanest fix available.
Is a lead action set to count every one?
Every conversion action has a count setting: Every or One. Google's guidance is to use Every for sales so each purchase is tracked, and One for leads to prevent duplicate counts from page refreshes. Lead accounts that leave this on Every inflate quietly. Each of these adds another conversion from a single person:
- A prospect submits the form twice because the confirmation was slow.
- Someone reloads the thank-you page.
- A visitor returns to the thank-you page from browser history.
None of these is a new lead.
For sales, Every is correct, because each checkout is revenue. It is only safe when a transaction ID travels with the conversion. Google's Tag Manager documentation is explicit: to avoid duplicate conversions, pass a transaction ID from your site into a data layer variable. With an ID attached, a reloaded order confirmation page is recognized as the same order rather than a second sale.
The third cause is a tag firing on the wrong event. A conversion tag on an All Pages trigger, or on a confirmation URL people can revisit, fires repeatedly. Some events look like outcomes but are not:
- A click on a phone number, with no call made.
- A form opened but never submitted.
- A purchase event that fires when the checkout page loads, before payment clears.
Each of these turns intent into a reported conversion. The fix is to trigger on the confirmed event, not on the page that precedes it.
Which gaps are not actually duplicates?
Some of the difference between Google Ads and your own records is not an error, and "fixing" it can make your data worse.
Modeled conversions. The Conversions column may include modeled conversions where Google cannot observe every one, for example when consent or browser restrictions block the tag. Your CRM will never contain these. They are an estimate of real activity, not a phantom.
Click-date reporting. Google Ads books a conversion against the day of the ad click. Your CRM records the day the lead arrived. A click on the 28th that converts on the 3rd lands in different months in each system. Compare a single week and the gap can look alarming, even though both systems hold the same events.
Last-clicked-ad credit. Google Ads credits the last ad clicked, not the last channel touched. Someone who clicks your ad, returns days later through organic search, and converts can still count as a Google Ads conversion within your conversion window. GA4, or your CRM's source field, may credit organic instead. Neither system is wrong. They answer different questions.
Conversions that are not leads. Spam, job applications, vendor pitches, and repeat enquiries all complete a form, so all of them count as conversions. Your CRM filters them out. This gap is about lead quality rather than tracking. Matching these records one to one is the wider job of reconciling Google Ads leads against your CRM.
How do you find which cause is yours?
Work through the checks in order. Each one rules out a cause before you change anything.
- Remove timing from the comparison. Compare a full month, using Google Ads' conversions-by-conversion-time view, against your CRM by creation date. If the gap mostly closes, the cause was timing and nothing is broken.
- Count primary actions per outcome. If any real-world event has more than one primary action behind it, you have found a duplicate. That is usually the largest single contributor.
- Check count settings. Lead actions should be set to One. Sales actions should be set to Every and carry a transaction ID.
- Check where each action fires. Open the action and review the pages it has recorded conversions on. Any page other than the true confirmation step means the tag is firing too early or too often.
Make the fixes as a single batch, not one a day. Google's documentation currently warns that frequent changes to conversion goals reset the standard 7–14 day learning period. Several small corrections spread across a fortnight keep the bid strategy permanently relearning.
Expect your reported cost per conversion to rise afterwards. That is not a performance drop. It is the first accurate number the account has shown in a while.
Conclusion
A Conversions column that outruns reality is almost always telling you about your setup, not your traffic. Duplicate primary actions, a lead action counting every submission, and tags firing on intent rather than completion account for most of the inflation. Modeled conversions, click-date reporting, and last-clicked-ad credit explain the remainder, and should be understood rather than removed. Fix the configuration once, in one batch, and bidding starts optimizing toward outcomes you can actually find in your CRM.
Companion answers questions grounded in your Google Ads spend and your HubSpot or Shopify records together, so you can set a conversion count against what actually arrived.
Frequently Asked Questions
All conversions is a broader column than Conversions. Google's documentation directs advertisers there for secondary conversion actions and view-through conversions, which credit people who saw an ad without clicking it. Those actions are reported but not used for bidding. A large gap between the two columns is expected and is not, by itself, a sign of duplicate counting.
Neither, for whether a conversion really happened. Your CRM or order system records the business outcome. Google Ads records what its bidding acts on, and GA4 applies its own attribution. Use Google Ads to understand what Smart Bidding sees, and your own records to judge whether those conversions turned into leads or revenue.
Yes. Once duplicates stop counting, the same spend divides across fewer conversions, so reported cost per conversion rises. Nothing about performance has changed, only the accuracy of the number. If you run a target CPA strategy, review the target at the same time. A target set against inflated counts is now unrealistically tight and can throttle delivery.
Get a complimentary audit to uncover AI opportunities hidden in your data.
Put these strategies to work


