Google Analytics Attribution Windows: How to Choose the Right Fit

Your campaigns may not be underperforming. Your attribution window may simply be cutting off conversions before your customers finish deciding.

Google Analytics now gives you much finer control over that cutoff. The useful question isn’t whether you should choose a longer window. It’s which window reflects the conversion you’re measuring, the interaction you’re crediting, and the decision you need the report to support.

What an attribution window actually changes

An attribution window, also called a lookback window, defines how long an advertising interaction remains eligible to receive credit for a later conversion. If the conversion occurs after the selected window closes, that interaction no longer qualifies for credit under that setting.

The window changes attribution eligibility. It doesn’t create or remove the customer’s action, accelerate the buying process, or prove that an ad caused the conversion. That distinction matters whenever a settings change makes campaign results appear better or worse.

Don’t confuse the window with the attribution model. The window determines which interactions are recent enough to qualify. The model determines how credit is handled among eligible interactions. A model can only work with the interactions admitted by the window.

A longer window keeps delayed conversions eligible for longer. That can increase the number of conversions associated with advertising interactions, especially when buyers take time to research, compare, seek approval, or return later. A shorter window applies a stricter recency standard, but it can exclude advertising interactions that genuinely began the decision process.

Neither direction is automatically more accurate. A long window can sweep distant interactions into the report even when their practical influence is uncertain. A short window can make longer consideration journeys disappear from campaign reporting. Your job is to choose the cutoff that makes the report useful for a defined decision.

Choose the window from the conversion backward

Start with the event being counted, not the platform’s maximum setting. A form submission, account registration, purchase, and completed contract represent different points in a customer journey. Their normal delays from ad interaction can be very different.

Define the event before estimating its delay

If Google Analytics records a lead form as the conversion, select a window for the time between the advertising interaction and that form submission. Don’t silently base it on the later time required to close the sale. Conversely, if the recorded conversion is an imported final outcome, the relevant delay extends to that final outcome.

Write a one-sentence definition for every conversion you optimize toward: what happened, when it is recorded, and what business decision it informs. This prevents teams from debating window length while referring to different endpoints.

Use observed decision lag, not a convenient preset

Look for the elapsed time between relevant ad interactions and the conversion event. Use the evidence available in your analytics paths, ecommerce records, lead timestamps, or customer system. You are looking for the ordinary shape of the delay: whether conversions cluster soon after interaction, continue arriving gradually, or commonly require a longer decision period.

Then choose the shortest window that still represents the normal journey you intend to measure. This is a decision rule, not a universal benchmark. It keeps the setting tied to customer behavior while limiting credit from interactions so old that their relevance becomes difficult to defend.

When evidence is thin, don’t hide the uncertainty behind the maximum available value. Pick a defensible starting point, document why you chose it, and treat the setting as a measurement assumption to validate.

Decide separately for clicks and engaged views

Click-through and engaged-view conversions begin from different types of advertising interaction, so they shouldn’t inherit the same window without examination. Ask what each interaction represents in your campaign and how long it can reasonably remain relevant to the measured action.

• For click-through conversions, examine the delay from an ad click to the defined conversion event.
• For engaged-view conversions, examine the delay from the qualifying view engagement to the same event.
• If the two paths show different timing, use different windows. Symmetry is not a measurement goal.
• If stakeholders disagree, make the assumption explicit rather than blending the two interaction types into one unexplained rule.

Configure the custom windows without defaulting to the maximum

Google Analytics now accepts any whole-number lookback value within the supported range. That removes the need to force your buying cycle into a small menu of presets.

In Google Analytics, go to Advertising > Conversion management > Settings. The controls are also available through the conversion management interface in linked Google Ads. Because both surfaces can be involved in campaign measurement, review the active values where your team actually manages conversions rather than assuming everyone is looking at the same configuration.

1. Inventory the conversions used in reporting, bidding, or budget decisions.
2. Define the exact customer action represented by each conversion.
3. Review the observed delay for click-through and engaged-view interactions separately.
4. Select a whole-day value within the applicable range.
5. Record the previous value, the new value, the change date, the evidence used, and the owner of the decision.
6. Check dashboards, recurring reports, and campaign reviews that may be affected by the new eligibility cutoff.

Resist setting click-through to 90 days and engaged-view to 30 days merely because those values capture the most possible credit. Maximum inclusion isn’t the same as accurate attribution. The right value is the one you can explain in terms of the conversion event and the customer’s normal decision time.

Evaluate the change without mistaking attribution for growth

A window change can move reported campaign performance even when customer demand and campaign execution haven’t changed. Treat the configuration change as a break in measurement continuity.

Annotate the effective date in your reporting workflow. When comparing periods, disclose whether both periods used the same window. If they did not, a difference in attributed conversions may reflect the eligibility rule rather than a change in campaign quality.

Recent conversion cohorts also need time to mature. The longer the selected window, the longer an interaction can remain eligible for a delayed conversion. A click tracked under a 90-day window can continue receiving eligible conversion credit for far longer than one tracked under a short window. Don’t judge the newest cohort as complete while that opportunity remains open.

Use a controlled review process:

• Keep a record of the configuration change so analysts can distinguish it from campaign edits.
• Compare the observed conversion-delay pattern with the window you selected. Conversions accumulating near the cutoff deserve scrutiny because the setting may be truncating a meaningful part of the journey.
• Inspect click-through and engaged-view results independently before combining them in a campaign conclusion.
• Ask whether any apparent gain comes from more customer actions or simply from allowing older interactions to qualify.
• Revisit the choice when the conversion definition, buying process, campaign format, or reporting objective changes.

The strongest internal test is explainability. A stakeholder should be able to ask, “Why does this interaction still deserve credit?” and receive an answer grounded in the conversion event and observed journey, not in a desire to preserve reported return.

Key takeaways

• An attribution window controls how long an ad interaction remains eligible for conversion credit; it does not prove causation.
• Choose the window for the conversion event actually recorded, not for a later business outcome that Analytics isn’t measuring as that conversion.
• Google Analytics supports custom click-through windows from 1 to 90 days and custom engaged-view windows from 1 to 30 days.
• Clicks and engaged views represent different interaction paths, so evaluate their timing separately.
• Document every window change because it can alter reported attribution without any underlying change in customer behavior.
• Use the shortest defensible window that captures the normal decision journey, then validate it against observed conversion delay.

Before your next campaign review, list the conversion actions that influence spend and write down the active window beside each one. Any value your team can’t connect to a defined event and an observed decision lag is the first setting to revisit.

References

• Search Engine Land — Google Analytics adds custom conversion attribution windows