Apple's ATT framework arrived with iOS 14.5 and changed how mobile teams measure ad performance. The system prompt that now appears before any cross-app tracking starts is not just a UX element. It controls whether your app can access the IDFA, the identifier that most paid channels relied on for granular attribution.
When a user taps "Ask App Not to Track," your ad platform loses that precise signal. Campaigns running on Meta, Google UAC, or TikTok shift from individual-level attribution to modelled data. You still see numbers in the dashboard, but those numbers represent statistical averages rather than real conversions.
SKAdNetwork and What It Replaces
SKAdNetwork is Apple's privacy-preserving attribution framework. It sends aggregated, delayed conversion data back to ad networks without exposing individual user identifiers. The delay can be up to 24ā48 hours and the granularity is significantly reduced compared to IDFA-based tracking.
Most teams now run a blended attribution approach: SKAdNetwork covers non-consenting users, while first-party signals from consenting users fill in the gaps for opted-in cohorts. The ratio between these two cohorts determines how accurately you can measure your actual ROAS.
Where Consent Strategy Enters the Stack
The system prompt cannot be modified. However, a custom pre-prompt screen that loads before it can explain what tracking enables for the user in plain language. Timing also changes opt-in rates measurably. Showing it after a value moment rather than at first launch consistently produces better results.
Tools like the Seers Mobile App CMP handle the consent capture layer. They store and sync consent signals across iOS and Android, forward approved permissions to your analytics and ad SDKs, and keep your attribution pipeline intact for opted-in users. Consent data is also audit-ready for GDPR and CCPA compliance.
Top comments (0)