At a Glance:
IDFV (Identifier for Vendors) is a unique ID assigned by Apple that helps identify a user within apps from the same developer on a device. Unlike IDFA, IDFV doesn't require App Tracking Transparency (ATT) consent, making it a reliable fallback when users opt out of tracking.
How IDFV Works
All apps from the same developer (vendor) on a device share the same IDFV
Apps from different developers will have different IDFVs on the same device
The IDFV is device-specific + developer-specific
If a company has 3 apps installed on a user’s phone, all 3 apps will have the same IDFV.
Key Characteristics
Shared within the same developer apps
Different across developers
Does not track users across different companies’ apps
Privacy-safe (does not reveal personal data)
When Does IDFV Change?
IDFV stays the same as long as at least one app from that developer is installed
If the user deletes all apps from that developer, the IDFV resets
A new IDFV is generated when the app is installed again
Why IDFV is Important
IDFV is mainly used for:
First-party analytics
Cross-promotion between your own apps
Understanding user behavior within your app ecosystem
Tracking reinstalls within the same developer apps
IDFV vs IDFA (Quick Difference)
Feature | IDFV | IDFA |
Scope | Same developer apps only | Across all apps |
Consent Required | No | Yes (via ATT) |
Use Case | First-party analytics | Advertising & attribution |
Privacy Level | High | Lower (requires permission) |
Key Features:
Shared across all apps from the same developer
No ATT consent required
Persistent until all vendor apps are deleted
Automatically generated by iOS
IDFV Attribution Setup
Automatic Fallback
Apptrove's SDK automatically uses IDFV when IDFA is unavailable:
SDK first attempts to collect IDFA
Falls back to IDFV if IDFA is not available
Enables attribution between same-vendor apps
Campaign URL Configuration
texthttps://click.apptrove.io/c/{app_id}?click_id={click_id}&idfv={IDFV}&site_id={publisher_id}
Cross-Promotion Attribution
IDFV is ideal for promoting apps within your own app portfolio:
Ad Display: Show ads for your other apps
Install Attribution: Match IDFV between ad click and install
Use Cases: Email campaigns, push notifications, in-app promotions.
Why Use IDFV for Testing
Works without ATT consent
Remains stable across test installations
Privacy compliant
Setup Steps
Navigate to Apptrove account settings
Register device using IDFV
Enable test mode for the device
Perform test installations
Important Limitations
Same Vendor Only: Attribution only works between apps from the same Apple Developer account
Reset Condition: IDFV changes if all vendor apps are deleted and reinstalled
Privacy Compliance: Cannot combine IDFV with other data for cross-vendor tracking
We are delighted to have assembled a world-class team of experienced professionals who are ready to take care of your queries and answer any questions you may have.
Feel free to reach out to us at any time by emailing us at support@apptrove.com or by using the in-platform chat feature. We'd love to hear from you!
