Attribution PlaybookMeasurement that survives the browser

Sep 15, 2026 - Attribution Playbook

Why Your Attribution Broke: A Short History of Losing the Signal

Most ecommerce teams know their attribution is worse than it used to be. Fewer can say precisely why, which layer failed, or what a fix actually restores. The erosion came in three distinct waves, and each needs a different response.

Wave one: intelligent tracking prevention

Browser privacy features - led by Safari's ITP - capped the lifespan of cookies set by JavaScript. A shopper who clicked your ad on Monday and bought on Saturday suddenly looked like two different visitors, because the cookie that connected them expired mid-week. Effect: returning visitors were reclassified as new, and multi-touch journeys collapsed into single sessions.

Wave two: ad blockers and tracking protection

Browser extensions and built-in protections began blocking analytics and ad pixels outright. These sessions never appear in your data at all - not misattributed, just absent. Effect: reported traffic and conversions fell below reality, and the missing share skews toward technical, higher-income audiences.

Wave three: cookie deprecation and mobile identifiers

The long phase-out of third-party cookies and mobile ad IDs removed the connective tissue between platforms. Cross-site retargeting and view-through attribution - always the least reliable numbers - degraded most. Effect: platform-reported ROAS diverged further from anything a finance team can verify.

Which fix restores which loss

Wave one's fix is first-party, server-set identifiers with durable lifetimes. Wave two's fix is server-side collection - events sent from your own domain and infrastructure rather than third-party scripts the blocker recognizes. Wave three has no full fix; the honest response is first-party data plus modeled or incrementality-based measurement. The common thread: the closer tracking lives to your own infrastructure and the network edge, the more signal survives.

Attribution Windows: Why 1 Day View and 7 Day Click Never Agree

Two platforms reporting the same campaign with different windows will produce different numbers and both can be internally correct. How to compare them without pretending one is the truth.

Change a window and you change the result. A campaign credited with 400 conversions at a 7 day click and 1 day view setting may show 260 at 1 day click, and neither figure is a lie. The longer window admits conversions where the ad was one touch among many, days before a purchase the shopper may have completed for reasons that had nothing to do with it. Comparing two platforms, or the same platform before and after a settings change, without aligning windows is the most common way teams manufacture a performance drop that never happened.

An attribution window has two parts that are often conflated: the lookback period for the touch, and which touches count, click or view. View through is the contentious half. A person who was served an impression and later bought is a weaker claim than a person who clicked, and platforms differ in how prominently they include view through in their headline number. Know which one you are reading before you act on it.

Align before you compare

Write down, for every source you report, the window, the conversion event, the timezone, the currency, and whether the figure is modelled or observed. That dull list prevents most attribution arguments. Google Analytics, ad platforms, and a store's own order system differ on all five, so their totals should not match. Agreement is not the goal. A stable, understood difference is.

When a platform changes a default, treat your trend line as broken at that date and annotate it. Teams routinely spend a month investigating a decline that begins exactly on the day a window default changed in an interface update. Annotate settings changes the way you annotate site changes and promotions. Attribution is a measurement instrument, and instrument changes belong in the record.

Choosing a window for the decision at hand

Match the window to the buying cycle and the decision. A short window is the stricter test and suits budget shifts between similar campaigns, where you want credit only for purchases plausibly driven by the ad. A longer window suits considered purchases, furniture, appliances, anything researched over weeks, where a 1 day window would credit the last search ad for work done by earlier touches.

What does not work is choosing the window that makes a favoured channel look best and then using it for everything. Decide the window by product category, publish it in the report, and keep it fixed for the period you are judging. If a channel only performs under the most generous setting, that is information about the channel, not a reason to adopt the setting.

Reporting to people who want one number

Give them one number and its definition, then the sensitivity. Headline: conversions at 7 day click, 1 day view. Underneath: the same campaign at 1 day click, and the share that is view through only. That second line changes conversations. A channel whose value is mostly view through gets a different budget discussion from one whose value is mostly clicks, even when their headline totals are identical.

Be explicit about what no window can fix. Cross device journeys, consent losses, and browser restrictions remove touches from every system. Attribution redistributes the credit that is visible. It does not recover the credit that was never recorded, which is why incrementality tests and blended store level figures belong next to platform attribution rather than underneath it.

Related reading: Attribution Playbook, Answers, Glossary.

Frequently asked questions

Which attribution window is correct?

There is no correct window in the abstract. There is a window appropriate to the product's buying cycle and the decision being made. Shorter windows are stricter and favour channels close to purchase. Longer windows credit earlier influence. Pick one deliberately, document it, and hold it steady for comparisons.

Why did my conversions drop after changing nothing?

Check the instrument first. A changed attribution setting, a consent banner change, a tag change, or a platform default update can all reduce reported conversions while orders stay flat. Compare against store orders for the same period before concluding demand fell.

Should view through conversions be reported?

Report them, labelled as view through, separately from click through. Hiding them flatters nothing and including them silently in a headline inflates channels that buy cheap impressions. The split between the two is often the most useful part of the report.

Can I compare Meta and Google numbers directly?

Not as raw totals. They use different windows, different modelling, different event definitions, and both claim credit for overlapping conversions, so adding them double counts. Align definitions as far as possible, expect a gap, and judge each channel within its own consistent series.

Frequently asked questions

Why did attribution get so much worse so quickly?

Several supports fell at once: third party cookies declined, mobile platforms restricted tracking, consent rates cut the observable share, and journeys spread across devices. Each change removed signal the old models quietly depended on.

Is last click attribution still useful for anything?

As a rough operational signal for bottom funnel activity, cautiously. As a budget setting truth it misleads, because it credits the last touch for demand other channels created and cannot see the touches privacy changes hid.

What should replace a single attribution model?

A blend: platform data read with scepticism, controlled experiments and holdouts for big questions, and marketing mix thinking for budget level decisions. No single replacement carries the certainty the old dashboards pretended to.

How should teams talk about attribution uncertainty?

Openly, with ranges and confidence stated. Reports that admit what cannot be observed produce better budget decisions than precise numbers built on a shrinking, biased sample presented as complete.