Attribution data discrepancies
Attribution data discrepancies are the routine mismatches between conversion numbers reported by different tools — an ad platform versus site analytics, or two analytics products. They arise from different attribution models, lookback and reporting windows, time zones, deduplication rules, bot filtering, and consent handling. Most discrepancies are structural and expected, so the goal is to explain them, not eliminate them.
What this means
No two attribution tools count conversions identically. An ad platform credits within its own walled garden on its own windows and dates conversions to the ad interaction; site analytics credits by channel grouping on the conversion date with a different model. Add time-zone offsets, deduplication differences, bot filtering, and consent-driven modeling, and the totals will diverge by design.
The first instinct — that a discrepancy means something is broken — is usually wrong. Most gaps are the predictable result of definitional differences between systems measuring related but distinct things.
How to reconcile
Work through the usual suspects systematically: are the tools using the same attribution model and lookback window; the same time zone; the same conversion definition; the same deduplication of pixel and server events; the same bot filtering; and the same consent treatment of unconsented traffic. Each difference accounts for part of the gap.
After accounting for those, a residual, stable gap is normal and can be documented rather than chased. What deserves investigation is a sudden change in the gap, which can indicate a genuine tagging regression, a broken event, or a consent-banner change. Google's documentation notes that platform and analytics conversion counts are expected to differ; the discipline is to explain the structural part and monitor for the anomalous part.
- Models, windows, time zones, and dedup all shift totals
- Stable structural gaps are expected and can be documented
- A sudden change in the gap signals a real issue to fix
How it appears in analytics and logs
A persistent gap between tools usually maps to a definitional difference (model/window/zone/dedup), not data loss; a sudden new gap may signal a real instrumentation issue.
Diagnostic use case
Diagnose why two tools report different conversions by checking model, window, time zone, dedup, and consent differences before assuming a tracking bug.
What WebmasterID can help detect
WebmasterID provides a clean, first-party, bot-filtered conversion baseline you can use as a reference point when explaining cross-tool discrepancies.
Common mistakes
- Assuming any cross-tool gap is a tracking bug.
- Comparing tools without aligning model, window, and time zone.
- Ignoring a sudden change in an otherwise stable discrepancy.
Privacy and accuracy notes
Reconciling discrepancies compares aggregate counts and definitions, not individual identities. This page is educational, not legal advice.
Related pages
- Duplicate conversion counting
Duplicate conversion counting happens when a single real conversion is recorded more than once — for example by both a browser pixel and a server event, by a tag firing twice, or by two platforms each claiming it. It silently inflates reported conversions and value, distorts ROAS, and misleads bidding unless deduplication via shared event IDs and clear ownership is in place.
- Attribution window vs reporting window
The attribution (lookback) window decides which past touches can earn credit for a conversion; the reporting window is the date range you are viewing. They answer different questions, and confusing them is a frequent cause of numbers that 'do not add up' between tools or between dates.
- Walled-garden attribution and its self-reporting
Walled gardens are closed ad platforms that measure and report the conversions they claim credit for, inside their own systems. Each marks its own homework with its own window and rules, so summed across platforms the attributed conversions routinely exceed the real total — double-counting is structural, not accidental.
- Attribution analytics
A first-party baseline for reconciling cross-tool gaps.
Sources and verification notes
- Google Analytics Help — Why analytics and ad platform numbers differDocuments structural reasons conversion counts differ between tools.
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.