IDFA (Identifier for Advertising)

What is IDFA (Identifier for Advertising)?

IDFA (Identifier for Advertising) is a unique, device-level identifier assigned by Apple to iOS devices for use in advertising and measurement. Mobile marketers use IDFA to track user engagement with ads, measure campaign effectiveness, and target specific audiences without exposing personally identifiable information. Since iOS 14.5, accessing IDFA requires explicit user permission through Apple's App Tracking Transparency (ATT) framework.

How it works

IDFA is a randomly generated string assigned by iOS at the device level. Apps that want to access this identifier must request user permission through the ATT prompt introduced in iOS 14.5. When a user grants permission, the app receives the device's IDFA and can use it for cross-app tracking, attribution, and audience targeting.

IDFA in Attribution

When a user taps an ad and installs an app, the advertising network records the IDFA at the time of the ad click. The installed app then reads the IDFA (if permission was granted) and sends it to the mobile measurement partner (MMP). The MMP matches the IDFA from the install event against the IDFA from the ad click to determine which campaign drove the install, enabling deterministic attribution.

IDFA in Targeting

Advertisers use IDFA to build audience segments based on prior in-app behavior, purchase history, or ad engagement. Demand-side platforms and ad networks use IDFA to serve retargeting campaigns to existing users or to create lookalike audiences by matching known high-value users to similar device profiles.

ATT and IDFA Availability

Under ATT (iOS 14.5+), users must explicitly opt in before an app can read their IDFA. If a user denies the ATT prompt or has not been prompted yet, the app receives a zeroed-out IDFA string, making deterministic tracking unavailable for that user. When IDFA is unavailable, measurement falls back to probabilistic modeling, SKAdNetwork (SKAN) postbacks, or privacy-preserving attribution methods. The identifierForVendor (IDFV) remains accessible without ATT consent but is scoped to a single vendor and resets on app reinstall.

Why it matters

IDFA is the foundation of deterministic mobile attribution on iOS. When available, it enables precise, user-level matching between ad interactions and downstream events such as installs, purchases, and re-engagement. This precision allows marketers to allocate budget confidently across channels, optimize creative performance, and suppress ads to users who have already converted.

The ATT framework introduced in iOS 14.5 meaningfully reduced IDFA availability across the iOS user base. Marketers working with reduced IDFA signals must rely on a combination of SKAdNetwork postbacks, aggregated conversion modeling, and probabilistic attribution to maintain campaign visibility. Platforms like Airbridge support all of these fallback methods, ensuring measurement continuity regardless of ATT consent status.

For re-engagement and retargeting specifically, IDFA availability is critical. Without it, re-engaging specific users across apps becomes significantly harder, increasing reliance on contextual signals and first-party data strategies. Advertisers who optimize ATT prompt timing and messaging see meaningfully higher opt-in rates, which directly expands the deterministic attribution pool.

How to measure campaigns using IDFA

Step 1: Implement ATT Prompt Correctly

Integrate the AppTrackingTransparency framework into your iOS app. Present the ATT permission prompt at a moment when users understand the value of personalization, such as after onboarding or before a rewarded experience. A well-timed prompt with a clear purpose string improves opt-in rates.

Step 2: Integrate an MMP SDK

Integrate a mobile measurement partner SDK such as Airbridge into your app. The MMP SDK reads the IDFA (when available) and sends it alongside install and in-app event data to enable deterministic attribution across your ad network partners.

Step 3: Configure Fallback Measurement

For users who deny ATT, configure SKAdNetwork postbacks through your MMP to capture aggregated install signals from Apple. Set up probabilistic modeling as an additional layer to estimate attribution for non-consenting users based on signals such as IP address and device metadata.

Step 4: Monitor IDFA Availability Rates

Track your app's ATT opt-in rate within your MMP dashboard. Segment campaign performance by IDFA-available versus IDFA-unavailable cohorts to understand measurement gaps and calibrate your optimization strategies accordingly.

Step 5: Supplement with First-Party Data

For retargeting and re-engagement, build first-party audiences using IDFV or hashed email addresses where users have consented. These signals complement IDFA-based targeting and reduce dependency on third-party identifiers.

Related concepts