Attribution windows in a privacy-first UK market

The Mobile Funnel Clinic spends a full evening on a sentence growth teams dislike: you will not get the 2019 last-click report back. Apple’s App Tracking Transparency, SKAdNetwork’s delayed and coarse posts, and the ICO’s view of storage and access on devices under PECR are not a mood. They are the climate in which a United Kingdom consumer app now buys attention.

An attribution window is a policy pretending to be a measurement. Seven days after click, twenty-four hours after view — these are conventions. They were always conventions. When identifiers were plentiful, the convention felt like physics. When a large share of iOS users refuse tracking, the same window still produces a number. The number describes the consented, matchable remainder, plus whatever modelling the ad network will not fully disclose. Presenting it as “our CAC” without that clause is the kind of theatre we fail in critique.

What still belongs in App Analytics: first-party events after consent, campaign parameters you control, store listing experiments, and a clear split between users who arrived with a deferred deep link you implemented and users who arrived as organic because the device would not tell you otherwise. What does not belong: a blended ROAS that quietly includes modelled conversions as if they were observed checkouts.

We ask students to keep two funnels for paid: the consented, deterministic path, and the store-reported path. They will disagree. The disagreement is the report. If finance needs a single figure for a board pack, label it as a planning assumption, not as an observation. That honesty has cost some teams a favourite campaign. It has also stopped them scaling a ghost.

Legal is not a guest lecture we tack on. If your consent banner rejects analytics cookies, your web-to-app story is already broken in the browser before the store is involved. Fix the banner copy with counsel; do not ask the analytics tutor to invent a join that the user refused.