You open Google Ads and see thousands of conversions recorded over the last 30 days. You open your CRM and see a handful. Your backend order system shows a fraction of what Google is claiming. This isn't a glitch — it's one of the most common, most misunderstood gaps in PPC measurement, and if you don't diagnose it correctly, you'll make bidding decisions based on fiction. After managing over $350M in Google Ads spend, I can tell you this discrepancy destroys more accounts than bad targeting ever will.
Before you panic or assume Google is lying to you, it helps to understand why this gap exists in the first place. Google Ads and your CRM are measuring fundamentally different things, using different attribution models, different identity resolution methods, and different definitions of what counts as a "conversion."
Google's conversion tracking fires based on signals — a thank-you page load, a tag trigger, a phone call duration threshold, an imported offline conversion. Your CRM records verified business outcomes — a signed contract, a fulfilled order, a qualified lead that passed a sales review. These two systems will almost never match exactly, but when Google shows 3,000 conversions and your CRM shows 40, something has gone seriously wrong.
As practitioners often discuss in the r/googleads community, the root causes tend to fall into a handful of repeatable categories. Let's walk through each one systematically.
This is the single most common cause of inflated conversion counts I see when auditing accounts. It happens when multiple conversion actions are firing for the same user event. A classic example: you have a Google tag firing on your thank-you page, and a Google Analytics 4 goal imported into Google Ads, and a manual conversion action set up from an older campaign — all three counting the same purchase.
Check your "Conversion actions" settings and look at how many are marked as "Primary" and included in your "Conversions" column. If you have 4–6 primary conversion actions and only one of them represents your true business outcome, you may be multiplying your reported conversions by 4–6x before any other issues come into play.
View-through conversions (VTCs) are counted when a user sees your display or YouTube ad but does NOT click it, then converts later through another channel. By default, Google includes these in many reporting views, and the default lookback window is 1 day for most formats.
However, if you're running broad reach campaigns, your VTC numbers can be enormous. A user who saw your banner ad while reading the news and then directly Googled your brand name and bought — Google claims that. So does your organic channel. So does direct. This is triple-counting at scale.
Your conversion tag may be firing multiple times per session. This happens when:
A quick diagnostic: compare your total conversions to your total transactions in GA4. If Google Ads shows 500 conversions but GA4 shows 100 purchase events, the tag is firing more than once per transaction on average. Use Google Tag Assistant to record a real conversion and count how many times the conversion tag fires in a single session.
Data-driven attribution (DDA) — now the default for most accounts — uses machine learning to assign fractional credit across touchpoints. Unlike last-click, it can distribute partial credit to impression-only touchpoints, early-funnel keywords, and branded terms that were "assistive."
The result: the sum of all attributed conversions across your Google Ads account will almost always exceed the actual number of unique converting users. This is by design. The question is whether the model is working correctly or whether it's dramatically overclaiming due to model miscalibration, especially in lower-volume accounts.
DDA requires a minimum of 300 conversions within 30 days to function reliably. Below that threshold, the model is essentially guessing, and it tends to err on the side of attributing more credit to Google-touchpointed paths.
A user clicks your ad on their phone during lunch, then completes the purchase on their laptop that evening. Google, if the user is logged into their Google account on both devices, can connect this journey and record a conversion against the original click. Your CRM, relying on cookies, may see this as two separate anonymous sessions with one conversion — or it may only attribute the desktop session where the purchase happened.
This is actually a good thing Google is doing — cross-device tracking is real user behavior. But if your CRM is purely cookie-based and has no identity resolution, the two systems will diverge significantly, especially on mobile-heavy traffic where conversion rates appear low in the CRM because the purchase happens on a different device.
Don't try to fix what you haven't measured. Here's a structured audit process I use when an account has a significant conversion discrepancy:
A common question in the r/googleads community is how to improve the accuracy of conversion tracking without sacrificing the scale that Google's machine learning needs. This is where Enhanced Conversions become essential.
Enhanced Conversions work by collecting hashed, first-party user data (email address, phone number, home address) from your conversion page and sending it to Google alongside the standard conversion ping. Google then matches this hashed data against its signed-in user database to confirm the conversion was a real, unique user — and to fill in cross-device gaps where cookies fail.
The practical impact I've seen in accounts after properly implementing Enhanced Conversions:
To implement Enhanced Conversions correctly:
No tracking system will ever achieve perfect parity with your CRM. The goal is a defensible, consistent measurement framework where you understand the variance and can explain it. Here's how I structure this for accounts I manage:
| Metric | Source of Truth | Expected Variance vs. Google Ads | Action if Variance Exceeds |
|---|---|---|---|
| Total Purchases | Backend database / Shopify / CRM | ±15–25% | Audit tag firing, check duplicate actions |
| Qualified Leads | CRM with lead scoring applied | ±20–40% | Add offline conversion imports for qualified leads |
| Revenue (ROAS) | Accounting system / MER (Media Efficiency Ratio) | ±30–50% | Use MER as primary efficiency signal, ROAS as directional |
| Phone Call Conversions | Call tracking platform (CallRail, etc.) | ±10–20% | Ensure call duration threshold is set to qualified call length |
The Media Efficiency Ratio (MER) — total revenue divided by total ad spend — is the blunt instrument that cuts through all attribution noise. When your Google Ads ROAS looks fantastic but your MER is flat, Google is overclaiming its contribution. MER doesn't care which channel gets credit. It just asks: for every dollar we spent across all channels, how many dollars came back?
Most conversion discrepancy issues are self-inflicted tracking problems that you can resolve in your own account. But there are cases where escalating makes sense:
When contacting support, come prepared with: a screenshot of your conversion actions list, a Tag Assistant recording showing the tag firing, and a comparison of Google Ads conversions vs. backend transactions for a specific 7-day window. Specific data forces a specific investigation rather than generic troubleshooting scripts.
If you've read this far and recognize your account in one of these scenarios, here's your priority order for the next two weeks:
The practitioners who build predictable, scalable Google Ads accounts aren't the ones with the most sophisticated bidding strategies — they're the ones who've done the unglamorous work of making their measurement trustworthy. Fix the foundation, and everything built on top of it gets better automatically.