Google Analytics has added a small feature with a large reporting consequence. Search Engine Land reported on August 14 that advertisers can now set custom conversion windows for click-through and engaged-view attribution. Google’s own Analytics release note, dated August 11, says conversions now support custom integer lookback windows for click-through conversions and engaged-view conversions.
The useful question is not whether every account should change its settings. The useful question is who is allowed to change the attribution window, why the change reflects the buying cycle, and how the team will explain any movement in CPA, ROAS or channel contribution after the switch. A conversion window is not only a technical setting. It is a budget narrative.
What changed in GA4
According to the Search Engine Land summary, engaged-view conversions can use a custom value from 1 to 30 days, replacing the old fixed 3-day window. Click-through conversions can use a custom value from 1 to 90 days, instead of only preset options such as 1, 7, 14, 30, 60 or 90 days. The settings are available in Google Analytics under Advertising, Conversion management and Settings, and also through linked Google Ads conversion management.
That flexibility helps teams whose sales cycles do not fit tidy presets. A local service, a software demo request, an ecommerce repeat purchase and a B2B lead do not earn credit in the same rhythm. The danger is that flexibility also makes it easier to make performance look different without making marketing better.
Why the window changes the budget story
Longer windows usually credit more delayed conversions. Shorter windows usually make reporting stricter. Neither choice is automatically more truthful. The right window depends on how long customers actually take to evaluate, return and convert, and whether the conversion is a first lead, a qualified opportunity, a sale or a repeat action.
If a team changes the window before a board report or budget review, the reported trend can become misleading. A channel may appear to improve because more delayed conversions are included. Another may look weaker because its influence happens earlier than the selected window captures. The customer did not change. The measurement rule did.
A practical checklist
- Define the business event first: lead, purchase, booked call, subscription, trial or repeat order.
- Map the observed buying cycle from CRM and transaction data before choosing the window.
- Separate click-through and engaged-view logic instead of copying one number across both.
- Document the owner, date, reason and expected reporting effect for every window change.
- Annotate GA4, Google Ads and client reporting dashboards on the change date.
- Compare pre-change and post-change performance only with a clear caveat.
- Check downstream lead quality in the CRM, not only the additional conversions credited in GA4.
How to report the change
For the first reporting cycle after a window update, show two things side by side: the operating metric used for optimization and the governance note explaining the rule change. If the change increases credited conversions, say so plainly. If it narrows the window to reduce noise, explain why the team accepts lower reported volume in exchange for a stricter signal.
Agencies should also keep this out of the black box. A client does not need every platform detail, but they do need to know when measurement rules have changed. Otherwise a legitimate analytics improvement can look like suspicious performance theater.
The CMO takeaway
Custom attribution windows are useful because they let measurement reflect the business more closely. They are risky because they can turn reporting into a settings debate. Treat the update as a policy moment: decide the window by buying cycle, document the reason, annotate the reports and validate the resulting leads or sales outside GA4.
The best use of the new flexibility is not a longer window. It is a better governed one.
