Conversion tracking "gaslights" you when tags fire multiple times, duplicate actions count the same event twice, or browser-side cookies miss cross-device journeys. The fix is a systematic audit: inventory every conversion action, verify tag firing with GTM Preview, reconcile Google Ads against your CRM, then layer Enhanced Conversions and server-side tagging to recover what cookies miss.
Conversion tracking breaks most often because of how and where the tag fires, not because the platform is malfunctioning. [1] Google Ads records a conversion every time the designated event is received — so if that event fires three times for one transaction, three conversions are logged. The original r/PPC thread that inspired this page is a textbook example: conversions in the platform, silence in the CRM, and no obvious reason why.
The most common root causes, ranked by how often they appear in audits:
/thank-you URL fires again every time that URL is reloaded — by the user hitting back, sharing the link, or your own QA visits.purchase event three times in one session sends three conversions to Google Ads.Audit before you change anything — blind edits can take you from inaccurate data to no data. The audit has three steps.
Open Google Ads → Tools & Settings → Conversions. For every action, document:
You will almost always find zombie conversion actions — tags left behind by a previous agency, test events never deleted, or the same event imported from both GA4 and a hardcoded tag simultaneously. Archive or delete anything you cannot explain. For a systematic approach, the 250-point Google Ads audit engine flags duplicate and misconfigured conversion actions automatically.
Use GTM's Preview mode to walk through your own conversion funnel and watch which tags fire and when. [2] Pair it with the Tag Assistant Companion Chrome extension. Flag any tag that:
Build a simple reconciliation table covering the same date range across all data sources. Acceptable variance ranges from practitioner experience:
| Data source | Expected vs. Google Ads | Acceptable variance |
|---|---|---|
| GA4 (same event) | Slightly lower (better deduplication) | 5–15% lower |
| CRM / backend database | Lower (last-touch or assisted only) | 15–35% lower |
| Payment processor | Ground truth for revenue | Within 2–5% of CRM |
| Call tracking platform | Matches call conversion count | <10% variance |
If Google Ads shows 2–3× more conversions than your CRM, you have a counting problem. If it shows 50% fewer, you have a tracking gap. Both are serious; they just need different fixes. If you want a faster diagnostic, the marketing analytics auditor compares platform data against GA4 and surfaces variance automatically.
Browser-side tracking is structurally losing 20–40% of conversions to ad blockers, ITP, and cross-device journeys — and that share is higher if your audience skews toward Apple-ecosystem or privacy-conscious users. Two complementary layers address this.
Server-side tagging moves tracking logic from the user's browser to your server or a cloud function, then sends confirmed, first-party data directly to Google. [6] Key advantages:
purchase event fires only after your database confirms payment — not on button clickTools that automate this setup (mapping sign-ups, add-to-cart, and purchase events to GA4, Google Ads, and Meta simultaneously) eliminate the need for custom engineering on each integration. If you are spending more than $20K/month on paid media, the ROI on proper server-side infrastructure is almost always positive within 60 days.
Enhanced Conversions hashes user-provided data (email, phone, name) from your confirmation page and sends it alongside the standard conversion ping. [7] Google matches that hashed data against logged-in Google accounts to recover conversions that cookies missed. In accounts where Enhanced Conversions has been implemented, reported conversions typically increase 10–25% — not because more conversions are happening, but because previously invisible ones are now recovered. This matters most for B2B and longer sales cycles.
For more on closing measurement gaps, see how to make conversion tracking more accurate.
Even with perfect tracking, Google Ads conversion counts will never match your CRM one-to-one — and attribution is a major reason why. [8] Understanding the difference prevents unnecessary panic.
Google Ads attributes conversions to the ad click that occurred within the attribution window. Your CRM might use last touch, first touch, or a linear model. Your finance team counts the day the transaction closed. None of these is wrong; they measure different things.
Google Ads defaults to data-driven attribution (DDA) for accounts with sufficient conversion volume. [8] DDA distributes credit across all touchpoints in the conversion path, which means:
When a client asks why numbers "changed" after switching attribution models, the totals are identical but the per-campaign breakdown has shifted. Branded keywords lose credit; upper-funnel campaigns gain it. This looks like a tracking problem; it is the model working correctly.
Default Google Ads conversion windows are 30 days for click-through and one day for view-through. For B2B SaaS or high-consideration purchases with 60–90 day cycles, a large share of conversions falls outside the window and goes unreported. Extending the click-through window to 60 or 90 days is appropriate when the sales cycle warrants it — but expect an initial backfill of historical conversions when you make the change. If you are unsure how window length affects your numbers, see how delayed conversion tracking is in Google Ads.
Bad conversion data does not just distort reports — it actively poisons Smart Bidding strategies, because the algorithm optimizes toward whatever signal you give it.
Only Primary conversion actions influence Smart Bidding. Set up your actions intentionally:
This lets you observe micro-conversion behavior for funnel insights without letting low-intent signals dilute your bidding signal.
Using a flat conversion value across transactions with varying margins destroys Smart Bidding efficiency. Conversion value rules let you adjust reported values by device, location, or audience segment — for example, weighting new customers differently from returning ones. Accounts using Target ROAS (the target set inside Maximize conversion value) with differentiated values consistently outperform those using flat values in categories where margin varies by product.
To understand how conversion tracking directly influences auction participation and campaign delivery, see whether tracking conversions affects how Google shows your ads.
The goal is not to get every platform to agree on one number — that is not realistic. The goal is a measurement hierarchy so you know which number to use for which decision.
| Layer | Use for | Do not use for |
|---|---|---|
| Google Ads / platform reporting | In-platform optimization decisions | Executive reporting, revenue reconciliation |
| GA4 | Cross-channel path analysis, funnel diagnostics, audience insights [9] | Revenue source of truth |
| CRM / backend database | Source of truth: closed deals, paid transactions, qualified leads | Real-time bidding signal |
When reporting to stakeholders, lead with CRM data and contextualize with platform data. This prevents the inevitable "but Google says 200 leads" conversation when the sales team received 80 qualified ones.
Compare your Google Ads conversion count against your CRM for the same date range. If Google Ads shows 2× or more conversions than your CRM, double-counting is the likely cause. Confirm it by running GTM Preview mode through a test conversion and checking whether the conversion tag fires more than once in a single session.
Removing a Primary conversion action will cause Smart Bidding to recalibrate, which can temporarily destabilize performance. The safer approach is to change the duplicate from Primary to Secondary first, monitor for two to four weeks to confirm bidding is stable, then archive or remove the action. Never delete an action that is currently the sole bidding signal for an active campaign.
No. Enhanced Conversions hashes user-provided data from the browser and sends it alongside a standard conversion ping so Google can match it to a logged-in account — recovering gaps caused by cross-device or cookie loss. Server-side tagging moves the entire tracking call off the browser and onto your server, eliminating ad blocker and ITP exposure entirely. They are complementary, not interchangeable.
Attribution models redistribute credit across touchpoints in the conversion path — they do not create or remove conversions. [8] Moving from Last Click to Data-Driven Attribution typically moves credit away from branded and bottom-of-funnel campaigns toward upper-funnel campaigns that initiated journeys. Total account conversions remain the same; the per-campaign split changes significantly.
Google recommends at least 30 conversions in 30 days before adding a Target CPA to a Maximize conversions campaign. Below that threshold the algorithm lacks enough signal and produces erratic spend patterns. If you are below 30 monthly conversions, run Maximize conversions without a target until volume builds, then introduce the target incrementally.
Not necessarily. GA4 and Google Ads measure conversions differently: GA4 counts all event instances in a session, while Google Ads attributes conversions to ad clicks within your attribution window. A 5–15% lower count in GA4 (which deduplicates better) versus Google Ads is within normal range. If GA4 is significantly higher than Google Ads, that is more unusual and worth investigating for attribution window or tag configuration issues.
More answers in this topic: Tracking & Measurement