Skip to Content
Platform.Ontology

LinkedIn identity and session cookies (bcookie, bscookie, lidc, li_gc, li_mc)

Cookies that give each browser and member a stable ID on LinkedIn and on sites with its tag.

Used to track youTracking across apps and sitesCookiesWeb browsersBefore you visitWhen the page loadsWhen you are signed inAfter you leave the site

In one line

Can give your browser and account a steady ID on LinkedIn and partner sites

Cookies that give each browser and member a stable ID on LinkedIn and on sites with its tag.

bcookie and bscookie identify the browser for one year, lidc routes traffic for 24 hours, li_gc and li_mc store consent and marketing state for 6 months. They link logged out and logged in activity.

What it can and can't do

What the user does: Nothing. It happens when you open LinkedIn or a site with the LinkedIn tag

It can

  • Give your browser a stable ID that stays between visits
  • Link that ID to your member account when you are signed in
  • Keep your session and route you to the right server
  • Tell LinkedIn which sites with its tag you visited

It cannot

  • Follow you after you clear cookies or use a fresh browser profile
  • Work where third party cookies are blocked, such as Safari and Firefox by default
  • Know your identity on other sites unless you are signed in to LinkedIn
  • See your activity in other apps

How it differs between platforms: Safari and Firefox block third party cookies by default, which limits the tag on other sites. 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 bcookie, bscookie, lidc, li_gc, li_mc, JSESSIONID, li_at, lang, liap
How access is grantednone
What the user seesNone (no browser prompt)
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsbcookie 1 year, bscookie 1 year, lidc 24 hours, li_gc 6 months, li_mc 6 months (LinkedIn table)
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. First request sets bcookie and bscookie
  2. Cookies sent on every LinkedIn request, including via Insight Tag pixel
  3. li_at and JSESSIONID are the logged in session

Data you get

What comes back: Browser IDs
Shape: string
How often: set once, refreshed on visit

FieldTypeUnitRangePrecision
bcookiestringNoneUUIDstable 1 year
bscookiestringNonesigned idstable 1 year

Technical limits

  • Third party cookie blocking limits bcookie on other sites
  • Durations are from LinkedIn's cookie table via summary (not rechecked)

The story

What it is

Cookies that give your browser a steady ID on LinkedIn and on sites that use its tag.

For you

You do not see these. A tag called bcookie gives your browser an ID for about a year, and others keep your consent and routing. They connect your logged out visits with the time you log in.

For makers

A stable ID lets LinkedIn count visitors, show the right ads and link activity before and after sign in. It is the base that other tracking pieces plug into. Advertisers use it to measure who saw an ad and who later acted.

Where you see it

TypeExampleApps
adsAn advertiser sees that the same browser clicked a LinkedIn ad, read a pricing page and later signed up.LinkedIn Insight Tag
analyticsA marketer measures how many unique people reached a webinar page, not just how many page views.LinkedIn Campaign Manager
socialYou open a LinkedIn post logged out, then log in, and LinkedIn can link the two visits to one person.LinkedIn
enterpriseA recruiter dashboard counts unique visitors to a careers page, using the browser ID across visits.None named
securityA sudden jump of requests with one browser ID helps LinkedIn catch scraping from that browser.LinkedIn
mediaA news site with a LinkedIn tag learns which readers also work at target companies for a sponsor.Fast Company, Harvard Business Review

Risks

  • Joins logged out and logged in activity
  • Lasts a year

Good uses and abuse

Legitimate uses

  • Login session
  • Load balancing
  • Security

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

bcookie, bscookie, lidc, li_gc, li_mc listed in LinkedIn's cookie table.

Sources

How well checked: Based on official documentation.

On this page