Skip to Content
Platform.Ontology

Cookie syncing

Ad companies swap IDs through redirects so each can recognise the same person.

Used to track youTracking across apps and sitesBefore the visitWeb browsersBefore you visitWhile you use it

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

BrowserStatusFirst versionReleasedNote
ChromeSupported12008-12-11Works while 3P cookies are allowed
EdgeSupported1Not listedNone
FirefoxPartial12004-11-09Partitioned so syncs are siloed per site
SafariPartial12003-06-23Blocked, uses link decoration or login IDs
Safari on iPhonePartial12007-06-29None
Chrome on AndroidSupported1Not listedNone
Samsung InternetSupported12013-04-27None

How a site asks for it

APIImage or iframe request to partner /sync?uid=...; 302 redirects; postMessage
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsMapping tables persist at vendors for months to years
How to take it backClear site data, browser privacy settings
Inside an iframeNot 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

TypeExampleApps
adsA 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
analyticsA measurement company uses synced IDs to count people who saw an ad on one site and bought on another.Nielsen, comScore
gamesA free browser game loads ads through partners that sync IDs so bidders value a player more.CrazyGames, Poki
mediaA video site sells ad space with synced IDs, which raises the price for known viewers.Hulu, YouTube
shoppingA shopper's cart visit is shared through synced IDs so a related ad shows on a news site.Criteo
securityResearchers 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

ScoreValueMeaning
Sensitivity4 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2019-05, all: Papadopoulos et al. (WWW 2019) quantified cookie syncing in the wild

Sources

How well checked: Based on official documentation.

On this page