Attribution & Measurement

IDFV (Identifier for Vendors)

Also known asIdentifier for VendorsVendor ID

Apple's per-vendor device identifier: the same across all apps from one developer on a device, available without ATT consent — but useless for tracking across publishers.

Key takeaways

  1. 01IDFV is the same value across all apps from one vendor (developer) on a device, and different across vendors.
  2. 02Unlike IDFA, IDFV needs no ATT consent prompt — it is available by default.
  3. 03It cannot track users across different publishers, so it is not an advertising identifier.
  4. 04It resets when the user deletes all of that vendor's apps from the device.

The IDFV (Identifier for Vendors) is an Apple device identifier that is the same across every app from a single vendor (developer) on a given device, and different for other vendors. It is the counterpart to the [[idfa]] (Identifier for Advertisers), but built for a different purpose: first-party measurement within one company's portfolio rather than cross-publisher ad tracking.

The key difference is consent. [[idfa]] requires an [[att]] (App Tracking Transparency) prompt and is only available if the user opts in — which most don't. IDFV needs no prompt and is available by default, precisely because it can't follow a user across different companies' apps: its scope is limited to one vendor. That makes it useful for stitching sessions across your own family of apps, deduplicating users, frequency capping within your portfolio, and some fraud signals — but useless as an advertising identifier across publishers.

Reset behavior: the IDFV persists as long as the user has at least one app from that vendor installed. Delete all of a vendor's apps and the IDFV is discarded; install one again and a new IDFV is generated. Android has no exact equivalent — the closest, the [[gaid]], is a cross-publisher advertising ID more analogous to IDFA.

Quick answers

What is the difference between IDFA and IDFV?

IDFA is a cross-publisher advertising identifier that requires ATT consent and is used for ad attribution across different companies' apps. IDFV is scoped to a single vendor (developer), is the same across that vendor's apps, requires no consent prompt, and cannot track across publishers — it is for first-party, within-portfolio measurement.

Does IDFV require ATT consent?

No. Because IDFV cannot follow a user across different companies' apps (it is vendor-scoped), it is not covered by App Tracking Transparency and is available by default — no prompt required. IDFA, by contrast, requires explicit ATT opt-in.

When does the IDFV change?

It stays constant as long as the user has at least one app from that vendor installed on the device. If they uninstall every app from that vendor, the IDFV resets, and a fresh one is generated when they next install one of the vendor's apps.

Can I use IDFV for ad attribution?

Not across publishers — IDFV is vendor-scoped, so it can't connect an ad shown in another company's app to your install. It is for first-party use cases: cross-app analytics within your own portfolio, user dedup, frequency capping, and some fraud detection. For cross-publisher attribution under ATT, teams rely on SKAdNetwork and IDFA-when-consented.

Back to glossary