Server-side conversions APIs
The advertiser's server sends purchase or signup events to ad platforms, with hashed email or phone.
In one line
Can send your purchases and signups from its server to ad platforms
The advertiser's server sends purchase or signup events to ad platforms, with hashed email or phone.
Bypasses on-device tracking limits: the server sends identifiers and click IDs directly, so the platform matches events to ad clicks.
What it can and can't do
What the user does: You buy, sign up, or tap an ad, then the app's server reports it
It can
- Send events to ad platforms with a scrambled email or phone number
- Match them to your ad click with click IDs, IP address and browser details
- Work around limits on the phone itself
- Report even when the phone shows no tracking
It cannot
- Count as not tracking on iPhone; Apple still counts sharing for ads, even server to server
- Send data without a matching ID or click
- Skip the tracking prompt on iPhone if it shares for ads
How it differs between platforms: Both systems allow it. Apple counts server to server sharing for ads as tracking, so the prompt rules apply.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| 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 | Data safety: sharing; consent required where law demands | ATT counts server-side sharing as tracking when linked to third-party data; 5.1.2 |
| API | Meta Conversions API, Google Ads enhanced conversions, TikTok Events API, MMP S2S | Same APIs |
| Notes | Matching uses hashed email, phone, click IDs (gclid, gbraid, fbclid) and IP/UA. | Apple's ATT definition covers sharing data for ads even if sent server to server. |
Data you get
What comes back: Event + hashed identifiers
Shape: object
How often: per event
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
em / ph | hash | SHA-256 | Not listed | Not listed |
click ID | string | None | Not listed | Not listed |
event_time | integer | s | Not listed | Not listed |
Technical limits
- Needs the user's data on the advertiser's server
- Consent and ATT rules still apply
The story
What it is
A company's server tells an ad platform about your purchase, using a scrambled email, to match it to an ad.
For you
You never see it. After you buy something, the store's own server may quietly tell Meta or Google that you bought, using a scrambled version of your email.
For makers
Browsers and phones now block many on device signals, so makers send events from their own servers with click IDs and hashed contact data. That goes around on device limits and often gives better matching than the old way.
Where you see it
| Type | Example | Apps |
|---|---|---|
| shopping | You buy shoes after an Instagram ad. The store's server sends the purchase and a hashed email to Meta so the ad gets credit. | Nike, Shein |
| games | A game's server reports your first in app purchase to the ad network, no matter what you did on the device. | Supercell, Zynga |
| banking | A bank sends 'account opened' to ad platforms, using a hashed email, to find similar customers. | Chime |
| ads | An advertiser uploads a customer list, and the platform matches it to find lookalikes. | Meta, Google Ads |
| travel | A travel site sends a booking event from its server after the page closes. | Booking.com |
| security | Servers can filter fake events before they reach ad platforms, which helps fight fraud. | None named |
Risks
- Gets around on device blocks
- Shares hashed contact data
Android and iPhone in short
- Android: Works with Android click IDs and the advertising ID when allowed.
- iPhone: On iOS it still works when ATT is refused, as long as the email is known to the company.
What the platform says
- Google: Enhanced conversions. Send hashed first party data like email to improve measurement while protecting privacy.
- Meta: Conversions API. Share web and app events from your own server directly with Meta.
Good uses and abuse
Legitimate uses
- Measurement resilient to blockers
Known abuse
- Bypassing consent signals
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 5 of 5 | How useful it is to honest apps |
| Friction | 1 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2021-04, iPhone iOS 14.5: Server-side APIs grow as a response to ATT
Related capabilities
Related
- Hashed email and phone identity graphs (UID2, RampID). Can match you across apps and sites using your email or phone, scrambled into an ID
- Meta (Facebook) SDK and app events. Can send your app activity to Meta and match it to your account
Same idea on the web
- Hashed email as identity. Can recognize you across sites by a scrambled version of your email
- Ad click IDs (gclid, fbclid, msclkid and more). Can tag your ad click so a later purchase links back to that exact ad
Sources
How well checked: Based on official documentation.