Conversions APIs (server to server)
Advertisers send purchase and signup events from their server straight to ad platforms.
In one line
Can send your purchases and sign ups to ad platforms from the advertiser's server
Advertisers send purchase and signup events from their server straight to ad platforms.
Meta, TikTok, LinkedIn, Snap and Google accept server events with hashed email, phone, IP and click IDs, bypassing browser blocking. Meta dedups with event_id inside 48 hours. The person sees nothing and the browser cannot stop it.
What it can and can't do
What the user does: Nothing on your side. It happens after you buy or sign up on a site
It can
- Send events straight from a company's server to ad platforms
- Include scrambled email, phone and click ID details
- Count sales even if your browser blocks tracking scripts
It cannot
- Be seen or blocked in your browser, since it never touches your device
- Match you without the advertiser having your details or click ID
- Cover sites that have not set it up
- Be turned off with a browser setting
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 1 | 2008-12-11 | Server side, browser independent |
| Edge | Supported | 1 | Not listed | Server side, browser independent |
| Firefox | Supported | 1 | 2004-11-09 | Server side, browser independent |
| Safari | Supported | 1 | 2003-06-23 | Server side, browser independent |
| Safari on iPhone | Supported | 1 | 2007-06-29 | Server side, browser independent |
| Chrome on Android | Supported | 1 | Not listed | Server side, browser independent |
| Samsung Internet | Supported | 1 | 2013-04-27 | Server side, browser independent |
How a site asks for it
| API | POST graph.facebook.com/{pixel}/events; Google Ads API upload; LinkedIn Conversions API |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Event windows 7 to 90 days depending on platform |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: Event with hashed identifiers
Shape: object
How often: per event
No individual data fields. The signal is the access itself.
Technical limits
- Requires data the advertiser holds (email, click ID)
- Consent rules still apply
- Hashed identifiers are still personal data (FTC Jul 2024)
- Matching rate limited by hash quality
The story
What it is
Companies send your purchase and signup events from their servers straight to ad platforms.
For you
You never see it. After you buy something or sign up, the company's own server sends a note to Meta, TikTok, Snap or Google, often with scrambled email and phone. Your browser cannot block it.
For makers
Browser blockers and iOS rules cut pixel data, so server events win back lost sales. Platforms use the scrambled IDs and click IDs to match events to ads. Matching improves ad targeting and the numbers in reports.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | A shop sends each order to Meta from its server so ads still get credit when the shopper used a blocker. | Shopify, Meta Ads |
| games | A game site sends Meta and TikTok a note when a player signs up or pays, so campaigns find more players like them. | Roblox, Zynga |
| analytics | A marketing team compares pixel and server events and removes duplicates with an event ID. | Segment |
| shopping | A retailer sends in store and phone orders to ad platforms, tied to a customer email. | Nike, Sephora |
| enterprise | A B2B firm sends a signed contract event to LinkedIn and Google weeks after the first click. | Salesforce, HubSpot |
| payments | A payment company sends a successful charge event, so ad platforms count only paid sales. | Stripe |
| security | The same stream lets platforms see fake sign ups, which helps them cut ad fraud. | None named |
Risks
- Cannot be blocked in your browser
- Hashed email still identifies you
What the platform says
- Meta: Conversions API. Meta pitches it as a way to share web and app events directly from a business server for more reliable measurement.
Good uses and abuse
Legitimate uses
- Resilient measurement
Known abuse
- Evading browser protections, silent sharing of purchases
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 | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
A real example: LinkedIn
LinkedIn Conversions API accepts hashed email and click IDs server side.
History
- 2020-07, all: Facebook Conversions API launched after iOS 14 changes
- 2024-07, all: FTC states hashing does not make data anonymous
Related capabilities
Related
- Meta Pixel. Can tell Meta about your visits and actions on a site that uses the pixel
- Google enhanced conversions. Can match a scrambled email or phone from your checkout to a Google account
- Server side tagging. Can send your activity to the site's own server first, then on to ad vendors
Sources
- Meta Conversions API
- FTC: No, hashing still doesn't make your data anonymous
- LinkedIn Conversions API
How well checked: Based on official documentation.