Cookie syncing
Ad companies swap IDs through redirects so each can recognise the same person.
In one line
Can let ad companies swap IDs so each recognizes you across sites
Ad companies swap IDs through redirects so each can recognise the same person.
Vendor A redirects the browser to vendor B with its own ID in the URL, so B stores a mapping A to B. Repeated across dozens of partners it builds the ID graph that real time bidding relies on. Academic crawls found it on a large share of sites.
What it can and can't do
What the user does: Nothing. It happens when a page loads ads or trackers
It can
- Pass your IDs between ad companies through quick redirects
- Match your visits across many sites
- Build one profile from several companies' cookies
It cannot
- Work where third party cookies are blocked, as in Safari and Firefox by default
- Continue once you clear cookies
- Know your name without a login or an email hash
- Work between browsers or devices unless a login links them
How it differs between platforms: Safari and Firefox block most of this by default. Chrome still allows third party cookies.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 1 | 2008-12-11 | Works while 3P cookies are allowed |
| Edge | Supported | 1 | Not listed | None |
| Firefox | Partial | 1 | 2004-11-09 | Partitioned so syncs are siloed per site |
| Safari | Partial | 1 | 2003-06-23 | Blocked, uses link decoration or login IDs |
| Safari on iPhone | Partial | 1 | 2007-06-29 | None |
| Chrome on Android | Supported | 1 | Not listed | None |
| Samsung Internet | Supported | 1 | 2013-04-27 | None |
How a site asks for it
| API | Image or iframe request to partner /sync?uid=...; 302 redirects; postMessage |
| 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 | Mapping tables persist at vendors for months to years |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: Pair of vendor IDs
Shape: hash
How often: per page view with partner tags
No individual data fields. The signal is the access itself.
Technical limits
- Needs a third-party cookie or another stable ID on each side
- Blocked by Safari ITP and Firefox TCP; Chrome allows it with third-party cookies on
- Browsers cannot distinguish a sync from an ordinary pixel
The story
What it is
Ad companies swap IDs through quick redirects so each can recognise the same person.
For you
You never see it. When you load a page, your browser is sent through several ad companies in a blink. Each one passes along its ID for you, so they can all say that they know you.
For makers
Real time ad auctions need every bidder to know who is on the page. Syncing lets them match their private IDs with each other. The result is a web of IDs that makes ads follow people, and a large share of sites take part.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | A news page loads, and a dozen ad companies swap IDs so they can bid on you within 100 milliseconds. | Google Ad Manager, The Trade Desk |
| analytics | A measurement company uses synced IDs to count people who saw an ad on one site and bought on another. | Nielsen, comScore |
| games | A free browser game loads ads through partners that sync IDs so bidders value a player more. | CrazyGames, Poki |
| media | A video site sells ad space with synced IDs, which raises the price for known viewers. | Hulu, YouTube |
| shopping | A shopper's cart visit is shared through synced IDs so a related ad shows on a news site. | Criteo |
| security | Researchers studied syncing to show how many sites share one ID. | None named |
Risks
- Builds a web of IDs that follows you
- Many companies learn your ID
Good uses and abuse
Legitimate uses
- Frequency capping across vendors
- Measurement matching
Known abuse
- Cross-vendor profile merging without the person knowing
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 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
- 2019-05, all: Papadopoulos et al. (WWW 2019) quantified cookie syncing in the wild
Related capabilities
Related
- Universal IDs: UID2, ID5, RampID. Can give you a shared ad ID based on your login email, with no cookie
- Third-party cookies by browser (Nov 2026). Can recognise you across sites with embedded cookies, unless your browser blocks them
Sources
How well checked: Based on official documentation.