Skip to Content
Platform.Ontology

Third party ID sync cookies in LinkedIn's table

Ad partner cookies (Adobe, ID5, Xandr, Yahoo, Microsoft, Google) set through LinkedIn's ad stack.

Used to track youTracking across apps and sitesCookiesWeb browsersBefore you visitWhen the page loadsAfter you leave the site

In one line

Can set partner cookies that let ad companies match you to their records

Ad partner cookies (Adobe, ID5, Xandr, Yahoo, Microsoft, Google) set through LinkedIn's ad stack.

Shows LinkedIn acting as a demand side platform: other ad networks write IDs that LinkedIn uses to resolve people across sites. Observation data is kept at most 90 days per LinkedIn.

What it can and can't do

What the user does: Nothing. It happens when you visit LinkedIn or a site using LinkedIn ads

It can

  • Store cookies from ad partners such as Adobe, ID5, Xandr, Yahoo, Microsoft and Google
  • Swap IDs between LinkedIn and those partners
  • Help partners recognize you on other sites

It cannot

  • Work where third party cookies are blocked
  • Follow you after you clear cookies
  • Know your name without a login at a partner
  • Reach another device unless a login links it

How it differs between platforms: Safari and Firefox block most of these by default. Chrome allows them unless you change settings.

Browser support

BrowserStatusFirst versionNote
ChromeSupportedNot availableNone
EdgeSupportedNot availableNone
FirefoxSupportedNot availableNone
SafariSupportedNot availableNone
Safari on iPhoneSupportedNot availableNone
Chrome on AndroidSupportedNot availableNone
Samsung InternetSupportedNot availableNone

How a site asks for it

APISet-Cookie aam_uuid, demdex, ID5, Xandr, TripleLift, Rubicon, Magnite, Claritas, MUID, ms_click_id, _gcl_*, ar_debug
How access is grantednone
What the user seesNone (no browser prompt)
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsVaries by vendor (see LinkedIn table)
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Ad slot or pixel loads vendor tags
  2. Vendor sets ID cookies
  3. IDs are matched in LinkedIn's identity graph

Data you get

What comes back: Partner IDs
Shape: list
How often: per sync

FieldTypeUnitRangePrecision
idslistNone10 or more vendorsvaries

Technical limits

  • Exact graph is not public
  • In Designated Countries off-site collection only with consent (per LinkedIn)

The story

What it is

Ad partners write their own IDs in your browser, and LinkedIn uses them to recognise you.

For you

You never see it. Partners like Adobe, Google and Yahoo place small ID files in your browser as part of LinkedIn's ad system. LinkedIn can then match you across other sites, for up to about three months of data.

For makers

This makes LinkedIn work like a buyer of ads on the wider web, not just its own site. Matching IDs lets it reach the same person on other sites and prove results. It also gives partners a larger view of people.

Where you see it

TypeExampleApps
adsA business sees its LinkedIn ads reach the same person who later sees its display ad on a news site.LinkedIn Ads
analyticsA marketer sees one combined count of people reached across LinkedIn and partner ad networks.Adobe Analytics
mediaA publisher sells ad space that LinkedIn bids on, using synced IDs to price the visitor.Yahoo, Xandr
shoppingA shopper browsing a store gets matched to a partner ID, so a related ad appears elsewhere.None named
securityPartners use the shared IDs to spot invalid traffic that appears under many IDs at once.None named
gamesA person reads a news site on a game break, and an ad partner ID helps LinkedIn show a related ad to the same person.LinkedIn Games

Risks

  • Builds a profile across many sites
  • Many companies hold your ID

Good uses and abuse

Legitimate uses

  • Ad delivery and measurement

Known abuse

  • Cross-site identity resolution

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

A real example: LinkedIn

Cookie table lists these vendor cookies; LinkedIn help page describes off-LinkedIn identity resolution with probabilistic matching.

Sources

How well checked: Based on official documentation.

On this page