BlogAttribution
Attribution

The post-IDFA attribution playbook: signals, scoring, and what to ship next

Five years after ATT, the playbook has settled. Here's the waterfall we recommend, the signals worth scoring, and the trap most teams still fall into.

ARAnya RousselHead of ProductMay 8, 2026·9 min read

It has been five years since Apple shipped App Tracking Transparency. The 'we'll know more in six months' phase is long over. What we know now is that mobile attribution lives on a probability spectrum — and the teams that ship best treat that spectrum as a feature, not a problem to wish away.

A waterfall, not a single signal

The mistake we see most often is teams treating attribution as a single check: 'did we match this install or not?' Real systems run a waterfall. Each layer is more accurate than the one below it, and each layer catches a different slice of users.

  1. 1Google Play Install Referrer — deterministic, free, Android-only. If you ship on Android and don't use this, fix that first.
  2. 2IDFA match — deterministic on iOS, but only for the ~20% of users who grant ATT.
  3. 3GAID match — deterministic on Android, when the user hasn't opted out of ad personalization.
  4. 4Multi-signal fingerprint — probabilistic. IP, User-Agent, screen dimensions, timezone, and locale, weighted and scored against a confidence floor.
  5. 5Organic — no match. Stop trying to force one.

Each layer should fall through to the next, and the install record should carry the match type with it. 'How did we attribute this?' is a question your analytics tools should be able to answer at query time.

Score, don't binary-match

Fingerprint attribution works. What does not work is treating it as a yes/no. Weight your signals, score the match, and publish the score alongside the install.

// Recommended starting weights
const weights = {
  ip: 0.40,
  userAgent: 0.25,
  screen: 0.15,
  timezone: 0.10,
  locale: 0.10,
};
const score = weighted(click, install, weights);
if (score >= 0.6) attribute({ matchType: 'fingerprint', score });

Why a floor of 0.6 and not 0.5? Because the cost of falsely attributing an organic install is much higher than the cost of conservatively crediting a paid one. False positives quietly inflate ROAS dashboards — and inflated dashboards are how growth teams misallocate the next quarter's budget.

The trap: optimizing on the wrong cut

The most common failure mode in 2026 is teams optimizing campaigns on a blended attribution number that mixes deterministic and probabilistic matches without weighting. The result: high-IDFA channels (e.g., Apple Search Ads) look amplified, fingerprint-heavy channels (e.g., influencer) look starved. Always be able to slice your performance dashboard by match type.

Show me a marketing report that doesn't break out match type and I'll show you a marketing report that's quietly wrong.
Internal Link Trail post-mortem, March 2026
Tagged#iOS#ATT#Fingerprinting#SKAN