What is the li_mc cookie?
li_mc is an HTTP cookie set on the .linkedin.com domain, used by LinkedIn for internal management of cookie consent. It typically appears when a visitor interacts with a site embedding LinkedIn resources (such as a "Share on LinkedIn" button, a profile widget, or a "Follow" plugin) or visits linkedin.com directly.
It is set by LinkedIn Corporation as part of its own privacy-preference infrastructure, not by the hosting website itself.
What data it stores
According to LinkedIn's publicly available information, this cookie stores a marker related to the visitor's consent or preference status for LinkedIn cookies. The exact value format is not documented in detail publicly and may vary; no explicit personal data is known to be stored directly in the cookie.
The data is sent to LinkedIn's (Microsoft's) servers with subsequent requests to the .linkedin.com domain, for as long as the cookie remains active.
What it is used for
The main purpose of li_mc is to let LinkedIn remember a user's cookie-related choice or consent state, avoiding repeated consent prompts on every visit or interaction with LinkedIn widgets.
For a site owner embedding a LinkedIn button or plugin, this cookie is part of the minimal set needed for that functionality (share, login, embed) to work correctly; it does not serve a cross-site advertising tracking role.
Does it require consent?
CookieFix classifies li_mc as strictly necessary, since it supports a functional mechanism (LinkedIn's consent management) rather than profiling or advertising.
- Strictly necessary cookies do not require prior consent under Article 5(3) of the ePrivacy Directive, but they must still be disclosed in the site's cookie policy.
- Site owners should still check exactly which LinkedIn feature is embedded (a simple button vs. a widget with broader tracking), since loading the full LinkedIn SDK can trigger additional analytics or marketing cookies that do require consent.
- It is recommended to document this cookie in the cookie policy and list LinkedIn as a third party.
How to block or delete li_mc
A visitor can manually delete or block li_mc from browser settings (Chrome, Firefox, Edge, Safari – per-site cookie management) or use third-party content-blocking extensions.
For site owners wanting granular control, a consent management platform such as CookieFix can automatically block LinkedIn scripts and widgets until the visitor makes a choice, if the LinkedIn integration is treated as non-essential or a more cautious approach is preferred.
Frequently asked questions
It's an HTTP cookie set on .linkedin.com, used for LinkedIn's internal management of consent and privacy preferences across its platforms.
CookieFix classifies it as strictly necessary, so it doesn't require prior consent, but it must still be disclosed in the site's cookie policy.
The typical duration observed is 6 months from when it's set or last updated.
It can be deleted manually from the browser's privacy settings, in the per-domain cookie section, by searching for .linkedin.com.