iOS ATT: what opting out did to Meta tracking

What ATT is

App Tracking Transparency, ATT, is Apple’s iOS framework that requires apps to ask permission before tracking a user’s activity across other companies’ apps and websites. When an app wants to use the device’s advertising identifier, the IDFA, for tracking or ad targeting, iOS shows a system prompt asking the user to allow or deny it. Since its rollout in 2021, most users have declined, which means the IDFA is unavailable for a large share of iOS devices.

For Meta and other ad platforms, the IDFA was previously a reliable way to connect an ad impression or click to a later app install or in-app action, even across different apps and sessions. Without it, that direct link disappears for opted-out users.

What changed

Before ATT, Meta could attribute a conversion to a specific ad by matching device-level signals across the ad and the advertiser’s app or website. After ATT, for users who decline tracking, Meta cannot make that direct match. This affected several things at once: the accuracy of attributed conversions, the size of usable custom audiences built from app events, and the granularity of reporting, since data for opted-out users can no longer be broken down by as many dimensions.

Meta responded with its Aggregated Event Measurement protocol, which lets advertisers report a limited number of prioritized conversion events per domain, aggregated in a way that satisfies Apple’s privacy requirements. Reporting windows also shortened, and some breakdowns, like detailed demographic splits on conversions, became less available or delayed for affected traffic.

Why it matters

The practical effect is that reported conversions since ATT undercount actual outcomes, particularly on iOS. Attribution windows are also less accurate, since Meta increasingly relies on statistical modeling to fill gaps left by missing device-level signals, rather than direct observation. A campaign might be performing better than the dashboard shows, but the platform has no way to prove it for the affected slice of traffic.

This matters most for app install campaigns and any advertiser whose customers are heavily iOS-based, since the coverage gap is concentrated there. Android tracking is largely unaffected by ATT specifically, though other privacy changes have moved in a similar direction across the industry.

How to act on it

Set up Meta’s Conversions API alongside the standard pixel or SDK, since server-side event sharing is not affected by ATT in the same way and provides a signal that survives even when browser or device-level tracking is blocked. Configure Aggregated Event Measurement thoughtfully, prioritizing the conversion events that matter most for your business since only a limited set can be tracked per domain.

Treat reported ROAS with more skepticism for iOS-heavy audiences, and lean on modeled conversions and incrementality testing, like conversion lift studies, to sanity check what the pixel alone under-reports.

Common mistakes

Assuming reported conversions dropped because campaigns got worse, rather than because measurement got worse, leads to unnecessary campaign changes. Skipping Conversions API setup leaves a real measurement gap that has a known fix. Over-prioritizing low-value events in Aggregated Event Measurement, when only a handful can be tracked per domain, wastes the limited signal budget on the wrong actions. Comparing pre-ATT and post-ATT performance directly, without adjusting for the measurement change itself, produces a misleading trend line.

How YieldBI helps

YieldBI combines pixel and Conversions API signals in its conversion tracking, so the gap left by ATT-affected iOS traffic is partially closed rather than simply missing from reporting, and its incremental attribution models give a truer read than raw pixel data alone.