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.
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
| 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 bcookie, bscookie, lidc, li_gc, li_mc, JSESSIONID, li_at, lang, liap |
| 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 | bcookie 1 year, bscookie 1 year, lidc 24 hours, li_gc 6 months, li_mc 6 months (LinkedIn table) |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- First request sets bcookie and bscookie
- Cookies sent on every LinkedIn request, including via Insight Tag pixel
- 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
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
bcookie | string | None | UUID | stable 1 year |
bscookie | string | None | signed id | stable 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
| Type | Example | Apps |
|---|---|---|
| ads | An advertiser sees that the same browser clicked a LinkedIn ad, read a pricing page and later signed up. | LinkedIn Insight Tag |
| analytics | A marketer measures how many unique people reached a webinar page, not just how many page views. | LinkedIn Campaign Manager |
| social | You open a LinkedIn post logged out, then log in, and LinkedIn can link the two visits to one person. | |
| enterprise | A recruiter dashboard counts unique visitors to a careers page, using the browser ID across visits. | None named |
| security | A sudden jump of requests with one browser ID helps LinkedIn catch scraping from that browser. | |
| media | A 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
| 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
bcookie, bscookie, lidc, li_gc, li_mc listed in LinkedIn's cookie table.
Related capabilities
Related
- LinkedIn ad sync cookies (UserMatchHistory, AnalyticsSyncHistory, lms_ads, li_sugr, _guid). Can match your browser to ad partners' records so ads can follow you
- LinkedIn anti-abuse cookies (li_bapfcc, li_odapfcc, li_apfcdc, spectroscopyId, fid, fcookie). Can check your browser for bots and add a device fingerprint to your visit
Sources
How well checked: Based on official documentation.