Why GA4 and Google Ads Conversion Numbers Never Agree
Three weeks ago I was on a call with a DTC e-commerce brand spending EUR 22,000 per month on Google Ads. Their head of growth pulled up two tabs. GA4 showed 214 purchase key events attributed to Google paid search for May. Google Ads reported 297 conversions for the same campaigns in the same period. An 83-conversion gap -- 39 percent. "Which number do I trust?" she asked. "Neither," I said. "Not until we understand what each one is actually counting."
This is one of the most common problems I diagnose. A client opens GA4 and Google Ads side by side, sees two different conversion numbers, and loses confidence in both. The instinct is to assume one platform is wrong. The reality is that they are designed to count differently. Once you understand where the discrepancy comes from, you can decide which number to trust for which decision -- and close the gap where it matters.
The Seven Reasons for GA4 Google Ads Conversion Discrepancies
The mismatch is not a bug. It is the predictable result of two platforms using different attribution models, counting methods, reporting dates, and data-collection mechanisms. Here are the specific causes, ordered by how often I see them drive the gap.
1. Attribution model differences
Google Ads defaults to data-driven attribution across touchpoints within the Google Ads ecosystem. If a user clicks your Search ad, then two weeks later clicks a Shopping ad and converts, Google Ads may assign fractional credit to both clicks.
GA4 also uses data-driven attribution by default, but evaluates across all traffic sources -- organic, direct, email, social, and paid. The same conversion that Google Ads fully attributes to a paid click may be credited to organic search or direct in GA4 if GA4's model determines that another touchpoint deserves more weight.
The result: Google Ads almost always reports more conversions attributed to paid campaigns than GA4 does.
2. Conversion counting method
Google Ads lets you choose between counting "every" conversion or "one" conversion per click. For e-commerce, "every" is standard -- if someone buys twice after one click, both purchases count.
GA4 counts events. If the event fires twice, it records two key events. But GA4 attributes those events using its own model, which may assign the second purchase to a different source. The event count matches, but the attributed-to-Google-Ads count does not.
3. Conversion window mismatch
Google Ads defaults to a 30-day click-through and 1-day view-through conversion window. GA4's default lookback window is 90 days for the first user touchpoint and 30 days for subsequent key events, but it does not have a view-through window at all.
This means Google Ads counts view-through conversions -- someone saw your Display or YouTube ad, did not click, but converted within 24 hours. GA4 never sees these because there was no click or session to attribute. In the accounts I have audited, this single difference has accounted for 15-25 percent of the gap.
4. Reporting date: conversion date vs click date
Google Ads reports conversions on the date of the original click. GA4 reports them on the date the conversion event occurred.
If someone clicks your ad on May 28 and converts on June 3, Google Ads attributes the conversion to May 28. GA4 attributes it to June 3. When you compare monthly reports, any conversion that straddles the month boundary shows up in different months in each platform. This is a timing difference, not a data loss -- but it inflates apparent discrepancies in any single-month view.
5. Consent and cookie gaps
This is the cause I see underestimated the most. Each platform relies on different tagging mechanisms and is affected differently by consent denial and cookie expiration.
When a user declines cookies and you run Consent Mode v2 in Advanced mode, both platforms receive cookieless pings and apply behavioral modeling to estimate conversions. But the models are independent. Google Ads uses its own conversion modeling, and GA4 uses a separate behavioral model. They will not produce the same number.
On top of that, Safari's ITP caps JavaScript-written first-party cookies at seven days. If the GA4 cookie expires before a user converts but the GCLID is still recoverable via enhanced conversions, Google Ads may record the conversion while GA4 misses it entirely.
6. Tag firing and implementation errors
Sometimes the gap is not architectural -- it is a plain mistake. Common implementation issues I find during audits:
- The GA4 tag fires on the conversion page but the Google Ads conversion tag does not (or vice versa).
- A duplicate Google Ads conversion tag inflates counts. GTM preview mode shows the tag firing twice -- once from a hardcoded gtag.js and once from GTM.
- The GA4
purchaseevent is missing thetransaction_idparameter, so Google cannot deduplicate repeat fires. Meanwhile the Google Ads tag has a transaction ID and deduplicates correctly.
If you suspect implementation issues but cannot isolate them, that is exactly the kind of problem I help clients diagnose.
7. Google Ads imports from GA4 versus native tags
Some advertisers import GA4 key events into Google Ads as conversion actions instead of using native Google Ads conversion tags. This adds another layer of discrepancy. Imported conversions inherit GA4's attribution, counting, and consent modeling. They will not match what a native Google Ads tag would have reported.
Google's own documentation notes that imported conversions may differ from GA4 reports due to data freshness -- GA4 data can lag 24-48 hours, and Google Ads may snapshot the import at a different point.
How to Diagnose the Gap in Your Account
Before fixing anything, quantify where the GA4 Google Ads conversion gap comes from. Here is the process I use.
Step 1: Align the comparison
Compare the same conversion action, same date range, same attribution scope. In Google Ads, filter by the specific conversion action. In GA4, filter by the corresponding key event. Use the conversion-time reporting toggle in Google Ads (Segment > Conversions > Conversion time) so both platforms report on the date the conversion happened, not the click date.
Step 2: Isolate view-through conversions
In Google Ads, segment by Conversions > Conversion type to separate click-through from view-through. Remove view-throughs from the comparison. GA4 does not track them, so including them guarantees a mismatch.
Step 3: Check modeled conversions
In Google Ads, look at the "Conversions (by conv. time)" column alongside "All conversions." The delta includes modeled conversions from Consent Mode. In GA4, check Admin > Reporting Identity -- if set to "Blended," GA4 is applying its own modeling. Compare modeled volumes.
Step 4: Audit the tags
Open Tag Assistant and walk through your conversion flow. Confirm that both the GA4 event tag and the Google Ads conversion tag fire exactly once on the same trigger. Check transaction IDs are present in both. For a full walkthrough of what to check, use the GA4 tracking audit checklist.
Step 5: Compare against your source of truth
Pull the same period's conversions from your CRM, payment processor, or backend. This is the number that matters. If your CRM shows 250 purchases and Google Ads shows 297, you know Google Ads is overcounting (likely view-throughs or duplicate tags). If GA4 shows 214, you know GA4 is undercounting (likely consent or cookie loss).
How to Reduce the Discrepancy
You will never get the two platforms to show the exact same number -- the attribution models are fundamentally different. In the accounts I have worked on, these changes typically close the gap from 30-40 percent to under 10 percent.
Align conversion windows
Set the Google Ads click-through conversion window to match your GA4 key event lookback window. For most businesses, 30 days for both is reasonable. If your sales cycle is longer, extend both. Reduce or disable the view-through window on Google Ads if you do not run Display or YouTube campaigns -- it is inflating the count with conversions GA4 will never see.
Fix implementation gaps
Ensure both tags fire on the same trigger with the same transaction ID. If you are using GTM, a single data-layer purchase event should trigger both the GA4 event tag and the Google Ads conversion tag. The Google Ads conversion tracking guide walks through the correct GTM setup.
Enable enhanced conversions
Enhanced conversions send hashed first-party data (email, phone) alongside the conversion tag. This recovers conversions lost to cookie expiration on Safari and cross-device journeys. When both GA4 and Google Ads have access to the same enhanced conversion data, the overlap in what they can measure increases -- and the gap shrinks.
Use native Google Ads tags, not GA4 imports
For bidding, use native Google Ads conversion tags rather than importing GA4 key events. Native tags use Google Ads attribution, benefit from Google Ads conversion modeling, and give Smart Bidding the most complete signal. Use GA4 for cross-channel analysis and Google Ads data for bid optimization. Trying to make one platform do both jobs is how the confusion starts.
Implement server-side tracking
Server-side tracking routes both GA4 and Google Ads requests through your own infrastructure. This extends cookie lifetimes past Safari's seven-day cap, bypasses ad blockers that suppress client-side tags, and gives you a single point of control to verify that both platforms receive the same events. In my experience it is the single most effective technical change for reducing the GA4 Google Ads conversion discrepancy.
Which Number Should You Trust?
Neither platform is "right." They measure different things.
| Decision | Use this source |
|---|---|
| Google Ads bid optimization | Google Ads conversion data (native tags) |
| Cross-channel budget allocation | GA4 key events (data-driven, all sources) |
| Actual business performance | Your CRM or backend (source of truth) |
The mistake I see most often is using GA4 to evaluate Google Ads campaign performance. GA4 redistributes credit across all channels. A campaign that Google Ads correctly attributes 50 conversions to might show 30 in GA4 because GA4 gave partial credit to organic and email touchpoints. If you cut the campaign budget based on the GA4 number, you are making a decision on the wrong dataset.
The reverse mistake also happens. Using Google Ads data to set overall marketing budgets ignores non-paid channels. GA4 is the right tool for the cross-channel view. And for board-level reporting -- revenue, customer counts, unit economics -- use your CRM or payment processor. They do not depend on cookies, consent banners, or attribution models.
FAQ
Why does Google Ads show more conversions than GA4?
Google Ads typically reports more conversions because it uses a different attribution model scoped only to Google Ads clicks, includes view-through conversions that GA4 cannot track, reports conversions on the click date rather than the conversion date, and applies its own conversion modeling for consent gaps. Each of these factors inflates the Google Ads number relative to GA4.
Should I import GA4 conversions into Google Ads or use native tags?
Use native Google Ads conversion tags for bidding and optimization. Imported GA4 key events inherit GA4 attribution and counting logic, which gives Smart Bidding a less complete signal. Use GA4 for cross-channel analysis and Google Ads native tags for campaign optimization. Running both in parallel gives you the most accurate picture.
What is a normal discrepancy between GA4 and Google Ads?
A gap of 5 to 15 percent between GA4 and Google Ads conversion counts is typical and usually explained by attribution model and reporting date differences. If the discrepancy exceeds 20 percent, there is likely an implementation issue such as missing tags, duplicate firing, consent misconfiguration, or conversion window misalignment that is worth investigating.
Does Consent Mode affect GA4 and Google Ads differently?
Yes. Both platforms apply conversion modeling when consent is denied, but they use independent models. Google Ads conversion modeling and GA4 behavioral modeling will produce different estimates for the same non-consented traffic. This is a structural source of discrepancy that cannot be fully eliminated, only minimized by ensuring both platforms receive the same underlying data.
Can server-side tracking eliminate the GA4 and Google Ads conversion gap?
Server-side tracking significantly reduces the gap by ensuring both platforms receive the same events from the same server, with extended cookie lifetimes and ad-blocker resilience. It does not eliminate the gap entirely because the attribution models remain different. But it removes the technical causes of discrepancy such as cookie loss, tag blocking, and inconsistent tag firing.
Not sure which of your conversion numbers to trust -- or why the gap keeps growing? Get in touch -- I will audit your GA4 and Google Ads setup and tell you exactly what is causing the discrepancy and how to fix it.