IDFA (Identifier for Advertisers)

IDFA — the Identifier for Advertisers — is Apple's per-device advertising ID: a resettable identifier that let mobile apps recognize a device across apps for ad targeting, frequency control, and conversion attribution. For most of the 2010s it was the deterministic spine of iOS app marketing — the thing MOBILE-attribution, retargeting, and measurement ran on. App Tracking Transparency (ATT), enforced with iOS 14.5 in late April 2021, ended that era by requiring apps to win an explicit opt-in before accessing it — and most users tap 'Ask App Not to Track.'

What IDFA did and how ATT broke it: pre-ATT, the IDFA was available to apps by default (users could limit ad tracking, but few did), so an advertiser could deterministically tie an install or purchase back to the ad that drove it across the ecosystem — the clean device-level join that made iOS the measurable channel. ATT inverted the default: apps must show Apple's standardized prompt ('Allow' versus 'Ask App Not to Track'), and a denied prompt returns a null IDFA (all zeros) — no opt-in, no identifier. Opt-in rates landed low (category-dependent, frequently a minority of users), which collapsed the deterministic signal and forced the rebuild this glossary keeps documenting: SKAdNetwork (Apple's privacy-preserving, aggregated, delayed attribution framework — campaign-level signal instead of user-level, the constraint MMPs and UA teams now plan around), aggregated and modeled measurement replacing user-level certainty, FIRST-PARTY-DATA and authenticated relationships rising in value, and the broader industry lurch toward privacy-preserving measurement that the THIRD-PARTY-COOKIE's parallel decline accelerated. The strategic readings that aged well: iOS UA became a portfolio of probabilistic and aggregated methods rather than a deterministic dashboard, incrementality and GEO-style testing gained ground precisely because user-level attribution got unreliable, and 'IDFA' became shorthand for the whole deterministic-to-probabilistic transition. The honest nuance: IDFA still exists and still works for the opted-in minority — it didn't disappear, it became a consented minority signal, which is a different planning problem than absence.

IDFA matters as the hinge of mobile marketing's privacy era — the 2021 event that reorganized app user-acquisition, attribution, and measurement around consent and aggregation, and the reason SKAdNetwork, modeled conversions, and incrementality testing became core iOS competencies. It matters as literacy for reading any mobile-measurement claim (user-level iOS attribution post-ATT deserves the question 'on whose opted-in data?') and as the template for the cookie's parallel story. The discipline is planning iOS as a consented-and-aggregated channel — opt-in experience optimized honestly, SKAdNetwork and modeling understood, incrementality leaned on where deterministic IDs went quiet — rather than mourning the deterministic default that isn't coming back.

Apple introduced IDFA in 2012 as a resettable, privacy-improved replacement for device UDIDs, and it anchored iOS ad measurement for nearly a decade; App Tracking Transparency (iOS 14.5, April 2021) put it behind an opt-in, turning the deterministic default into a minority signal and forcing mobile marketing's aggregation era.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where idfa is a core concern: