Ads vs analytics discrepancies
It is normal for Google Ads and GA4 to report different conversion and click numbers for the same campaign. They use different attribution models, count conversions at different times (Ads at click time, GA4 at conversion time), define a click versus a session differently, and apply different windows and de-duplication. This page enumerates the documented reasons the two tools diverge.
Why they diverge
Google Ads credits a conversion to the click that drove it and reports it on the click's date; GA4 credits conversions per its own attribution model and reports them on the conversion date. Ads counts clicks (which can include invalid-click filtering and multiple clicks per session); GA4 counts sessions and users. They also apply different conversion windows and de-duplication rules.
Linking Ads and GA4 helps align some figures, but exact parity is not expected even when configured correctly.
What to reconcile
Compare like with like: the same attribution model, the same date basis (click date vs conversion date), and the same conversion definitions. Confirm the accounts are linked, auto-tagging is on so `gclid` is captured, and the conversion windows match before treating a difference as an error.
- Ads reports on click date; GA4 on conversion date
- Different attribution models and conversion windows
- Clicks (Ads) vs sessions/users (GA4)
- Confirm auto-tagging and account linking first
How it appears in analytics and logs
A gap between Ads and GA4 conversions usually reflects model, timing, and counting differences — expected behavior — not a tracking failure, unless the gap is extreme or sudden.
Diagnostic use case
Explain to stakeholders why Ads and analytics conversion counts differ without assuming one is broken, and reconcile within each tool's defined model.
What WebmasterID can help detect
WebmasterID gives a first-party view of campaign-driven conversions you can compare against ad-platform figures to understand where the two diverge.
Common mistakes
- Expecting Ads and GA4 conversions to match exactly.
- Comparing different attribution models or date bases.
- Forgetting auto-tagging so gclid is never captured.
Privacy and accuracy notes
Conversion modeling fills gaps left by consent and cookie loss; modeled figures are estimates, not observed individuals. This page is educational, not legal advice.
Related pages
- Why two analytics tools disagree
It is normal for two analytics tools to report different numbers for the same site. The differences are structural, not bugs: each tool defines a session differently, filters bots differently, samples or does not, attributes on different windows, and fires its tag at a different moment. This page explains the recurring causes and how to reconcile them.
- Data import errors in GA4
GA4 data import merges external files (cost data, item metadata, offline events, user attributes) with collected data by matching on a key. When the key, the column names, the date format, or the schema do not match exactly, rows fail to import or join to nothing — leaving partial or absent enriched data with no obvious error in reports. This page covers the join model and its failure points.
- Last-click attribution: simple, and what it hides
Last-click attribution assigns 100% of a conversion's credit to the last touchpoint before it. It is simple, deterministic, and the historical default — which is exactly why it misleads: it ignores every earlier touch that created demand, systematically overrating bottom-funnel channels and underrating discovery.
- Attribution Analytics
Compare ad-platform and first-party conversions.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.