If the conversion count in your Google Ads account is higher than the number of real orders sitting in your shop or CRM, the most common cause is the same purchase being counted more than once, usually because the confirmation or thank-you page fires your conversion tag again on a reload, a back-button visit, or a bookmark, or because you have two separate tracking setups (for example a native Google Ads tag and a GA4 import) both reporting the same purchase as a conversion. The fix in almost every case is to add a unique transaction ID to your conversion tag so Google Ads can recognize and discard the repeat, and to make sure you are not double-reporting the same event from two sources.
This is one of the more frustrating problems to diagnose because nothing looks broken. The tag fires, the conversion shows up in Google Ads, and the numbers in your reports look healthy, right up until you compare them against your actual order count and realize you are “converting” more customers than you have orders. Here is how to find the cause and fix it properly.
Before chasing tag code, pull your real order count for a specific date range from your store, booking system, or CRM and compare it to the conversion count in Google Ads for the matching conversion action over the same range. Check this at the conversion action level (Goals and conversions, then look at each action individually) rather than the account total, since a wildly inflated single action is a strong signal of duplication rather than genuinely strong performance.
It is also worth checking whether the inflated number is showing in Conversions or in All conversions. All conversions includes cross-device and view-through activity and is expected to run higher than Conversions, so a gap between those two columns is normal and not evidence of a bug.
Most ecommerce and lead-gen sites fire the conversion tag directly on the thank-you or order-confirmation page. That page gets revisited far more often than people assume: a customer hits refresh, uses the back button after checking their inbox, reopens a saved tab, or a confirmation email link gets clicked twice. Every one of those reloads can fire the tag again and report a second conversion for an order that only happened once.
The fix Google recommends is to attach a transaction ID to the conversion tag. If two conversions come through for the same conversion action with the same transaction ID, Google Ads flags the second one as a duplicate and does not count it. If you are tracking through Google Tag Manager, the setup looks like this:
purchase) to the data layer with a unique transaction_id generated for that specific order.transaction_id to pull that value through.A few things will quietly break this and are worth checking directly: a static placeholder value like 1234 or thank_you instead of a real order number, an unresolved template string still showing as {{ order_number }}, or a value that leaks personal information such as an email address or phone number, which Google Ads will also reject. If you see transaction IDs prefixed with GG_ in your diagnostics, that means your own tag never supplied an ID at all, so treat it as blank and go fix the data layer rather than assuming the feature is doing its job.
Transaction IDs are not shown anywhere in your Google Ads reporting, so you cannot audit duplicates by eye in the interface. You have to verify the setup in GTM Preview mode or in your analytics tool, not in Google Ads itself.
If your transaction ID setup is clean and duplicates are still showing up, check whether you are running more than one conversion source for the same action. A common pattern is importing conversions from GA4 into Google Ads as a conversion action, while also running a native Google Ads purchase tag directly on the site through GTM. Both of these can report the exact same order as a separate conversion, because they are two independent tracking paths pointed at the same customer action.
The fix here is organizational rather than technical: pick one source of truth per conversion goal. Either import that goal from GA4, or track it with a dedicated Google Ads tag, not both. If you need both GA4 and Google Ads reporting for internal purposes, that is fine, but only one of them should be feeding the Google Ads conversion action that your bidding actually optimizes against.
Not every inflated number is a tracking error. Check the Count setting on the conversion action, found in the action’s settings alongside the category and value fields. If it is set to count every conversion rather than one per click, a single customer who goes through checkout, abandons, and completes the purchase again shortly after can legitimately generate two recorded conversions for one ad click, which is expected behavior for some lead-gen setups but usually wrong for ecommerce purchases.
Also rule out cross-domain tracking issues if checkout happens on a different domain or subdomain than the rest of your site (a hosted checkout provider, for instance). A broken cross-domain linker can sometimes cause a session to be treated as two separate visits that each trigger their own conversion event.
Start by confirming the gap is real at the conversion-action level, then check for a missing or broken transaction ID on your confirmation page tag, since reloads and revisits of that page are the single biggest cause of duplicate conversions. If that is clean, look for a second tracking source, usually a GA4 import running alongside a native tag, feeding the same conversion action. Fixing either of these brings your reported conversions back in line with what actually happened, which matters because Smart Bidding is optimizing against whatever number you hand it. Inflated conversions do not just look wrong in a report, they actively mislead your bidding strategy into chasing a result that is partly fictional.