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.
What this means
The attribution window (lookback) is how far back the tool searches for touches eligible to share credit for a conversion. The reporting window is simply the date range of the report you are reading. One governs credit eligibility; the other governs which conversions appear on screen.
Where the confusion bites
Tools also differ on whether a conversion is dated to the conversion event or back-dated to the touch that earned credit. A conversion that happens today from a touch 20 days ago may appear in today's report in one tool and in the touch-date report in another.
When two systems disagree, align lookback length and the date-attribution rule before assuming a tracking fault.
- Attribution window: which past touches can earn credit
- Reporting window: which dates you are viewing
- Conversion-date vs touch-date dating differs by tool
How it appears in analytics and logs
If conversion totals differ between tools, check whether one credits a conversion to the touch date and another to the conversion date, and whether lookback windows match.
Diagnostic use case
Distinguish the two windows when reconciling reports: a mismatch in either can explain discrepancies before you suspect a data bug.
What WebmasterID can help detect
WebmasterID keeps both windows explicit, so reconciliation issues surface as configuration differences rather than as mysterious data gaps.
Common mistakes
- Confusing the lookback window with the report date range.
- Ignoring conversion-date vs touch-date dating differences.
- Reconciling tools without aligning both windows first.
Privacy and accuracy notes
Both windows operate on one site's own first-party events over time and need no cross-site identity. This page is educational, not legal advice.
Related pages
- Lookback and conversion windows explained
A lookback (or conversion) window is the period before a conversion in which earlier touchpoints are eligible for credit. Touches outside the window are ignored entirely. Because every attribution model only sees touches inside this window, its length quietly governs which channels can ever receive credit.
- Data-driven attribution: promise and caveats
Data-driven attribution (DDA) assigns credit using a model trained on a site's own conversion paths rather than a fixed rule like last-click. Done well it credits assist touches more fairly. Its caveats are real: it needs enough conversion volume, it is a model not a measurement, and it cannot see touches that were never tracked.
- Analytics sampling: when reports estimate
Sampling is when an analytics tool computes a report from a fraction of the data and extrapolates. It keeps big queries fast, but it adds estimation error — worst for small segments and rare events, where a few sampled sessions get scaled into a confident-looking number. Knowing when a report is sampled is the first defence.
- Attribution analytics
Both windows made explicit for reconciliation.
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.