Probabilistic install matching (IP plus user agent)
An MMP guesses which ad click led to an install by matching IP, device model and OS version within a short time window.
In one line
Can guess which ad led to your install by matching your IP, phone model and timing
An MMP guesses which ad click led to an install by matching IP, device model and OS version within a short time window.
Without IDs, the vendor matches the click (IP, UA, language, OS) with the first app open from the same signals, usually within hours. Apple treats this as fingerprinting for ATT-denied users.
What it can and can't do
What the user does: You tap an ad, install the app, then open it within a short window
It can
- Match your ad click to your first open using IP, phone model and system version
- Credit the right ad when no exact install code is available
- Work for installs outside Google Play on Android and, with gaps, on iPhone
It cannot
- Match you for sure; it is a guess and can be wrong
- Match you on a long delay; it needs a short time window
- Match you on iPhone when iCloud Private Relay hides your Safari IP
- See anything else about you from this step alone
How it differs between platforms: Android has a reliable referrer for Play installs, so guessing is a backup. On iPhone it is often the main method, though Private Relay breaks it.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Partial |
| First version | Not available | Not available |
| Permission or entitlement | Not listed | Not listed |
| Protection level | none | none |
| How access is granted | none | none |
| What the user sees | Not listed | Not listed |
| How long it lasts | Not listed | Not listed |
| How to take it back | Not listed | Not listed |
| Store policy | Play does not ban it; used as fallback to referrer | App Review 5.1.2(i): fingerprinting prohibited for tracking; vendors limit it to non-user-level modeling |
| API | MMP click redirect + SDK first open | MMP click redirect + first open |
| Notes | Used when Install Referrer is not available, e.g. non-Play installs. | iCloud Private Relay hides the Safari IP, breaking matches; Apple leaves enforcement to review. |
Data you get
What comes back: Match score
Shape: object
How often: single, within a window
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
match window | integer | hours | usually 1 to 24 | Not listed |
signals | list | None | IP, UA, language, OS, model | Not listed |
Technical limits
- Accuracy falls with shared Wi-Fi, VPN, Private Relay
- Not allowed on iOS for denied users per Apple
The story
What it is
A guess about which ad led to an install, made by comparing network and device details.
For you
You tap an ad, install the app and the ad firm quietly matches the two by network address and device details. You never see this. It can be wrong, especially on shared Wi-Fi.
For makers
When IDs are blocked, ad firms still need to say which campaign worked. Matching in a short window gives an estimate for budgets. Apple treats it as fingerprinting when the person said no to tracking.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | A game studio checks which of five video ads brought a new player, using the click and first open from the same Wi-Fi. | AppsFlyer, Adjust |
| shopping | A retailer measures whether an influencer link caused app installs. | None named |
| games | A mobile game pays an ad network per install, and the match decides who gets paid. | None named |
| security | Fraud teams spot clicks that claim installs by guessing from the same address at odd hours. | None named |
| travel | A booking app estimates which search ad led to its first booking in the app. | None named |
| analytics | A marketing team compares the guess to Apple's own aggregate ad reports. | None named |
Risks
- Can be wrong
- Works around no-tracking choice
Android and iPhone in short
- Android: Allowed more freely, though Google Play rules limit ad use.
- iPhone: Apple warns it counts as fingerprinting for people who tapped Ask App Not to Track.
Good uses and abuse
Legitimate uses
- Last-resort attribution on non-Play installs
Known abuse
- Joining a click to a device without consent
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 20 | Rough identifying entropy, when known |
History
- 2021-04, iPhone iOS 14.5: ATT: IP+UA matching not allowed for denied users; vendors restrict or rebrand
- 2021-09, iPhone iOS 15: iCloud Private Relay hides Safari IP from apps' redirectors
Related capabilities
Related
- Fingerprinting ban and ATT enforcement. Can't rebuild your identity from phone details after you refuse tracking on iPhone
- Deferred deep links. Can send you to the right screen after install, using how you reached the store
Same idea on the web
- Referer and Origin headers. Can tell which site you came from, usually just the site name, not the page
Sources
How well checked: Inferred from related behavior.