SKAN crowd anonymity tiers
Apple withholds detail from postbacks when too few installs came from a campaign.
In one line
Can't get much detail when too few people installed from an ad
Apple withholds detail from postbacks when too few installs came from a campaign.
Protects individuals in small groups: low install counts get less detail. Small advertisers lose signal first.
What it can and can't do
What the user does: Nothing. Apple applies the rules by itself
It can
- Send full detail for large campaigns
- Send a 3 or 4 digit campaign ID in higher tiers
- Send a detailed score in higher tiers
It cannot
- See the exact limits; Apple keeps them secret
- Get detail for small campaigns at tier 0
- Pick the tier; Apple decides
How it differs between platforms: iPhone only (iOS 16.1 and later). Not used on Android.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Not supported | Supported |
| First version | Not available | iOS 16.1 |
| Permission or entitlement | Not listed | Not listed |
| Protection level | none | none |
| How access is granted | not-exposed | 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 | None listed | None listed |
| API | Not listed | Not listed |
| Notes | Not applicable. | Four tiers (0 to 3). Higher tiers unlock 3 or 4 digit source identifiers and fine conversion values; tier 0 gives the least data. Thresholds are secret and Apple does not publish them. |
Data you get
What comes back: Crowd anonymity tier 0 to 3
Shape: enum
How often: decided per postback by Apple
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
source-identifier digits | integer | digits | 2 to 4 | Not listed |
conversion value | enum | None | none, coarse, or fine by tier | Not listed |
Technical limits
- Thresholds undocumented
- Applied independently to each postback
The story
What it is
Apple hides detail from ad reports when too few people came from a campaign.
For you
You never see it. If you are one of few people who installed from a niche ad, Apple makes sure the report cannot point to you.
For makers
The more installs a campaign has, the more detail the report shows. Small advertisers lose the most detail first, so many test big first or combine campaigns.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A new indie studio runs a tiny test and gets only a basic count back. | None named |
| ads | A big ad network sees full values for large campaigns, but only a coarse one for small ones. | Meta, Google Ads |
| shopping | A boutique retailer merges its campaigns into one to reach a higher detail tier. | None named |
| analytics | A measurement team models what small campaigns would look like at scale. | Singular |
| security | Small groups cannot be singled out, which protects rare users. | None named |
| developer | A developer reads postbacks and finds blank values due to low volume. | None named |
Risks
- Small advertisers lose signal
- Data may be missing
Android and iPhone in short
- Android: Android has no equal system.
- iPhone: Part of SKAdNetwork 4 on iOS 16.1 and later.
What the platform says
- Apple: SKAdNetwork crowd anonymity. Reports include less detail when a campaign has few installs, to protect people in small groups.
Good uses and abuse
Legitimate uses
- Prevents re-identification
Known abuse
- Advertisers split campaigns to game thresholds
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2022-10, iPhone iOS 16.1: Tiered data disclosure introduced in SKAN 4
Related capabilities
Related
- SKAdNetwork 4 (postbacks). Can tell an ad network an ad led to an install, in a delayed report
Sources
How well checked: Inferred from related behavior.