What is the ln_or cookie?
ln_or is an HTTP cookie associated with LinkedIn that appears on a website when the site embeds a LinkedIn widget, share button, or other LinkedIn element (for example a "Share" or "Follow" plugin, or a LinkedIn tracking pixel used for analytics or advertising).
It is typically set by the LinkedIn script loaded from the host website's own domain rather than directly from LinkedIn.com, which is why it is often flagged under the statistics/analytics category during a cookie scan.
What data it stores
The exact value stored in ln_or is not documented in detail by LinkedIn publicly; it varies and is used internally by LinkedIn's systems to correlate interaction events with their widgets.
The collected data is sent to LinkedIn/Microsoft servers and may be linked, directly or indirectly, to user or session identifiers depending on whether a LinkedIn account is active in the browser.
What it is used for
Its main purpose is to let LinkedIn measure how visitors to a website interact with its embedded content and widgets – for example how many people click a "Share on LinkedIn" button or view an embedded post.
For the website owner, this cookie provides no directly usable data; the benefit is indirect, through the proper functioning of the LinkedIn widget displayed on the page.
Does it require consent?
In CookieFix's classification, ln_or falls under the statistics (analytics) category. Under the ePrivacy Directive (transposed in Romania via Law 506/2004) and the GDPR, cookies in this category are not strictly necessary for the website to function and require the visitor's prior consent before being set.
Website operators must disclose it explicitly in their cookie policy, place it in the correct consent banner category, and avoid loading it automatically before the visitor accepts.
How to block or delete ln_or
A visitor can delete or block this cookie through browser settings (Chrome, Firefox, Edge, Safari), via per-site cookie management options, or by using extensions that block LinkedIn scripts.
- Manually deleting cookies stored for the LinkedIn domain or the visited website's domain.
- Blocking third-party scripts through browser privacy settings.
- Disabling LinkedIn widgets from a personal LinkedIn account, where available.
For website owners, the most practical solution is using a CMP such as CookieFix, which automatically blocks the LinkedIn widget script until the visitor consents to the statistics category, avoiding non-compliant cookie placement.
Frequently asked questions
It is not malware, but it collects data about visitor interactions with LinkedIn widgets, which is why it is classified as a statistics cookie and requires consent.
The typical observed duration is 1 day, after which the cookie expires automatically and may be set again if the LinkedIn widget reloads.
Yes, since it is classified as a statistics cookie, ln_or is not strictly necessary and requires the visitor's prior consent under the ePrivacy rules and GDPR.
It usually appears through an embedded LinkedIn widget, share button, or embedded content added by the site itself or a third-party plugin.