App Tracking Transparency (ATT): The Definitive Guide for 2026

What Is App Tracking Transparency?

App Tracking Transparency (ATT) is Apple's privacy framework that requires apps to ask for user permission before tracking their activity across other companies' apps and websites. Introduced with iOS 14.5 in 2021, ATT fundamentally changed mobile advertising by giving users an explicit choice about data tracking.

When a user sees the ATT prompt, they have two options: "Allow" or "Ask App Not to Track." If they choose not to allow tracking, the app cannot access the device's IDFA (Identifier for Advertisers).

Why ATT Matters

Before ATT, the IDFA was available to all apps by default. Advertisers could track user behavior across apps, build detailed profiles, and target ads with high precision. ATT shifted control to users.

Key impacts:

• Average opt-in rate is 25-35% globally in 2026 (varies by region and app category)
• Mobile ad revenue decreased significantly for apps relying on targeted advertising
• SKAdNetwork became the primary attribution framework for iOS campaigns
• Contextual advertising has resurged as an alternative to behavioral targeting

When Is ATT Required?

You must show the ATT prompt if your app:

• Accesses the IDFA for any purpose
• Uses advertising SDKs that perform cross-app tracking
• Shares user data with data brokers
• Links user or device data from your app with data from other companies' apps

You do NOT need ATT if:

• You only track users within your own app
• You use anonymous, aggregated analytics
• You link data solely on the user's device without sending it to a server
• You use SKAdNetwork for attribution (it does not require ATT consent)

Implementation

Step 1: Add the Usage Description

Add the NSUserTrackingUsageDescription key to your Info.plist file. This string appears in the permission dialog:

Good examples:

• "This allows us to show you more relevant ads based on your interests."
• "We use this to measure advertising performance and improve your experience."

Bad examples:

• "Please allow tracking" (too vague, Apple may reject)
• "Required for the app to work" (misleading, Apple will reject)

Step 2: Request Permission

Use the ATTrackingManager.requestTrackingAuthorization API. Important rules:

• Only call it when your app is in the active state
• Do not call it on first launch or during onboarding (bad UX, low opt-in rates)
• Show a pre-prompt screen explaining the value before the system dialog appears

Step 3: Handle the Response

The four possible authorization states:

• authorized - User allowed tracking, IDFA is available
• denied - User denied tracking
• restricted - Tracking is restricted (parental controls, MDM)
• notDetermined - Permission has not been requested yet

Maximizing Opt-In Rates

The pre-prompt strategy is the most effective way to increase opt-in rates:

1. Wait for the right moment - Ask after the user has experienced value (not during onboarding)
2. Explain the benefit - "Allow tracking to see fewer, more relevant ads"
3. Show a custom screen first - A well-designed pre-prompt can increase opt-in by 30-40%
4. Do not punish users who decline - Never degrade the experience for users who say no
5. Respect the decision - You cannot re-prompt. If denied, you can only direct users to Settings

Life After ATT: Attribution Alternatives

SKAdNetwork (SKAN)

Apple's privacy-preserving attribution framework. Now in version 5 (2026):

• Provides campaign-level attribution without user-level data
• Supports multiple conversion windows
• No IDFA required
• Limited data granularity compared to pre-ATT attribution

Probabilistic Attribution

Some MMPs use statistical methods to estimate attribution. Apple discourages fingerprinting and actively works to prevent it. This approach carries compliance risk.

First-Party Data

The most sustainable approach. Build direct relationships with users through:

• Email signups
• In-app accounts
• Loyalty programs
• First-party analytics

AdAttributionKit (AAK)

With iOS 18, Apple introduced AdAttributionKit (AAK) as the successor to SKAdNetwork. AAK is fully compatible with SKAN but offers broader attribution support:

• Attribution for alternative app marketplaces (under DMA)
• Safari web-to-app install attribution
• Preserves SKAN 4 conversion value structure
• As of 2026, new projects should adopt AAK while SKAN remains supported but AAK is the recommended approach

Related Topics

• iOS Privacy Labels Guide
• Privacy Manifest Guide
• Digital Markets Act and Apps