Growth Systems Library
Signal Loss After iOS 14
Signal loss after iOS 14 refers to the structural reduction in user-level tracking data available to ad platforms following Apple's App Tracking Transparency (ATT) framework, which required users to opt in to cross-app tracking from April 2021. Opt-in rates settled around 25–35%, meaning platforms lost visibility into roughly 65–75% of iOS conversions at the user level.
Before iOS 14, ad platforms — primarily Meta and Google — could track users across apps and websites using the IDFA (Identifier for Advertisers), a device-level identifier Apple provided automatically. This enabled precise attribution: platforms could connect an ad exposure to a purchase days or weeks later, even across different apps.
After ATT, platforms lost direct access to IDFA for the majority of users. The gap is partially filled by two mechanisms: Conversion API (CAPI), which sends server-side event data directly from a brand's systems to the platform, bypassing browser and app tracking; and modeled attribution, where platforms use machine learning to estimate conversions they can no longer directly observe.
Neither mechanism fully replaces the lost signal. CAPI improves match rates but does not restore full user-level tracking. Modeled attribution introduces estimation error that compounds over time and varies significantly by industry, audience, and creative mix. Exactius treats this as a permanent structural shift — not a problem to be solved, but an operating condition to be managed.
Signal loss directly inflates platform-reported ROAS and undermines the reliability of any attribution model that depends on user-level data. When a platform cannot observe a conversion directly, it either fails to attribute it (under-reporting) or uses modeled attribution to claim it (over-reporting). The direction of the error depends on the platform and is not transparent to advertisers.
For businesses that scaled aggressively on Meta pre-iOS 14, reported ROAS often dropped 30–50% in the months after ATT — not because performance degraded, but because attribution became incomplete. Brands that reacted by cutting spend made a measurement error, not a business decision.
The downstream consequence for LTV:CAC measurement is significant: if a channel's conversions are under-reported due to signal loss, its calculated CAC appears higher than it actually is. Capital gets reallocated away from channels that are performing, based on data that is structurally incomplete.
How to measure the impact of signal loss
Compare platform-reported conversions against first-party data sources (your analytics platform, your CRM, or your purchase database). The ratio of platform-reported conversions to independently verified conversions tells you the magnitude of signal loss in your account. A ratio above 1.2 (platforms report 20%+ more conversions than you can verify) indicates significant over-attribution from modeled data.
Mitigation approaches
CAPI implementation: Sending purchase and lead events server-side via Conversion API improves match rates. Event match quality scores above 7/10 in Meta's Events Manager indicate strong CAPI performance. This is the highest-priority technical mitigation.
MER-based measurement: Shift primary optimisation from platform ROAS to media efficiency ratio. MER requires no user-level data — it is calculated from total revenue and total spend, making it immune to signal loss.
Incrementality testing: Use geo holdouts or Meta Conversion Lift studies to measure actual causal impact rather than attributed impact. This bypasses the attribution question entirely.
iOS 14 exposed a dependency that most growth teams had never examined: the assumption that platforms were accurately reporting what was causing conversions. They were not — even before ATT. ATT made the inaccuracy visible by forcing platforms to model what they could no longer observe directly.
Exactius responded to ATT by accelerating the transition to MER-based optimisation and incrementality-based measurement for all partners. Platform-reported ROAS is treated as a directional input, not a governing metric. This approach was already embedded in the Growth Operating System before iOS 14; ATT simply made the case undeniable.
David Manela has noted that signal loss created a forcing function for better measurement infrastructure. Brands that adapted — building first-party data assets, implementing CAPI correctly, and adopting MER as their primary efficiency signal — are now operating with cleaner data than they had pre-iOS 14. Brands that did not adapt are optimising toward numbers their platforms are largely estimating.
Exactius embeds growth squads that audit CAPI implementation quality, first-party data coverage, and MER tracking as part of every new engagement. Signal quality is a prerequisite for reliable capital allocation.
What did iOS 14 change for digital advertising?
iOS 14 introduced Apple's App Tracking Transparency framework, which required apps to ask users for permission before tracking them across other apps and websites. Before this change, ad platforms could automatically access the IDFA (device identifier) to track user behaviour across apps and attribute conversions to specific ads. After ATT, opt-in rates settled around 25–35%, meaning platforms lost direct visibility into approximately 65–75% of iOS user activity. Platforms responded by using Conversion API (server-side tracking) and modeled attribution to partially reconstruct the lost signal, but neither fully replaces user-level data.
How does iOS 14 affect Facebook ad performance?
iOS 14 affected Meta's ability to track off-platform conversions for iOS users who did not opt in to tracking. The practical effects include delayed and incomplete conversion reporting (Meta moved to a 7-day click, 1-day view attribution window), reduced audience size for retargeting (fewer identifiable users), and inflated or deflated ROAS depending on how Meta's modeled attribution fills the signal gap. Brands often saw reported ROAS drop 20–50% after ATT without actual performance degrading — the ads were still working, but Meta could attribute fewer conversions. The fix is implementing Conversion API with high event match quality and anchoring optimisation decisions in MER rather than platform ROAS.
What is Conversion API and does it fix iOS 14 signal loss?
Conversion API (CAPI) is a server-side integration that sends purchase, lead, and other conversion events directly from a brand's systems to ad platforms, bypassing browser and app tracking. It improves signal quality by sending first-party data that platforms can use for attribution and optimisation — regardless of whether a user opted in to ATT. CAPI does not fully restore pre-iOS 14 signal: it can only match events for users the platform can identify through email, phone, or other first-party identifiers. Brands with strong email capture typically see 40–60% match rates from CAPI, meaningfully improving over browser-only tracking but not reaching the near-complete coverage that existed before ATT.
Exactius Growth
Your growth system is either compounding or degrading.
Book a diagnostic call. We'll identify where your growth system is breaking.
Book a call