Skip to Content
Platform.Ontology

LinkedIn ad sync cookies (UserMatchHistory, AnalyticsSyncHistory, lms_ads, li_sugr, _guid)

Cookies that sync LinkedIn IDs with ad partners and match visitors by probability.

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

In one line

Can match your browser to ad partners' records so ads can follow you

Cookies that sync LinkedIn IDs with ad partners and match visitors by probability.

Keep identifier matches between LinkedIn and ad tech partners. li_sugr (90 days) is a probabilistic match for visitors who are not logged in; _guid (90 days) links to Google Ads.

What it can and can't do

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

It can

  • Store IDs in your browser that link LinkedIn with ad partners
  • Match your visit to ad partner records by probability
  • Keep the match for weeks or months until the cookie expires
  • Help show targeted ads on other sites

It cannot

  • Work if you block third party cookies or clear cookies
  • Know who you are without a LinkedIn login or a match from a partner
  • See inside other apps or your device
  • Cross over to a browser or device where the cookie is missing, unless a login links them

How it differs between platforms: Safari and Firefox block many of these cookies by default; Chrome currently allows them unless you choose otherwise.

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 UserMatchHistory, AnalyticsSyncHistory, lms_ads, lms_analytics, li_sugr, _guid, li_giant, ln_or
How access is grantednone
What the user seesNone (no browser prompt)
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsUserMatchHistory 30 days, AnalyticsSyncHistory 30 days, lms_ads 30 days, lms_analytics 30 days, li_sugr 90 days, _guid 90 days, li_giant 7 days, ln_or 1 day
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Ad pixel loads on a partner or LinkedIn page
  2. Sync cookies are written
  3. Partners exchange IDs through redirect syncs

Data you get

What comes back: Partner match IDs
Shape: string
How often: every 30 days or per sync

FieldTypeUnitRangePrecision
li_sugrstringNoneUUID90 days

Technical limits

  • ln_or is from Oribi, 1 day
  • Cookie durations are from the cookie table summary

The story

What it is

Cookies that help LinkedIn match you with ad partners, even when you are not logged in.

For you

You never see these tiny files. They sit in your browser for about three months and help LinkedIn and ad partners agree that a visitor is the same person. They are why an ad can seem to follow you.

For makers

LinkedIn needs to link its IDs to those of Google and other ad partners to sell and measure ads across sites. A probabilistic match for visitors who are not logged in means it guesses at who you are from device clues. That widens the audience a campaign can reach.

Where you see it

TypeExampleApps
adsYou read a news site, then see a LinkedIn ad for a tool you looked at, because sync cookies helped match you across sites.LinkedIn Ads, Google Ads
analyticsAn advertiser sees one person counted across LinkedIn and Google ads, instead of two people, which cleans up reports.Google Ads, LinkedIn Campaign Manager
shoppingA shopper looked at a pair of shoes at work, and sees a related ad on a LinkedIn feed later that day.LinkedIn Ads
securityThe same ID helps spot one browser acting in ways no real person would, like thousands of page views.None named
gamesA person plays LinkedIn Games like Queens or Zip logged out, and the ad sync cookies still tag the browser for ad matching.LinkedIn Games
mediaA publisher with a LinkedIn tag sells its audience to advertisers, using the synced IDs to prove the readers are real.Forbes, Business Insider

Risks

  • Follows you across sites
  • Guess based matching for logged out visitors

Good uses and abuse

Legitimate uses

  • Ad measurement

Known abuse

  • Cross-site profile joins

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

All listed in LinkedIn's cookie table.

Sources

How well checked: Based on official documentation.

On this page