Facebook "App Tracking Transparency" iOS issues

Quick Answer

Set up Aggregated Event Measurement in Events Manager, prioritise your top 8 conversion events, verify your domain, and integrate the Conversions API. This combination recovers most of the iOS attribution lost to ATT.

Step-by-step fix

1. Verify your domain in Business Manager → Brand Safety → Domains. Required for AEM.
2. Open Events Manager → Aggregated Event Measurement → click Configure Web Events.
3. Add your verified domain.
4. Prioritise 8 events in order of business value. The first event is typically Purchase, then InitiateCheckout, AddToCart, Lead, ViewContent, etc.
5. For value-based events (like Purchase), set up the value optimisation tier — Meta will track the value of converting users in addition to the binary conversion.
6. Set up Conversions API server-side. CAPI is not blocked by ATT because it's server-to-server, not browser-to-Meta.
7. Use the same event_id in both Pixel and CAPI for deduplication.
8. Wait 72 hours for the AEM configuration to propagate. iOS users will start being attributed via the prioritised events.
9. Check the iOS reporting in Ads Manager — look for the "Attribution Setting" filter and switch between modelled and actual data.

Why it happens

Apple's App Tracking Transparency (ATT) framework, introduced in iOS 14.5 (April 2021) and tightened in subsequent iOS releases, requires apps to ask users for permission to track them across other companies' apps and websites. Most iOS users (around 75%) opt out.

When an iOS user opts out:

• Meta can't access their IDFA (Identifier for Advertisers).
• The Pixel can't reliably link a Facebook session to a website conversion.
• Conversion data for that user becomes anonymous and aggregated.
• Custom audiences based on website visitors shrink dramatically.
• Lookalike audiences get less seed data.
• Reporting in Ads Manager delays by up to 72 hours for iOS.

Meta's response was a multi-layered system:

1. Aggregated Event Measurement — uses Apple's privacy-compliant aggregation framework.
2. SKAdNetwork integration — for app install campaigns.
3. Conversions API — server-side data that bypasses browser restrictions.
4. Modelled conversions — statistical estimation of unmeasurable conversions.
5. Enhanced match quality — better matching for the events Meta does receive.

The net effect: iOS attribution went from near-perfect (pre-ATT) to about 50-70% accuracy (post-ATT, with all the fixes).

How to prevent it

• Treat ATT as permanent. It's not going away.
• Always run CAPI in parallel with the Pixel. Server-side data is your only reliable iOS signal.
• Verify your domain even if you don't think you need to. Without it, AEM can't be configured.
• Send hashed user data with every CAPI event for cross-device matching.
• Use Conversion API for Offline Events if you have CRM data — match offline conversions back to ad clicks.
• Plan your 8 events carefully. Once configured, you can change them but each change requires a 72-hour reset.
• Build a measurement framework that doesn't rely on platform attribution alone — incrementality testing, MMM, post-purchase surveys.
• Use the iOS-specific reporting view in Ads Manager so you understand what's measured and what's modelled.

When to escalate to Meta support

Escalate only if:

• AEM configuration is failing despite having a verified domain.
• Your Conversions API is showing events in Test Events but not in production reporting.
• Modelled conversions are showing as zero across all iOS campaigns.

Use Pro Team Chat with the dataset ID and AEM configuration screenshot.

Pix-Vu mention

With iOS attribution permanently degraded, ad creative is more important than ever — the algorithm has less data to work with, so it leans harder on creative quality signals. Pix-Vu helps you keep your creative library upgraded and varied so you give the algorithm the strongest possible signal.