LinkedIn ad sync cookies (UserMatchHistory, AnalyticsSyncHistory, lms_ads, li_sugr, _guid)
Cookies that sync LinkedIn IDs with ad partners and match visitors by probability.
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
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Supported | Not available | None |
| Edge | Supported | Not available | None |
| Firefox | Supported | Not available | None |
| Safari | Supported | Not available | None |
| Safari on iPhone | Supported | Not available | None |
| Chrome on Android | Supported | Not available | None |
| Samsung Internet | Supported | Not available | None |
How a site asks for it
| API | Set-Cookie UserMatchHistory, AnalyticsSyncHistory, lms_ads, lms_analytics, li_sugr, _guid, li_giant, ln_or |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | UserMatchHistory 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 back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Ad pixel loads on a partner or LinkedIn page
- Sync cookies are written
- 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
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
li_sugr | string | None | UUID | 90 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
| Type | Example | Apps |
|---|---|---|
| ads | You 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 |
| analytics | An advertiser sees one person counted across LinkedIn and Google ads, instead of two people, which cleans up reports. | Google Ads, LinkedIn Campaign Manager |
| shopping | A shopper looked at a pair of shoes at work, and sees a related ad on a LinkedIn feed later that day. | LinkedIn Ads |
| security | The same ID helps spot one browser acting in ways no real person would, like thousands of page views. | None named |
| games | A person plays LinkedIn Games like Queens or Zip logged out, and the ad sync cookies still tag the browser for ad matching. | LinkedIn Games |
| media | A 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
| 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 |
A real example: LinkedIn
All listed in LinkedIn's cookie table.
Related capabilities
Related
- LinkedIn Insight Tag (conversion pixel on other sites). Can tell LinkedIn when you visit or act on an advertiser's site
- Third party ID sync cookies in LinkedIn's table. Can set partner cookies that let ad companies match you to their records
Sources
How well checked: Based on official documentation.