Attribution window mismatch across tools
Attribution look-back windows define how far back a tool searches for the touchpoints that earn conversion credit. When two tools use different window lengths or models, the same conversion is credited differently — or to a touchpoint one tool can see and the other cannot. This page explains how attribution-window mismatches across tools produce diverging conversion and channel numbers, and how to compare fairly.
What the look-back window does
An attribution model assigns conversion credit among the touchpoints in a visitor's path, and the look-back window bounds how far back the model looks. A touchpoint older than the window earns no credit; a longer window can pull in earlier touchpoints a shorter one ignores. Tools ship different default windows for clicks and for engaged views.
Two tools on different windows therefore see different candidate touchpoints for the same conversion, so they credit it differently.
- The window bounds how far back credit can reach
- Touchpoints older than the window get no credit
- Default click/view windows differ between tools
Comparing tools fairly
Before treating a gap as a fault, confirm both tools use the same attribution model and the same look-back window; a data-driven model in one and last-click in another will disagree by design. Where you can configure the window, align them, and compare over a period that fully contains the longest window so no conversion is half-counted at the edge.
This window is distinct from the session and campaign timeouts; check all three when reconciling.
How it appears in analytics and logs
Two tools crediting a conversion to different channels, or counting different conversion totals, often reflects different look-back windows or models, not an error.
Diagnostic use case
Reconcile diverging conversion or channel credit between tools by aligning attribution-window length and model before comparing.
What WebmasterID can help detect
WebmasterID retains first-party touchpoint timing, so you can reason about credit under a window you control rather than accepting each tool's default.
Common mistakes
- Comparing conversion credit across tools on different windows.
- Mixing a data-driven model with last-click and expecting a match.
- Confusing the look-back window with session or campaign timeouts.
Privacy and accuracy notes
Attribution windows operate on touchpoint timing, not identity. This page is educational, not legal advice; respect the consent that governs touchpoint data.
Related pages
- GA4 vs Google Ads conversion gaps
GA4 and Google Ads frequently report different conversion numbers for the same campaigns. The causes are structural: Ads credits conversions to the click date and can count multiple per click, while GA4 attributes on its own model and counts on the conversion date. Add different attribution windows, modelling, and de-duplication and the totals diverge. This page explains the differences and how to compare them sensibly.
- Campaign timeout window effects
A campaign or acquisition timeout controls how long the source that brought a visitor keeps getting credit for their later sessions. When that window expires before the visitor returns, the next session is no longer attributed to the original source and often falls to Direct. Changing the window moves attribution between channels. This page explains the campaign timeout and its effect on source reports.
- 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
Reason about credit under a window you control.
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.