Why is a GA4 vs Google Ads conversion discrepancy normal?
A GA4 vs Google Ads conversion discrepancy is when the two panels show different conversion counts for the same period, and it's expected. The reason is simple: GA4 looks at the user's whole journey (cross-channel, data-driven attribution), while Google Ads decides inside the ad (usually last-click/ad-based). Because the two systems use different attribution models and counting methods, the numbers not matching is normal.
Analysts consider a 20-30% gap normal. What matters isn't forcing the two numbers to match, but understanding where the gap comes from. The numbers here are illustrative; the real gap varies by account and region.
Where do conversions vanish? The measurement funnel
Between the ad click and the conversion measured in GA4, data shrinks at each step: some sessions never land, some deny consent (cookieless), some never fire the tag. What remains is what GA4 can directly measure; the rest is estimated by modeling.
The 4 main sources of the gap
- Attribution model. Google Ads gives credit to the ad interaction; GA4's data-driven model splits credit across channels. The same conversion can land on a different campaign in each panel.
- Counting and timing. Google Ads counts on click date, GA4 on conversion date. Google Ads can also count "one per click" or "every conversion." This alone can be 5-20%.
- Attribution window. If the Google Ads click-through window and the GA4 lookback window aren't aligned, the same conversion lands in a different time bucket. Typical contribution: 5-15%.
- Consent Mode v2 + modeling. In regions where consent is denied, GA4 fills what it can't directly measure with modeling, creating up to 20-40% undercounting and panel-dependent results.
How much of a gap is normal?
Practical rule: a 20-30% gap is healthy, and above 50% almost always points to a configuration issue, most often Consent Mode v2 not deployed correctly or a tagging error.
Let it read and explain the gap for you
Ads Sensor unifies GA4 and Google Ads in one panel and shows the reason for the discrepancy.
Attribution window: how the gap grows over time
Most conversions don't happen at click time; they arrive days later. Google Ads back-dates them to the click date, while GA4 counts them on the day they happened. As windows lengthen, these delayed conversions accumulate and the gap grows. Best practice: align the Google Ads click-through window with the GA4 lookback window, even matched windows leave the models different, but the gap narrows noticeably.
The 2026 change: Consent Mode v2 + DDA recalibration
The April 2026 GA4 update changed two things: the data-driven attribution (DDA) model was recalibrated (compare pre/post-update periods and you'll see a difference), and Consent Mode v2 became a hard requirement for GA4 data to flow accurately into Google Ads in the EEA/UK. It also introduced stricter behavioral modeling thresholds globally.
Stop chasing numbers: the right approach
- Align the attribution windows (Google Ads click-through ↔ GA4 lookback).
- Deploy Consent Mode v2 and enhanced conversions correctly; verify tag firing.
- Use each platform for its purpose: Google Ads for ad optimization, GA4 for cross-channel analysis.
- Decide from a blended revenue/ROAS view; don't treat any single panel's number as absolute truth.
How Ads Sensor handles conversion discrepancy
Resolving the gap by hand on every account is slow and tiring. Ads Sensor unifies Meta Ads, Google Ads and GA4 data in a single panel; it places the platforms' reported conversions/revenue next to GA4's cross-channel view, produces a blended ROAS and explains the reason for the discrepancy (attribution window, counting, consent) with its rationale. With an approve-and-apply flow you can apply window/tagging recommendations and track the before/after impact. Open the panel to see the gap on your own account. The numbers are illustrative; real values vary by account.
Make sense of the GA4 vs Google Ads gap
Three sources in one panel; blended ROAS and a reasoned explanation of the discrepancy.