What Is an Attribution Window?

An attribution window is the period in which a marketing interaction is eligible to receive credit for a later action, such as a signup. The window defines eligibility; the attribution model determines how eligible interactions share credit. A reported conversion is not proof that one advertisement caused the action.

Dupple publishes technology newsletters and sells sponsorships and post-signup lead generation. We have a commercial interest in those channels. The examples below are fictional and illustrate measurement choices, not real customer outcomes.

How a window changes eligibility

Imagine a newsletter reader clicks a campaign link on 2 November and signs up on 8 November. In a fictional reporting setup with a seven-day click lookback, that click falls within the eligible interval. With a three-day lookback it falls outside. Whether the seven-day setup actually assigns credit to that click depends on its attribution model, data availability and any other eligible interactions. The reader may also have visited the product's website through another channel.

The seven-day and three-day periods above are examples, not recommended defaults. The precise boundary can depend on how a platform counts days, time zones and event timestamps. Before comparing reports, read the tool's definition and test a known event path where possible. A longer window can make more interactions eligible; it does not make those interactions more causal.

Google Analytics describes its key-event lookback window as the period in which touchpoints can receive attribution credit. Its current settings and reporting behavior apply to that product, not automatically to a newsletter publisher or an advertiser's customer relationship management system.

Google Analytics defaults are product settings, not recommendations

As checked 6 November 2026, Google's key-event lookback documentation states different defaults for different event types. These describe that product's settings; they are not Dupple campaign terms or a recommendation for your buying cycle.

Table: Google Analytics documented lookback settings, read 6 November 2026.

The separate attribution settings page likewise describes the 30-day acquisition default and 90-day default for other key events. Distinguish those settings from the fictional 7-day and 3-day examples above. A default of 90 days does not establish that every property, report or campaign you inspect uses 90 days, and a choice of 30 days does not make the underlying event a qualified sale. Record the setting actually in force for the report.

Window, model and event are different choices

Table: measurement choices to record before comparing attribution reports. The order follows the decisions from event definition to reporting.

A report can use the same attribution window but produce different results when its event definitions or model change. Conversely, two systems can use the same event and different lookback periods. The table is a checklist, not evidence that any one platform supports every setting. Record the product, configuration and effective dates alongside a report.

How does a lookback period work?

The action being measured anchors the lookback. The system looks backward from that event and determines whether a prior interaction is eligible under its rules. Eligibility is a necessary input to attribution, but it does not mean that every eligible touchpoint receives full credit. Some models allocate credit to one interaction; others can divide it among multiple interactions.

Google's attribution settings documentation describes how its reporting model and key-event lookback settings work. It also notes that data-driven attribution can produce fractional credit. Those settings are specific to Google Analytics and can change. Check your own property rather than assuming its defaults or settings apply to another company's report.

In the fictional example above, add an organic search visit on 6 November. Both the newsletter click and search visit might be in a seven-day window, but the credited source depends on the model and available data. A newsletter publisher's count of outgoing clicks, an analytics report and a CRM report may therefore use different denominators and differ without any one report being a complete record of the buyer's journey.

Click windows and view windows

A click-based window uses a recorded click as the qualifying interaction. A view-based window concerns an eligible exposure under a platform's own measurement rules. These are not interchangeable. A delivered email, an open signal, a tracked click, a landing-page session and a purchase are distinct events. Ask how each is measured before interpreting a report.

Email open measurement has particular limitations. The guide to open rates under Mail Privacy Protection discusses why an open signal should not be treated as proof that a person read an ad. A view-through claim also depends on whether the platform can observe an eligible exposure and connect it to a later event. Do not infer a view-through conversion merely because an email was sent.

If the publisher offers only aggregate placement clicks, that report does not by itself identify a person or follow their later path. Agree on the reporting terms and data use before a campaign. A marketing analytics tool may have its own recorded click or session data; it still cannot recover interactions that were not recorded or linked.

Choose a window for the decision

Begin with the event and the time a real evaluator may need to complete it. A subscription signup immediately after a trial and a procurement decision involving several stakeholders answer different questions. Choose a primary window before reviewing the results and write down why it suits the decision. If you also show a shorter or longer sensitivity view, label each clearly and keep the event and model consistent.

Longer is not automatically more accurate. It can include older touchpoints whose contribution is uncertain, while a short window can exclude an interaction that genuinely preceded a longer evaluation. Consent choices, browser restrictions, cross-device behavior and inconsistent identifiers may prevent a tool from observing or joining a path. The appropriate response is to disclose those gaps, not to claim the missing activity did not happen.

For a fictional software trial, a team might report signup events with a seven-day click window and also show a separate thirty-day view. It should not add the two totals together: the eligible sets can overlap. If the team later measures signed contracts, it should define a new event and reporting period instead of treating all trial signups as sales. These durations are examples, not Dupple product settings or universal recommendations.

What should a newsletter advertiser record?

Record the issue date, placement, campaign link, event definition, analytics configuration and any reporting limitations. Use a consistent link naming convention, and check the landing page before launch. The UTM and sub ID guide explains different identifiers; the GA4 measurement guide covers campaign setup. A UTM is a label for traffic, not an attribution window or a guarantee that an individual conversion can be connected to an ad.

Dupple's guide to buying newsletter ads suggests questions about placement and reporting. For a first campaign, agree on what the publisher counts and how the advertiser will measure its own downstream actions. The first sponsorship test guide and ROI measurement guide cover how to define a test. Ask about actual deliverables instead of assuming a publisher supplies identity-level data or a particular lookback report.

Do not equate attribution with an incremental impact study. When a business needs to know what would have happened without a campaign, it needs a suitable comparison or experiment and an interpretation that reflects its design. A credited conversion is useful as a reportable signal, but it is not a controlled estimate of the advertisement's effect.

What we could not verify

We have not established one ideal attribution window, a universal newsletter conversion rate or an attribution setting included in every Dupple proposal. Google documentation describes Google Analytics settings rather than Dupple's campaign reporting. The examples are invented and do not establish an advertiser's results.

FAQ

Sources and related reading

Sources read 6 November 2026: Google Analytics attribution settings and key-event lookback windows. These are product-specific explanations and may change. Dupple's advertising glossary, unique clicks guide, AI referral traffic guide and advertiser data page provide related context. Explore Dupple advertising for available placements.