Glossary

Lookback Window

Updated on Jul 22, 2026

Learn what a lookback window is in attribution, how it changes conversion reporting, and why teams should document it before comparing results.

Key Takeaway

A lookback window defines how far before a conversion an earlier interaction can receive attribution credit.
Changing the window can change reported performance even when campaign activity has not changed.
A lookback window is an attribution setting, not a universal measure of customer loyalty or data retention.

What Is a Lookback Window?

A lookback window is the period before a conversion or key event during which an earlier marketing interaction can be eligible for attribution credit. It is a measurement rule: it determines which touchpoints can be considered, not whether an interaction caused the result.

For example, Google Analytics explains that a 30-day key-event lookback window can credit only touchpoints that occurred during the 30 days before the event. Platform settings and available options vary, so the configured value should always accompany a report.

How a Lookback Window Works

An analytics system receives a conversion, examines its eligible historical interactions, and applies an attribution model such as first-touch attribution or last-click attribution. The lookback window limits the history that model can use.

Changing the window can change channel, campaign, and revenue reports without any change in the underlying user behavior. It can also apply only going forward, depending on the platform. Comparisons should therefore state the platform, conversion definition, attribution model, window, time zone, and reporting date range.

Why It Matters for Mobile Operations

Mobile app and web reporting often involve delayed actions: a user may discover a campaign, install an app later, and complete an approved key event after several sessions. A documented lookback window helps a team avoid comparing incompatible reports across a mobile automation campaign workflow or product surface.

The setting does not justify collecting extra personal data or inferring a user's identity. Use approved analytics configuration, minimize data exposure, and respect applicable consent and platform requirements.

Risks and Best Practices

Choose a window that matches the actual decision cycle being measured, then keep it stable long enough to compare results. Mark reporting changes in a change log, and do not present a shift in attributed credit as proof that a channel suddenly became more effective.

Avoid confusing the lookback window with session timeout, customer retention, audience membership, or raw data retention. These are separate settings with different operational and privacy implications.

MoiMobi Perspective

MoiMobi treats the lookback window as measurement governance. Teams should be able to reproduce a result by knowing the event definition, allowed touchpoints, selected model, and configured history window.

Bottom Line

A lookback window limits which earlier touchpoints can receive conversion credit. Document it with the attribution model so reporting changes are understood rather than mistaken for operational improvement.

How MoiMobi Fits

MoiMobi explains the lookback window as a measurement rule that operations teams should document before comparing campaign or workflow results.

Sources

FAQ

What is a lookback window in attribution?

It is the period before a conversion during which an eligible touchpoint can receive credit under the selected measurement rules.

Why does the lookback window matter?

A shorter or longer window changes which earlier interactions are considered, so conversion and channel reporting can change.

Is a lookback window the same as a session timeout?

No. A session timeout determines when an interaction session ends, while a lookback window determines which earlier touchpoints can be credited for a conversion.