Attribution Windows Explained: What 7-Day Click / 1-Day View Really Means

There is a dropdown in Meta Ads Manager that can cut a campaign's reported conversions in half. It is called the attribution setting, most advertisers never touch it, and its default — 7-day click, 1-day view — quietly decides what your dashboard calls success. Change the window and the number changes. Your sales do not.

This post explains what an attribution window actually is, how the window choice inflates or deflates everything downstream — conversions, CPA, ROAS — why platforms default to the generous end of the dial, and how to neutralize the distortion when comparing platforms.

What an Attribution Window Actually Is

An attribution window is the maximum time a platform allows between an ad interaction and a conversion for the ad to claim credit. "7-day click / 1-day view" means two separate clocks are running:

• Click window (7 days). Someone clicks your ad on Monday and buys on Saturday — five days later. The purchase falls inside the 7-day click window, so the ad gets full credit.
• View window (1 day). Someone scrolls past your ad without clicking, then buys within 24 hours through any other path — a branded search, a bookmark, a friend's link. The ad still gets credit, because an impression happened inside the view window.

The conversion itself happens at one moment in time. The window only decides whether the platform is allowed to write that conversion into your report. That distinction matters more than it sounds: the window is an accounting rule, not a measurement of cause and effect. A click seven days before a purchase might have driven it — or the buyer might have been coming anyway. The window cannot tell the difference; it just sets the cutoff for claiming. And of the two clocks, view-through is by far the weaker evidence: a click is a deliberate act, a view is your ad being on screen while someone scrolled toward something else — yet both land in the same conversions column.

The Same Campaign, Three Different Realities

Here is the mechanic in numbers. This is illustrative math — invented figures chosen to make the moving parts visible, not benchmarks from any study. Suppose a campaign spends $10,000 and your store records 100 orders of $400 each that interacted with this ad at some point before purchase:

Same spend. Same orders. Same customers. The only thing that changed is which conversions the platform is permitted to count — and the "performance" of the identical campaign ranges from 4.0x to 2.2x.

Each step removes a specific population. Dropping view-through removes everyone who saw the ad but never clicked it. Shrinking from 7-day to 1-day click removes everyone who clicked but took more than a day to decide — which is most buyers of anything considered: higher prices, B2B, comparison-shopped products. The same window change distorts a cheap-impulse campaign and a high-ticket campaign in completely different proportions.

Why Platforms Default to Generous Windows

It is tempting to read the defaults as a trick. Read them instead as incentives — they stack three deep:

• Reported performance is the product demo. The platform sells ads, and the conversions column is how it proves the ads work. A wider window means more conversions attributed, which means the platform looks better in the exact report you use to decide next month's budget.
• There is a defensible argument underneath. Ads genuinely have delayed effects — a 7-day window catches real conversions that a 1-day window would miss. The generous default is not pure fiction; it bundles real delayed influence together with coincidence and refuses to separate them.
• Optimization wants volume. Automated bidding learns from attributed conversions. More attributed events means more training signal. Narrow windows starve the algorithm, so the platform has an operational reason — not just a vanity reason — to prefer wide ones.

The settings are documented and adjustable on both major platforms (Meta attribution settings, Google attribution models). But the default is the platform's choice, made in the platform's interest — and most accounts run on the default.

Shrinking the Window Changes the Report, Not Reality

When a team shortens its attribution window and conversions "drop 30%," someone usually panics. Nothing dropped. Revenue is identical to the cent. What changed is the claiming rule — the campaign is producing exactly what it produced yesterday, under a stricter accountant.

This cuts both ways: widen the window the week before a budget review and ROAS "improves" — the same lever, pulled in the other direction.

Two practical consequences follow:

• Never compare across a settings change. If the window changed mid-quarter, every period-over-period comparison spanning that date is corrupted. A window change shows up in your charts as a performance change, and it will be misread as one.
• A window is not an incrementality test. Even the strictest window only tells you a conversion happened after an interaction, not because of it. Whether the ad created the sale is a separate question, answered by holdouts and geo tests — not by any dropdown.

How to Compare Platforms Fairly

The everyday trap: Meta's dashboard on its default window next to Google's dashboard on its own settings, side by side in a spreadsheet, treated as comparable. They are two different rulers measuring two overlapping claims on the same orders. Whichever platform runs the more generous rules wins your next budget reallocation — for accounting reasons, not performance reasons.

Normalizing is straightforward:

1. Match the windows. Set both platforms to the closest equivalent click window, and exclude view-through from cross-platform comparisons. View-through is platform-specific evidence at best; it has no place in a head-to-head.
2. Better: use one ruler you own. Capture clicks first-party on your own domain — with their gclid, fbclid, and UTM parameters — ingest orders from your checkout, and join the two under a single attribution model with a single window applied uniformly to every channel. This is how Decisa computes it: one set of rules, every platform measured identically, every match inspectable. The platforms stop grading their own homework.
3. Keep platform numbers for platform jobs. In-platform metrics remain useful for comparing creatives and audiences within one platform, where the ruler is at least consistent. Budget allocation across platforms is where the windows must be normalized or the comparison is fiction.

What to Do This Week

1. Look up your current windows. Find the attribution setting on every active account. If you cannot say what windows your numbers are built on, you do not know what your numbers mean.
2. Annotate every change. If you adjust a window, record the date and never compare across it.
3. Run the two-window read. Pull your top campaign under the default window and under 1-day click. The gap is your exposure to slow-click and view-through credit — the share of reported performance that evaporates under a stricter rule.
4. Stand up one uniform measurement. First-party clicks plus checkout orders, one model, one window, all channels.
5. Keep feeding the platforms. Normalizing your reporting does not mean starving smart bidding — keep sending conversion signals, and do your judging elsewhere.

An attribution window is an accounting policy wearing a performance costume. The campaign does not change when the dropdown changes; only the story does. Pick one ruler, apply it to every platform, and stop letting each one choose how it gets measured.