Yes. In the EU, EEA and UK, the LinkedIn Insight Tag generally requires prior consent before it loads, sets cookies or sends website visitor data to LinkedIn for advertising, conversion tracking, retargeting or website demographics.
The reason is simple.
The LinkedIn Insight Tag is not just a neutral analytics script. It is part of LinkedIn's advertising infrastructure. It helps advertisers measure conversions, build website retargeting audiences and understand the professional attributes of website visitors.
LinkedIn's own developer documentation describes conversion tracking as an analytical function powered by the LinkedIn Insight Tag. It also explains that advertisers deploy the Insight Tag JavaScript snippet across their website to track conversions or retarget users on any page where the tag is installed.
Source: LinkedIn conversion tracking documentation
In practice, that means the Insight Tag should normally be treated as a Marketing or Advertising tracker, not as strictly necessary technology.
The safest rule is:
Do not fire the LinkedIn Insight Tag until the visitor has granted marketing consent.
This guide explains why the LinkedIn Insight Tag usually requires consent, what it does, which cookies and identifiers are involved, how it differs from ordinary analytics, and how to configure it correctly.
Disclaimer: This article is general information, not legal advice. Consent requirements depend on your technologies, purposes, vendors and implementation.
Related guides
- Does Meta Pixel Require Consent?, a companion guide covering Meta advertising pixel consent
- Does Google Analytics Require Consent?, covering GA4 consent requirements
- Does Microsoft Clarity Require Consent?, covering Clarity Consent Mode and cookies
- GDPR Cookie Consent Requirements, complete guide for websites and businesses
- Google Consent Mode v2 Requirements, complete guide for websites and agencies
Why B2B Marketers Often Underestimate This Tracker
The LinkedIn Insight Tag is especially common on B2B websites.
That makes sense.
If you sell to companies, LinkedIn Ads can be one of the most attractive channels. The Insight Tag helps answer questions such as:
- Which LinkedIn campaigns drive leads?
- Which website pages convert best?
- Can we retarget people who visited our pricing page?
- What job titles, industries or company sizes are visiting the site?
- Which audiences should we use for future campaigns?
For marketers, this is useful.
For privacy teams, it is also sensitive.
The Insight Tag is not only counting page views. It is connected to advertising measurement, retargeting and professional demographic insights. It can help LinkedIn connect website behavior with LinkedIn's advertising ecosystem.
That is why it should be handled more like the Meta Pixel than like a basic traffic counter.
For a similar advertising-pixel analysis, see our guide on Does Meta Pixel Require Consent?
What the LinkedIn Insight Tag Actually Does
The LinkedIn Insight Tag is a JavaScript tag that advertisers add to their website.
LinkedIn says it is used for conversion tracking, and its conversion tracking documentation explains that conversions are actions a member takes that are valuable to a business. This can include actions such as submitting a form, completing a purchase, requesting a demo or visiting an important page.
Source: LinkedIn conversion tracking documentation
The Insight Tag supports several advertising use cases:
- Conversion tracking
- Campaign performance measurement
- Website visitor retargeting
- Matched Audiences
- Website Demographics
- Enhanced conversion tracking
- First-party click ID tracking
- Deduplication with LinkedIn Conversions API
LinkedIn's website visitor retargeting documentation says advertisers can match website visitors to members on LinkedIn to enable further engagement. It also says advertisers can use website retargeting with LinkedIn professional demographic segments for more refined targeting.
Source: LinkedIn website visitors retargeting documentation
That is the key privacy point.
The Insight Tag is not just measuring your website. It is helping connect website behavior with LinkedIn advertising capabilities.
Does the LinkedIn Insight Tag Use Cookies?
Yes. The LinkedIn Insight Tag can use cookies and other identifiers.
LinkedIn's conversion tracking API documentation refers to a setting called firstPartyTrackingEnabled. When first-party tracking is enabled, the Insight Tag attempts to drop a first-party cookie on the advertiser's domain if the page URL contains the first-party tracking ID.
Source: LinkedIn conversion tracking documentation
LinkedIn also documents enhanced conversion tracking and first-party click IDs. It explains that enhanced conversion tracking automatically appends a click ID parameter called li_fat_id to landing page URLs when a user clicks a LinkedIn ad and is redirected to the advertiser's landing page.
Source: LinkedIn enabling click IDs documentation
LinkedIn's Conversions FAQ describes LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID, also known as li_fat_id, as LinkedIn's first-party cookie click ID. It says this click ID allows the tag to use first-party cookie tracking and can improve conversion tracking accuracy.
Source: LinkedIn Conversions FAQ
In addition to first-party click ID tracking, LinkedIn-related tracking can involve cookies and identifiers such as:
| Cookie or identifier | Typical purpose | Typical category |
|---|---|---|
li_fat_id | LinkedIn first-party ads tracking click ID used for conversion tracking | Marketing |
UserMatchHistory | LinkedIn advertising and matching history | Marketing |
li_sugr | Probabilistic matching and advertising-related identification | Marketing |
AnalyticsSyncHistory | Analytics and sync history for LinkedIn advertising services | Marketing or Analytics |
bcookie | Browser identifier used by LinkedIn services | Marketing or functional depending on context |
bscookie | Secure browser identifier used by LinkedIn services | Marketing or functional depending on context |
lidc | Routing and session-related LinkedIn cookie | Functional in LinkedIn context, but may appear with LinkedIn services |
li_gc | Stores LinkedIn cookie consent preference | Functional or consent preference |
Cookie behavior can vary depending on configuration, region, browser restrictions, account settings and whether enhanced conversion tracking is enabled.
The practical takeaway is still clear:
The LinkedIn Insight Tag is not a cookieless, strictly necessary script. It is an advertising and measurement tag that can use cookies and identifiers.
Why the LinkedIn Insight Tag Usually Requires Consent
The consent question has two layers.
The first is cookie consent under ePrivacy-style rules and UK PECR.
The second is GDPR or UK GDPR.
You often need to satisfy both.
ePrivacy and UK PECR
European cookie rules focus on storing or accessing information on the user's device.
If the technology is not strictly necessary for providing the website service requested by the user, prior consent is generally required.
The LinkedIn Insight Tag is not necessary for your website to load, display content or process basic user actions. It is used for advertising measurement, conversion tracking, retargeting and audience insights.
That makes it non-essential.
The UK ICO explains that organisations using cookies and similar technologies must explain what they are used for and make sure users understand the consequences of allowing them.
Source: ICO cookies and similar technologies guidance
The CNIL also states that, generally, before depositing or reading cookies or other trackers, publishers must inform users of the purpose, obtain consent and provide a way to refuse.
Source: CNIL analytics guidance
For the LinkedIn Insight Tag, the ePrivacy conclusion is usually straightforward.
Do not place or read LinkedIn advertising cookies and identifiers before the visitor has consented.
GDPR and UK GDPR
GDPR becomes relevant because the Insight Tag can involve personal data processing.
Depending on configuration, the tag may contribute to processing involving:
- Page URLs visited
- Referrer information
- Browser and device information
- IP address
- Conversion events
- Click IDs
- Campaign attribution data
- Matching against LinkedIn members
- Website retargeting audiences
- Professional demographic reporting
The more the tag is used for retargeting, profiling or audience building, the stronger the GDPR relevance becomes.
LinkedIn's own website visitor retargeting documentation says advertisers can match website visitors to members on LinkedIn to enable further engagement.
Source: LinkedIn website visitors retargeting documentation
That is not just anonymous analytics.
It is advertising-related matching and audience activation.
For a broader explanation of GDPR and ePrivacy consent requirements, see our guide on GDPR Cookie Consent Requirements.
Should the LinkedIn Insight Tag Be Analytics or Marketing?
For most websites, classify the LinkedIn Insight Tag as Marketing or Advertising.
Some CMPs may place conversion measurement under Analytics or Performance, but the Insight Tag is closely tied to LinkedIn Ads, retargeting and campaign optimization.
A practical categorization looks like this:
| Use case | Recommended CMP category |
|---|---|
| LinkedIn Ads conversion tracking | Marketing |
| Website retargeting audiences | Marketing |
| Website Demographics for ad optimization | Marketing or Advertising |
| Enhanced conversion tracking | Marketing |
| Campaign attribution | Marketing or Performance, depending on CMP model |
| Pure aggregated B2B traffic insights without audience activation | Analytics, but review carefully |
The safest choice is usually Marketing.
Why?
Because the user is not merely consenting to site performance measurement. They are consenting to LinkedIn advertising measurement and potentially audience building.
This matters for banner design.
If your banner lets users reject marketing cookies but the LinkedIn Insight Tag still fires under analytics, you may be creating a compliance gap.
LinkedIn Insight Tag vs Google Analytics
Google Analytics and the LinkedIn Insight Tag both help measure website activity, but they are not the same type of tool.
| Question | LinkedIn Insight Tag | Google Analytics |
|---|---|---|
| Main purpose | Advertising attribution, conversion tracking, retargeting and demographics | Website measurement and event analytics |
| Connected to ad platform | Yes, LinkedIn Ads | Often, especially with Google Ads integrations |
| Retargeting use | Core use case | Possible through Google Ads integration |
| Professional profile matching | LinkedIn ecosystem relevance | No LinkedIn-style professional graph |
| Typical CMP category | Marketing | Analytics, sometimes Marketing if ads features are enabled |
| Consent required in EU/UK | Generally yes | Generally yes |
| Strictly necessary | No | Usually no |
The LinkedIn Insight Tag is closer to a marketing pixel than a neutral analytics tool.
If you already require consent for Meta Pixel, TikTok Pixel or Google Ads conversion tracking, the same logic should usually apply to LinkedIn Insight Tag.
For a dedicated analytics comparison, see our guide on Does Google Analytics Require Consent?
LinkedIn Insight Tag vs Microsoft Clarity
LinkedIn Insight Tag and Microsoft Clarity both collect website behavior signals, but they serve different business purposes.
Microsoft Clarity is primarily a behavioral analytics and UX tool. It helps with heatmaps, session recordings and user experience analysis.
LinkedIn Insight Tag is primarily an advertising and conversion measurement tool. It helps LinkedIn advertisers measure campaigns, retarget website visitors and understand audience demographics.
| Question | LinkedIn Insight Tag | Microsoft Clarity |
|---|---|---|
| Main purpose | Advertising measurement and retargeting | UX and behavioral analytics |
| Typical category | Marketing | Analytics |
| Retargeting | Yes | Not the primary purpose |
| Session recordings | No | Yes |
| Professional audience insights | Yes, through LinkedIn ecosystem | No |
| Consent required in EU/UK | Generally yes | Generally yes |
| Best consent category | Marketing | Analytics |
Both should usually be consent-controlled.
The difference is the category.
LinkedIn Insight Tag usually belongs under Marketing. Microsoft Clarity usually belongs under Analytics.
For a dedicated Clarity analysis, see our guide on Does Microsoft Clarity Require Consent?
The B2B Misconception: "It Is Only Company Data"
Many B2B marketers assume LinkedIn advertising data is less sensitive because the audience is professional.
That is a mistake.
GDPR applies to personal data about individuals, including people acting in a professional capacity.
A visitor's job title, employer, industry or seniority may be business-related, but it can still relate to an identifiable person. Website behavior can also reveal interests, intent and buying-stage signals.
This is why B2B tracking still needs privacy controls.
If your website uses the Insight Tag to retarget people who visited pricing pages, demo pages or product pages, that is behavioral advertising activity even if the product is sold to companies.
The fact that the visitor is a professional does not remove consent obligations.
LinkedIn Advertising and Recent Regulatory Context
LinkedIn's advertising data practices have been under regulatory scrutiny.
In October 2024, the Irish Data Protection Commission announced a 310 million euro fine against LinkedIn Ireland following an inquiry into LinkedIn's processing of personal data for behavioral analysis and targeted advertising of LinkedIn members.
Source: Irish DPC press release on LinkedIn fine
This decision was about LinkedIn's own processing of member data, not a simple rule that every Insight Tag implementation is unlawful.
Still, it is relevant context.
It shows that behavioral analysis and targeted advertising are not low-risk categories under EU data protection law. If your website uses LinkedIn's advertising infrastructure, you should treat consent, transparency and lawful basis carefully.
Do not overstate the point.
The DPC fine does not mean you cannot use LinkedIn Ads or the Insight Tag.
It means advertising-related data processing needs a solid legal basis and clear transparency.
Can You Use the LinkedIn Insight Tag Without Consent?
For EU, EEA and UK visitors, you generally should not fire the LinkedIn Insight Tag before consent.
The tag is used for advertising measurement and retargeting. It can use cookies, click IDs and matching signals. It is not required for the website to function.
That makes it difficult to justify without prior consent in consent-first jurisdictions.
There may be edge cases where a server-side or restricted setup avoids certain cookies or limits processing. But that does not automatically remove consent obligations. You still need to consider whether information is being stored or accessed on the user's device, whether personal data is processed, and whether the purpose is advertising or profiling.
For most websites, the practical answer is:
Block the LinkedIn Insight Tag by default. Fire it only after marketing consent.
What About LinkedIn Conversions API?
LinkedIn Conversions API is a server-side way to send conversion data to LinkedIn.
LinkedIn says advertisers can use Insight Tag conversions, Conversions API and CSV conversions, and recommends sending conversions through both the Insight Tag and Conversions API for a more complete view of the customer journey.
Source: LinkedIn Conversions API use case documentation
Server-side tracking does not automatically avoid consent requirements.
This is a common misconception.
If your website collects data from the user, stores identifiers, reads click IDs or sends conversion events to LinkedIn for advertising measurement, you still need to evaluate consent and lawful basis.
A server-side setup may reduce browser exposure, improve reliability or help with deduplication. It does not make advertising attribution consent-free.
If Conversions API uses li_fat_id, event IDs, email addresses or other user identifiers, review the setup carefully.
How to Use the LinkedIn Insight Tag Compliantly
A compliant setup is mostly about control.
The tag should not run until the user has made a valid marketing consent choice.
Use this checklist.
1. Classify LinkedIn Insight Tag as Marketing
In your CMP, create or use a Marketing category.
The LinkedIn Insight Tag should usually sit there, not under Strictly Necessary.
A clear vendor description might say:
LinkedIn Insight Tag helps us measure LinkedIn Ads performance, track conversions, understand website demographics and create advertising audiences.
2. Block the Tag Before Consent
The LinkedIn Insight Tag should not load until marketing consent is granted.
This includes:
- Direct script installation
- Google Tag Manager installation
- Other tag manager installation
- WordPress plugin injection
- Server-side setups that depend on client-side identifiers
If the tag fires before the user chooses, the banner is not doing its job.
3. Configure Google Tag Manager Correctly
Many sites install LinkedIn Insight Tag through GTM.
That is fine, but only if the GTM trigger respects consent.
Common mistakes include:
- Firing the tag on all pages
- Firing the tag on DOM ready before the banner choice
- Using a consent banner but not connecting it to GTM
- Blocking only visible scripts while GTM still injects LinkedIn
- Treating LinkedIn as Analytics when the visitor rejected Marketing
If your CMP sends consent events into the data layer, make sure the LinkedIn tag fires only when marketing consent is true.
For a broader explanation of consent signaling and tag behavior, see our guide on Google Consent Mode v2 Requirements.
4. Check Enhanced Conversion Tracking
LinkedIn enhanced conversion tracking may append li_fat_id to landing page URLs and use first-party cookie tracking.
LinkedIn says enhanced conversion tracking automatically appends li_fat_id to landing page URLs when a user clicks a LinkedIn ad, and this is enabled by default for recently created Insight Tags.
Source: LinkedIn enabling click IDs documentation
Review whether this is enabled in your Campaign Manager setup.
If first-party click ID tracking is active, include it in your consent and cookie review.
5. Review Retargeting Audiences
If you use Website Retargeting or Matched Audiences, the consent case becomes even stronger.
LinkedIn says advertisers can match website visitors to members on LinkedIn to enable further engagement.
Source: LinkedIn website visitors retargeting documentation
That should be disclosed as advertising or retargeting, not hidden under generic analytics wording.
6. Update Your Privacy and Cookie Policy
Your policy should explain:
- That you use LinkedIn Insight Tag
- That it supports LinkedIn Ads measurement
- That it may support conversion tracking
- That it may support retargeting and audience creation
- That LinkedIn may receive information about website visits and conversions
- What cookies or identifiers may be used
- How users can withdraw consent
- Where users can learn more about LinkedIn's processing
7. Respect Withdrawal
Users must be able to change their decision later.
If a visitor withdraws marketing consent, your CMP should stop firing the Insight Tag and prevent new LinkedIn advertising cookies or identifiers from being set.
8. Test the Implementation in the Browser
Do not rely only on documentation.
Test what happens.
Before consent:
- Clear cookies.
- Open the site in a clean browser.
- Do not interact with the banner.
- Reject marketing cookies.
- Check whether requests to LinkedIn domains occur.
- Check whether LinkedIn-related cookies appear.
- Check whether GTM fired the Insight Tag.
After consent:
- Grant marketing consent.
- Confirm the Insight Tag fires.
- Confirm expected conversion tracking behavior.
- Confirm consent withdrawal stops future firing.
Look for domains and endpoints such as:
snap.licdn.compx.ads.linkedin.comlinkedin.comlicdn.com
The exact network requests may vary by implementation.
Common LinkedIn Insight Tag Consent Mistakes
Mistake 1: Treating the Tag as Analytics Only
LinkedIn Insight Tag is often used for advertising attribution and retargeting.
That usually belongs under Marketing, not simple analytics.
Mistake 2: Firing LinkedIn Through GTM on Every Page
If the GTM tag fires before the CMP records marketing consent, the implementation is likely wrong.
Mistake 3: Forgetting About Enhanced Conversion Tracking
li_fat_id and first-party click ID tracking can affect cookie and consent analysis.
Review the Campaign Manager settings, not just the script snippet.
Mistake 4: Not Disclosing Retargeting
If you use LinkedIn Matched Audiences or website retargeting, say so clearly.
Users should not have to infer that "analytics" also means advertising audience creation.
Mistake 5: Ignoring Server-Side Conversions
Conversions API can still involve advertising-related personal data.
Server-side does not automatically mean consent-free.
Mistake 6: Assuming B2B Data Is Not Personal Data
Professional data can still be personal data.
A person's job title, employer and website behavior can still relate to an identifiable individual.
Mistake 7: Not Testing the Reject State
Many implementations are only tested after accepting cookies.
The reject and no-interaction states are where most compliance issues appear.
Recommended Cookie Policy Wording
You should adapt this wording to your actual setup and legal review.
A clear description could look like this:
We use the LinkedIn Insight Tag to measure the performance of our LinkedIn advertising campaigns, track conversions and understand how visitors interact with our website after viewing or clicking LinkedIn ads. LinkedIn may use cookies, click IDs and similar technologies to help attribute conversions, create advertising audiences and provide aggregated website demographics. The LinkedIn Insight Tag only runs when you give marketing consent. You can withdraw your consent at any time through our cookie settings.
If you use website retargeting, add:
We may also use LinkedIn Insight Tag data to create retargeting audiences so we can show relevant ads to people who have visited our website.
If you use Conversions API, add:
We may send certain conversion events to LinkedIn server-side to measure advertising performance. Where required, this is controlled by your marketing consent choice.
LinkedIn Insight Tag Consent Checklist
Use this before going live.
| Requirement | Status |
|---|---|
| LinkedIn Insight Tag listed in CMP | To verify |
| Vendor categorized as Marketing | To verify |
| Tag blocked before marketing consent | To verify |
| GTM trigger respects consent state | To verify |
| No LinkedIn ad requests before consent | To verify |
| No LinkedIn cookies or IDs before consent | To verify |
li_fat_id and enhanced conversion tracking reviewed | To verify |
| Retargeting audiences disclosed | To verify |
| Conversions API reviewed if used | To verify |
| Privacy policy updated | To verify |
| Cookie policy updated | To verify |
| Consent withdrawal available | To verify |
| Reject state tested | To verify |
| No-interaction state tested | To verify |
Frequently Asked Questions
Yes, generally. In the EU, EEA and UK, the LinkedIn Insight Tag usually requires prior consent because it is used for advertising measurement, conversion tracking, retargeting and audience insights. It is not strictly necessary for the website to function.
The LinkedIn Insight Tag can be used as part of a GDPR-compliant setup, but only if the website owner implements it correctly. That usually means prior consent, clear disclosure, correct CMP categorization, proper contractual terms, and controls for withdrawal.
Usually Marketing. It can provide analytics-style reporting, but it is strongly connected to LinkedIn Ads, conversion tracking, retargeting and website demographics.
LinkedIn-related tracking may involve identifiers and cookies such as li_fat_id, UserMatchHistory, li_sugr, AnalyticsSyncHistory, bcookie, bscookie, lidc and li_gc.
Actual cookies can vary depending on configuration, region, browser and account settings.
li_fat_id is LinkedIn's first-party ads tracking click ID. LinkedIn says enhanced conversion tracking can append this click ID to landing page URLs when a user clicks a LinkedIn ad, allowing the tag to use first-party cookie tracking and improve conversion tracking accuracy.
Source: LinkedIn Conversions FAQ
For EU, EEA and UK visitors, you generally should not load it before marketing consent. If the tag loads before consent, it may set cookies, send advertising data or enable retargeting before the visitor has agreed.
Yes. LinkedIn's documentation says advertisers can match website visitors to members on LinkedIn to enable further engagement.
Not by itself. Google Consent Mode is designed for Google tags. You can use consent states in GTM to control LinkedIn firing, but you must explicitly configure the LinkedIn tag to respect marketing consent.
It can. If Conversions API sends advertising-related personal data, click IDs or conversion events to LinkedIn, you need to evaluate consent, lawful basis and transparency. Server-side tracking does not automatically remove consent requirements.
Yes, in the sense that both are advertising pixels used for conversion tracking, retargeting and ad optimization. For consent purposes, LinkedIn Insight Tag should usually be treated similarly to Meta Pixel and other marketing trackers.
US rules are different. In many US state privacy regimes, the main issue may be sale, sharing, targeted advertising and opt-out rights rather than prior opt-in consent. If the tag is used for targeted advertising or cross-context behavioral advertising, it may need to be included in opt-out controls and honored when a user sends Global Privacy Control.
Conclusion
The LinkedIn Insight Tag generally requires consent in the EU, EEA and UK.
That is because it is used for advertising measurement, conversion tracking, retargeting and professional audience insights. It can use cookies, click IDs and matching signals. It is not necessary for the website to function.
The best practical setup is:
- Classify LinkedIn Insight Tag as Marketing.
- Block it before marketing consent.
- Make sure GTM or other tag managers do not fire it too early.
- Review enhanced conversion tracking and
li_fat_id. - Disclose retargeting and conversion tracking clearly.
- Review Conversions API if used.
- Allow users to withdraw consent.
- Test the reject and no-interaction states.
The most important point is this:
A cookie banner does not make the LinkedIn Insight Tag compliant unless it actually prevents the tag from firing before consent.
Concentio can automatically detect LinkedIn Insight Tag, classify it as a marketing tracker and block it until consent is granted.