Skip to main content
Cookie reference · LinkedIn Insight

The li_sugr cookie

A LinkedIn advertising cookie used for probabilistic matching when a browser can't be tied to a LinkedIn member directly.

li_sugr at a glance

Cookie name
li_sugr
Vendor
LinkedIn Insight
Category
Advertising
Party
Third-party
Typical duration
90 days
Set on
.linkedin.com
Value format
Opaque identifier (format not documented by vendor)
Name match
Exactly li_sugr

What the li_sugr cookie does

li_sugr is used to make a probabilistic match of a user's identity. LinkedIn uses it for advertising when the browser can't be matched to a LinkedIn member directly, for example when the visitor isn't signed in.

LinkedIn categorizes it as personalized advertising, with a 90 day lifetime. It's set on .linkedin.com, typically when the LinkedIn Insight Tag loads on a site.

What TagPipes observed

1.0%

of sites scanned set it (422 of 41,162)

90 days

median observed lifetime

TagPipes scanned 41,162 public websites between August 11, 2026 and September 13, 2026, loading up to three pages per site in a real browser as a first-time visitor. li_sugr was present on 422 of them.

It was set as a first-party cookie on 0 sites and as a third-party cookie on 422. A site can count in both. Where it was stored as a persistent cookie, the median lifetime we recorded was 90 days.

Often found alongside

Percentage of sites with li_sugr where the other cookie was also present.

Technologies detected on the same sites

  • LinkedIn Insight on 97% of them (1.1% of all sites scanned)
  • Google Analytics on 93% of them (55% of all sites scanned)
  • Google Fonts on 74% of them (78% of all sites scanned)
  • Meta Pixel on 70% of them (13% of all sites scanned)
  • The Trade Desk on 67% of them (1.5% of all sites scanned)

Aggregate figures across all sites scanned. Websites of TagPipes customers are excluded, no individual site is named, and cookie values are never read or stored. Snapshot dated September 13, 2026.

How to check for li_sugr on a website

  1. Open the site in Chrome, then open DevTools (F12, or Cmd+Option+I on a Mac).
  2. Go to the Application tab and expand Cookies in the left panel.
  3. Select each domain listed there and look for li_sugr. The Expires column shows when it will be deleted.
  4. If it is not there, reload the page. Many cookies are only set after a tag has loaded, and some only after a visitor has made a consent choice.

Sources

Purpose, duration and value format checked against the vendor documentation above on . The figures under What TagPipes observed are TagPipes scan data from September 13, 2026, not values documented by the vendor. Vendors change their cookies, and sites can configure their own names and lifetimes. Browse all cookies.

Know every cookie your own site sets

TagPipes Pulse identifies the cookies dropped on your site and flags unclassified or miscategorized ones. Shield builds your cookie declaration from a real scan rather than a questionnaire.

TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Rawsoft's expertise is technology, not law; please confirm any regulatory interpretation with your own counsel.