What Is iOS 14.5 Tracking Changes (ATT)?
iOS 14.5 introduced App Tracking Transparency (ATT), an OS prompt that forces every app (including Meta, TikTok and Snap) to ask iPhone users for permission before using their advertising identifier (IDFA). About 75 percent of users declined worldwide, which collapsed cross-app attribution, shrank retargeting audiences and forced every major ad platform to switch to server-side signals, event caps and probabilistic modelling.
The 2026 fallout, in numbers
A DTC brand that ran 60 percent iOS traffic saw reported Meta purchases fall 32 percent overnight in May 2021 while Shopify sales were flat. In 2026 the same brand runs Meta CAPI plus sGTM, sends Enhanced Conversions to Google, and uses MER (not platform ROAS) as the primary KPI. Reported ROAS is still 15 to 20 percent lower than pre-ATT, but decisions are made off blended MER, so scaling is stable.
Benchmarks
- iOS opt-in rate: 20 to 30 percent worldwide as of 2026; lower in EU, higher in Japan.
- Meta signal recovery with CAPI + AEM: 60 to 80 percent of pre-ATT attribution.
- Signal recovery with CAPI + sGTM + first-party CRM sync: 85 to 95 percent.
- Retargeting audience shrinkage on iOS: 40 to 70 percent smaller than 2020 baselines.
Why it matters
iOS 14.5 is not a one-time event. It set the direction of the entire ad industry: less cross-app data, more first-party data, more modelling. Every measurement decision after 2021 (Consent Mode v2, EMQ, Enhanced Conversions, PMax modelling) is a downstream consequence. Brands that still measure like it is 2019 systematically underspend on the winners.
Common mistakes
- 1.Still judging Meta on platform ROAS alone. Post-ATT it under-reports iOS by 20 to 40 percent.
- 2.Ignoring Aggregated Event Measurement setup. Web events on iOS are capped at 8; wrong prioritisation kills your Purchase event.
- 3.Running Pixel-only. Without CAPI you cannot recover the traffic ATT blocked.
- 4.Assuming Android is fine. Android Privacy Sandbox is on the same trajectory; the same fixes apply.
Put iOS 14.5 Tracking Changes to work
Free calculators
Related services
FAQs about iOS 14.5 Tracking Changes
Is iOS 14.5 still relevant in 2026?
Yes. ATT is the baseline; every OS update since (iOS 15, 16, 17, 18) has tightened it further. Nothing has been rolled back.
Does CAPI fix iOS 14.5 attribution?
It recovers most of it, not all. CAPI plus sGTM plus properly hashed customer parameters gets you into the 85 to 95 percent range vs pre-ATT baseline.
Should I still use lookalike audiences on iOS?
Yes, but seed them from server-side purchasers, not Pixel-only web events. Otherwise your seed is missing a third of your best customers.
What KPI should replace platform ROAS?
MER (Marketing Efficiency Ratio) as your north star, backed by geo holdouts or incrementality tests once a quarter. Platform ROAS becomes a bidding signal, not a decision metric.
Go deeper
Long-form reads that show iOS 14.5 Tracking Changes applied end to end.
Related terms
Server-side event stream from your site/CRM to Meta or Google.
Meta's privacy-safe event system after iOS 14.5; caps you at 8 ranked events.
Meta's 0 to 10 score of how well events match to a Meta user.
How credit for a conversion is assigned across ad touchpoints.
Customer data you collected yourself with consent; the strongest signal.
Google's consent signalling API; required in EEA for ad measurement.
Estimated conversions Google or Meta report when direct measurement is blocked by consent or ITP.