Advertising & Tracking Identifiers
Mobile Privacy & Data Protection · Mobile Advanced Security track
9 min read
In this module
The Advertising Identifier Ecosystem
Every phone in your pocket ships with a persistent identifier built specifically for advertisers. iOS calls it the IDFA (Identifier for Advertisers). Android calls it the GAID (Google Advertising ID). These two strings of hex are the load-bearing pillars of a multi-billion-dollar industry — they let advertisers track users across apps, measure campaign payoff, and stitch together detailed behavioural profiles.
IDFA and GAID
What They Are
Both IDFA and GAID are device-scoped, resettable, UUID-format identifiers handed out by the OS:
- IDFA (iOS): A UUID accessible through the
ASIdentifierManagerAPI. Example:EA7583CD-A667-48BC-B806-42ECB2B48606. - GAID (Android): A UUID accessible through Google Play Services. Example:
38400000-8cf0-11bd-b23e-10b96e40000d.
Each is meant to be the sole tracking identifier used by advertising SDKs. Both operating systems lock down access to hardware identifiers (IMEI, serial, MAC) precisely so users can reset their identifier and start fresh.
How They Are Used
A user opens an app with an embedded ad SDK. The SDK reads the advertising ID, fires it off with context — app name, screen, location — to the ad network. The network looks up the ID in its profile database, picks a targeted ad, logs the impression. Because the same ID surfaces in every app, the network ends up with a cross-app behavioural profile: which apps a person uses, when, how long, in what order.
Apple App Tracking Transparency (ATT)
April 2021, Apple shipped iOS 14.5 with App Tracking Transparency. The mobile advertising industry has not been the same since.
How ATT Works
ATT forces every app to show a system-controlled prompt before touching the IDFA or doing any cross-app tracking. The wording is unambiguous: "Allow [App Name] to track your activity across other companies' apps and websites?" The user picks "Allow" or "Ask App Not to Track".
If the user denies tracking:
- The IDFA returns all zeros (
00000000-0000-0000-0000-000000000000). It's also all zeros before the app has asked, so on iOS 14.5 and later only an "Allow" unlocks it. - The app is prohibited from using alternative tracking methods (device fingerprinting, email hashing, other persistent identifiers).
- The app must respect the
trackingAuthorizationStatusAPI.
Impact
Most users say no. Measured opt-in rates vary a lot by app category and by who's counting, but industry trackers have generally put them somewhere between a quarter and a half of the users who see the prompt, and lower still across all users. The fallout was massive:
- Ad networks lost cross-app profiling for the bulk of iOS users overnight.
- Apps leaning on targeted ad revenue saw earnings crater.
- Money started moving to contextual advertising (targeting based on what's on screen, not who's looking) and on-device attribution: Apple's SKAdNetwork, now succeeded by AdAttributionKit, reports installs back to ad networks with delays, coarse values and no user identifier.
Apple followed up in 2024 with privacy manifests: apps and third-party SDKs must declare the data they collect and give an approved reason for using a list of "required reason" APIs (file timestamps, system boot time, disk space and the like) that are popular fingerprinting inputs.
ATT is enforced at the OS level. When a user denies tracking, the system returns an all-zeros IDFA and Apple's guidelines prohibit alternative tracking techniques. However, enforcement of the alternative tracking prohibition relies on App Review detection and user reports. Research has shown that some apps continue device fingerprinting after the user denies tracking, though Apple has been tightening enforcement progressively.
Android: Privacy Sandbox and What's Left
Google's counter-move was meant to be the Privacy Sandbox for Android, a slow, multi-year programme to replace cross-app tracking with something less hostile to users. Its two headline pieces were worth knowing because the ideas keep resurfacing:
- Topics API: the device sorted user interests into topics locally ("Sports", "Travel", "Technology") from app usage and shared only a few labels (typically 3) from a taxonomy of a few hundred, with a random topic mixed in for noise and no persistent identifier.
- Attribution Reporting API: the device logged ad-to-install attribution locally and sent back aggregated, noised reports instead of per-user events.
It didn't survive. In October 2025 Google announced it was retiring most Privacy Sandbox technologies, including Topics and Attribution Reporting on both Chrome and Android, citing low adoption, and dropping the Privacy Sandbox branding.
GAID Lives On
Google had once said GAID would go once the Sandbox APIs were ready. With the Sandbox wound down, GAID is still the Android advertising identifier, guarded by user controls rather than a consent prompt: users can reset it, and since Android 12 delete it outright, after which apps read all zeros. Apps targeting Android 13 or later also need the AD_ID permission to read it. For analytics that don't need cross-app tracking, Google points developers at the App Set ID, which is shared only between apps from the same developer. Where Apple forced the change overnight with ATT, Android's tracking picture has barely moved.
The Identifiers an App Can Still Read
The advertising ID is only one of several values an SDK can pick up. iOS also hands every app an IDFV (identifierForVendor), shared by apps from the same vendor on one device, with no prompt; it only changes once every app from that vendor has been deleted and one is installed again. Android has the App Set ID, which follows a similar rule, and ANDROID_ID, which since Android 8 is fixed per app-signing key, user and device and survives an uninstall. None of these touch a fingerprint built from the device itself.
Identifier lifecycle
Three apps with the same ad SDK inside. Change a setting, open the apps, and watch which events the ad network can tie together. All values are illustrative random IDs.
Factory reset here sets the phone up as new and reinstalls the same three apps.
Nothing changed yet.
Daily Crossword
Grid GamesTracking: Not asked
- IDFAzeros
- 00000000-0000-0000-0000-000000000000
- ATT not asked yet
- IDFV
- B27E2A43-D604-45A1-965E-8A3355A01D35
- Shared by Grid Games apps
- Fingerprint
- 6fddf38da78ddc73
- Hash of device signals
Daily Sudoku
Grid GamesTracking: Not asked
- IDFAzeros
- 00000000-0000-0000-0000-000000000000
- ATT not asked yet
- IDFV
- B27E2A43-D604-45A1-965E-8A3355A01D35
- Shared by Grid Games apps
- Fingerprint
- 6fddf38da78ddc73
- Hash of device signals
Run Log
Stride LabsTracking: Not asked
- IDFAzeros
- 00000000-0000-0000-0000-000000000000
- ATT not asked yet
- IDFV
- 3B758A3E-E6C0-45C0-A781-A97DBB872BE2
- Shared by Stride Labs apps
- Fingerprint
- 6fddf38da78ddc73
- Hash of device signals
What the ad network can link
3 events, 2 separate profiles
- Profile 1: #1 #2 linked by IDFV
- Profile 2: #3 on its own
| # | App | After | Usable IDs sent |
|---|---|---|---|
| 1 | Daily Crossword | Start | IDFV B27E… |
| 2 | Daily Sudoku | Start | IDFV B27E… |
| 3 | Run Log | Start | IDFV 3B75… |
Events link when they carry the same value, directly or through a chain. Zeroed IDs link nothing. The fingerprint here hashes model, OS version, screen, language and IP address.
Deny tracking in all three apps on the iPhone, open them, and count the profiles the network ends up with. Then switch to Android, delete the advertising ID, reinstall Run Log and open it again: the ad ID is gone, but ANDROID_ID ties the new events to the old ones. Tick the fingerprint box to see why a factory reset doesn't help much.
Cross-App Tracking Techniques
Platform restrictions slow the industry down. They don't stop it. Several workarounds have appeared in the wild.
Device Fingerprinting
No IDFA available? Some SDKs reach for device fingerprinting — stitching device model, screen resolution, OS version, installed fonts, timezone, carrier, storage and memory into a pseudo-unique signature. Stack enough attributes and you separate devices with high confidence. Apple explicitly bans this under ATT. Detecting violations remains hit-and-miss.
Here's the arithmetic behind that confidence. Each attribute narrows the crowd by a factor, and factors multiply, so their bits add. The 1 in N numbers are made up but plausible, and adding them assumes the attributes are independent, which overstates things (screen size follows from the model). Boot time and free disk space do most of the work, which is why Apple's 2024 privacy-manifest rules make apps declare a reason before they read either.
Probabilistic Matching
Probabilistic matching lets statistics do the heavy lifting. Correlate IP address, timestamps, device characteristics, and behavioural patterns, and the algorithm links ad impressions to conversions without ever holding a hard identifier.
Ad SDK Data Collection
Ad SDKs sit inside millions of apps, hoovering up far more data than most developers realise they're shipping.
What Popular SDKs Harvest
Research has documented that major ad SDKs collect:
- Device information: Model, OS version, screen size, carrier, language, timezone.
- Location: GPS coordinates (if the host app has location permission), WiFi-derived location, IP-based geolocation.
- App usage: Which apps are installed, usage frequency, session duration.
- Network information: IP address, WiFi SSID, connection type.
- Sensor data: Accelerometer, gyroscope (used for fraud detection and fingerprinting).
The SDK Supply Chain Problem
Developers stack multiple ad SDKs to maximise fill rates. Each one collects independently, ships data to its own backend. A typical app pulls in five to ten of these, each piping telemetry to a different company. The developer rarely audits all of them properly. That's the supply-chain risk hiding in plain sight.
The mobile advertising ecosystem is built on device-scoped identifiers (IDFA, GAID) that enable cross-app user profiling. Apple's ATT framework requires explicit consent, and most users decline. On Android, Google retired its Privacy Sandbox replacements (Topics, Attribution Reporting) in 2025, so the GAID remains, limited by user reset and delete controls. Despite restrictions, device fingerprinting and probabilistic matching continue as alternative tracking methods. Ad SDKs embedded in apps collect extensive data, creating a supply chain risk most developers do not fully understand.