Definition

iOS ATT (App Tracking Transparency) is Apple’s framework requiring apps to request user permission before tracking activity across other companies’ apps and websites for advertising. Opt-in rates are typically low, impacting Meta and mobile measurement.

Detailed Explanation

iOS shows ATT prompt; denied users get limited IDFA access. Advertisers rely on SKAdNetwork, modeled conversions, and Aggregated Event Measurement.

Promote pre-prompt screens explaining value exchange before system dialog to improve opt-in modestly.

Web campaigns also affected via Safari ITP — not only native apps.

Nepal Context

Expect only a minority of iOS users to allow tracking, so plan Meta app install campaigns assuming measured CPI will look higher than pre-2021 baselines.

Fintech and wallet apps should emphasize privacy copy in Nepali + English pre-prompts.

Practical Examples

  1. Beginner: Audit iOS share in analytics; if <20% of revenue, deprioritize iOS-specific app install spend.

  2. Intermediate: Implement SKAdNetwork conversion schema with coarse value buckets.

  3. Advanced: MMM + incrementality for iOS-dominant products; shift prospecting to Android where LTV similar.

How to Check It

  1. Check your own opt-in rate: your mobile measurement partner or App Store Connect analytics shows how many users allowed tracking.
  2. Compare iOS and Android installs and revenue in your backend, not only in ad platforms, to see how much iOS reporting under-counts.
  3. Confirm SKAdNetwork or AdAttributionKit postbacks are reaching your ad networks.

Key Takeaways

  • ATT limits cross-app tracking on iOS.
  • SKAdNetwork provides delayed, aggregated app attribution.
  • Pre-prompts can slightly improve opt-in rates.
  • Modeling and first-party data fill gaps.
  • Nepal app advertisers must rebaseline CPI expectations.

Common Mistakes

  1. Comparing post-ATT CPI to 2019 benchmarks.
  2. No Android parallel measurement strategy.
  3. Aggressive pre-prompt dark patterns risking App Store rejection.