Cookie library

The bcookie cookie

LinkedIn’s browser identifier, set when the Insight Tag is present and accompanied by an unusually long list of companions.

Set by
LinkedIn
Classified as
advertising
Typical expiry
1 year
Storage
Third-party

What it does

`bcookie` identifies a browser to LinkedIn. It arrives with `bscookie` for secure contexts, `lidc` for routing, `li_sugr` for probabilistic matching, and `UserMatchHistory` and `AnalyticsSyncHistory` for identifier synchronisation.

The Insight Tag also writes first-party identifiers through the page (`ln_or` and `_lc2_fpi`), which a domain-based audit would attribute to your own site.

What to write in a cookie declaration

Declare the LinkedIn set as a group with LinkedIn named as provider, and include the first-party ones. The group is long enough that omitting half of it is noticeable.

FieldValue
Namebcookie
ProviderLinkedIn
Purpose categoryadvertising
Consent categoryMarketing
Expiry1 year (vendor default)
StorageThird-party

Treat the expiry as indicative

The value above is the vendor’s documented default. Vendors change configuration and several browsers cap script-written lifetimes. Record what repeated scans observe on your own site, with the browser, region, path and interaction state; one run is not authoritative for every visitor.

Common questions

Why does LinkedIn set so many cookies?

Because the tag serves several purposes at once: identification, routing, matching and synchronisation with LinkedIn’s advertising systems. Each has its own cookie.

Sources and verification

Verified on . Product-behaviour statements were checked against the current implementation and tests. The links below are the verification basis recorded for this article. They support the stated facts, not a legal conclusion for every site or configuration; recheck changing vendor behaviour before relying on it in production.

See what your own site is loading

A browser scan reports the requests and storage it observed during the sampled journey. Use configured workspace scans to compare the states and pages that matter to your implementation.