TL;DR
The LinkedIn Insight Tag sets third-party advertising cookies on websites that include it. These cookies require prior visitor consent under GDPR and the ePrivacy Directive. Without a CMP blocking the script before consent is given, your site is non-compliant.
Why the LinkedIn Insight Tag falls under GDPR
The LinkedIn Insight Tag is a JavaScript snippet provided by LinkedIn to measure advertising conversions and build retargeting audiences. As soon as it loads, it sets several third-party cookies on the visitor's device. These cookies serve advertising purposes and are not strictly necessary for the site to function.
The ePrivacy Directive (Article 5.3) requires prior consent for any non-necessary tracker. GDPR requires that consent be freely given, informed, specific, and unambiguous. The LinkedIn Insight Tag falls under the advertising/targeting category: consent is mandatory before the script activates.
Cookies set by the LinkedIn Insight Tag
- li_gc: LinkedIn's internal consent status (2 years)
- li_sugr: probabilistic matching for cross-device attribution (90 days)
- UserMatchHistory: identifier sync between LinkedIn and advertisers (30 days)
- bcookie / bscookie: LinkedIn browser identifier (2 years)
- AnalyticsSyncHistory: LinkedIn analytics data synchronisation
None of these cookies are strictly necessary for the technical operation of your site. All require prior consent.
How to configure the LinkedIn Insight Tag for GDPR compliance
The logic is the same as for the Meta Pixel or TikTok Pixel: the script must only load after the user explicitly consents to the advertising category.
Method 1: blocking via a CMP (recommended)
Use a consent management platform (CMP) that automatically blocks third-party scripts before consent. With FlowConsent, the LinkedIn script stays inactive until the user accepts the advertising category. Consent proof is recorded automatically.
Method 2: Google Tag Manager with a consent variable
Condition the LinkedIn tag trigger on a consent variable in GTM. The tag only fires if the user has consented to the advertising category. Note: incorrect configuration can cause the tag to fire on the first page load despite the condition.
Method 3: conditional loading in JavaScript
For sites without GTM, load the LinkedIn script only when advertising consent is granted. This approach requires a custom consent storage mechanism on the client side.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Common mistakes and how to avoid them
Script in the <head> with no condition. LinkedIn's default setup places the script directly in the HTML. Without a CMP, it loads on every visit before any consent. Always use a CMP or conditional loading.
GTM without a consent variable. Adding the LinkedIn tag in GTM without a consent-based trigger is equivalent to loading it unconditionally. Set up a consent variable or enable Consent Mode in GTM.
A banner that informs but does not block. Some banners notify users without technically blocking scripts. Check in the browser developer tools (Network tab) that requests to snap.licdn.com do not appear before consent.
LinkedIn missing from the cookie policy. Your cookie policy must list all trackers, including LinkedIn cookies, with their duration and purpose. Any omission is a transparency violation.
Confusing li_gc with GDPR consent. The li_gc cookie stores LinkedIn's internal consent for its own platforms. It is not a GDPR consent mechanism for your site. Your CMP remains the only valid mechanism.
For more on compliance requirements, see our guide on cookie dark patterns prohibited by regulators.
LinkedIn Pixel GDPR compliance checklist
- The LinkedIn Insight Tag is blocked by default until consent is given.
- Consent is collected via a compliant CMP (visible banner, rejection in one click).
- The advertising/targeting category is separate from other categories in the banner.
- The script does not load on refusal or when no response is given.
- The cookie policy lists all LinkedIn cookies with their purpose and duration.
- Consent records are stored with timestamp, visitor ID, and banner version.
- The consent withdrawal mechanism is accessible and functional.
- Consent is renewed every 6 months (ICO/EDPB guidance).
- No LinkedIn cookie is set server-side without consent.
- Configuration is reviewed after every LinkedIn script update.
To measure the impact of your setup on your cookie consent rate, see our dedicated guide.
Conclusion
The LinkedIn Insight Tag is a powerful tool for B2B campaigns, but its default integration violates GDPR and the ePrivacy Directive. The fix is straightforward: a CMP like FlowConsent automatically blocks the script until consent is obtained, with no complex manual configuration.
Check whether the LinkedIn Insight Tag and other third-party scripts are properly blocked on your site using the FlowConsent cookie scanner.
Frequently asked questions
What is the LinkedIn Insight Tag?
The LinkedIn Insight Tag is a JavaScript snippet provided by LinkedIn that measures advertising conversions, builds retargeting audiences, and provides demographic insights about website visitors. It automatically sets third-party cookies as soon as it loads.
Does the LinkedIn Insight Tag require consent?
Yes. The cookies set by the LinkedIn Insight Tag serve advertising purposes and are not strictly necessary. The ePrivacy Directive (Article 5.3) and GDPR require prior, free, informed and active consent before these cookies can be placed.
What happens if the LinkedIn Insight Tag loads without consent?
If the script loads before the user gives consent, the website violates the ePrivacy Directive and GDPR. Data protection authorities (ICO, BfDI, AEPD, etc.) may issue fines. A CMP like FlowConsent automatically blocks the script until consent is obtained.
Is the li_gc cookie a GDPR consent mechanism?
No. The li_gc cookie stores LinkedIn''s internal consent status for its own platforms. It does not constitute a GDPR consent mechanism for your website. Your CMP remains the only valid mechanism for collecting and proving visitor consent.
How to block the LinkedIn Insight Tag before consent?
The recommended method is to use a CMP that automatically blocks third-party scripts before consent. With FlowConsent, the LinkedIn script stays inactive until the user accepts the advertising category. Consent proof is automatically recorded.