Related service:
Rikard Jonsson
Rikard Jonsson is Founder & CEO of Hey Sid and a five-time entrepreneur with a background in B2B SaaS, sales, and brand building. He believes B2B marketing is overcomplicated and writes about going back to basics: visibility, positioning, and consistent presence among the accounts that matter.
LinkedIn Insight Tag: How to Install It and Use It for B2B Attribution
Quick answer: The LinkedIn Insight Tag is a JavaScript snippet that enables conversion tracking, website retargeting, and Website Demographics. Installation takes minutes through Google Tag Manager. The part most guides skip: LinkedIn's default snippet fires on page load, which is not compliant in the EEA, where the tag must be blocked until a visitor gives advertising consent.
What the LinkedIn Insight Tag does
The LinkedIn Insight Tag, sometimes called the LinkedIn pixel, is a lightweight piece of JavaScript you add to your website. Once installed it unlocks three capabilities that are otherwise unavailable.
Conversion tracking connects actions on your site, such as a demo request or a content download, back to the LinkedIn campaign that produced them. Without it, LinkedIn reports clicks and you guess at the rest.
Website retargeting lets you build audiences from site visitors and serve ads to them on LinkedIn, including audiences based on specific pages visited.
Website Demographics is the capability with no equivalent elsewhere. Because the tag can associate a visit with a LinkedIn member profile when the visitor is signed in, it reports the professional characteristics of your traffic in aggregate: seniority, function, industry, company size. Learning that a quarter of your visitors are senior managers in your target industry is a different class of information from a bounce rate.
The tag collects page URLs, referrers, IP address, device and browser metadata, and timestamps. That last point matters for the compliance section below, because this is advertising data by any reading.
Installing the LinkedIn Insight Tag
Three routes, in ascending order of control.
Method | Setup effort | Consent control | Best for |
|---|---|---|---|
Direct code in site template | Lowest | Poor, fires on page load by default | Sites with no EEA traffic and no tag manager |
Google Tag Manager | Moderate | Strong, conditional firing on consent signal | Any site with EEA traffic; the recommended route |
Platform integration (HubSpot, CMS) | Lowest | Inherited from the platform, needs verifying | Teams already centralising tags in one platform |
Direct code. Copy the snippet from Campaign Manager and paste it before the closing body tag on every page. Simple, and the hardest to manage consent around, so we would not recommend it for EEA traffic.
Google Tag Manager. The standard approach. Create a new tag using the LinkedIn Insight Tag template, add your Partner ID from Campaign Manager, and set the trigger. This is the route that makes consent handling straightforward, which is why it is worth the extra ten minutes.
Platform integration. HubSpot, and most major CMS and marketing platforms, offer a native integration where you paste the Partner ID into a settings field. Convenient, though you inherit whatever consent behaviour the platform implements, so verify it rather than assuming.
After installing, check Campaign Manager's tag status. It should move from unverified to active once traffic passes through, usually within a day. If it stays unverified, the usual causes are the tag firing on only some pages, a consent tool blocking it entirely, or a Partner ID mismatch.
One further check worth building into the process: confirm the tag is present on the pages that matter most, not merely on the homepage. Retargeting audiences built from pricing, product, and case study pages are considerably more useful than a general all-visitors audience, and they only exist if the tag is firing there.
Setting up conversion tracking
Installation alone gives you retargeting and demographics. Conversions need explicit configuration.
URL-based conversions are the simplest. Define a conversion as any visit to a specific page, such as a thank-you or confirmation URL. This works well for form submissions that redirect and requires no additional code.
Event-based conversions fire on a specific action rather than a page load, which is what you need for single-page applications, in-page form submissions, and anything that does not produce a distinct URL. These are configured through GTM triggers or by calling the LinkedIn conversion function directly.
For each conversion, set the attribution window and the conversion value. Both defaults are worth changing. B2B buying cycles routinely exceed the standard window, and leaving conversion value empty makes downstream return calculations impossible.
The click identifier. LinkedIn passes a click ID, li_fat_id, on ad clicks. Capturing it and passing it to your server enables conversion API events, which report conversions server-side rather than relying entirely on the browser. For teams losing data to consent rejection and browser restrictions, this recovers attribution for consented visitors.
The consent problem most guides skip
This section is the one that matters most for European teams, and it is routinely omitted or handled in a sentence.
LinkedIn's default installation snippet loads immediately on page load. Under the ePrivacy Directive, storing or accessing information on a visitor's device requires prior consent unless the tracker is strictly necessary for a service the visitor requested. The Insight Tag does not meet that exemption; it is an advertising tracker. LinkedIn's own marketing documentation states that advertisers using the tag in the EEA must obtain explicit opt-in consent before it fires.
So the default installation is not compliant for EEA traffic. The tag must not execute until a visitor actively accepts advertising cookies.
The Consent-First Install Sequence
Run these steps in this order. Installing first and adding consent later is how sites end up with months of non-compliant collection.
Configure the consent management platform first. Advertising and targeting must be a separate, rejectable category in the banner, with rejection available in one click.
Install the tag through GTM, not directly. Direct installation makes conditional firing considerably harder.
Gate the tag on the advertising consent signal. With Google Consent Mode v2, set the tag to fire only when ad_storage is granted. Without GTM, use your CMP's script-blocking capability.
Verify no cookies are set before consent. Load the site in a clean browser, reject the banner, and confirm no LinkedIn cookies appear. This is the test regulators apply.
Update the privacy policy. Name the Insight Tag specifically, list what it collects, state the purpose, and explain how to withdraw consent.
Document the transfer basis. Data is processed on LinkedIn's US infrastructure, so the appropriate transfer safeguards need to be in place and recorded.
Only then verify the tag in Campaign Manager. Confirm it fires correctly for consented visitors.
One frequent error worth naming: the li_gc cookie records LinkedIn's own internal consent state and is not a GDPR consent mechanism for your site. Your consent platform remains the only valid basis. Teams occasionally point to li_gc as evidence of compliance, which it is not.
The practical consequence of doing this correctly is that you will see fewer conversions than a non-compliant setup would report. That is the accurate number.
Using the tag for B2B attribution
Here the tag's limits become the point. The Insight Tag reports what LinkedIn can see: clicks, site visits, and conversions it can connect to an ad interaction. It does not see the deal that closes eleven months later after four people from the same account engaged across three channels.
That gap is why LinkedIn programs get cut while working. Across the 150+ B2B companies we work with, the biggest predictor of whether a marketing program survives is not campaign performance. It is whether the team can prove business impact and defend the budget internally. Campaigns generating strong engagement still get cut when nobody can connect them to pipeline.
The Insight Tag is a component of that proof, not the proof itself. Three layers make it usable:
Layer one, the tag. Conversion tracking and Website Demographics. Tells you which campaigns produced site actions and who is visiting.
Layer two, the CRM. Passing LinkedIn lead and conversion data into HubSpot, Salesforce, or Dynamics connects a form fill to an account and eventually to an opportunity. Without this, everything stays at the lead level.
Layer three, multi-touch attribution. Tools such as Dreamdata and Factors.ai stitch advertising exposure, site behaviour, and CRM records into an account-level view, which is the only level at which B2B buying groups make sense.
For the strategic side of this, including which attribution model suits account-based programs and what to report to leadership, see our guide to account-based marketing attribution. This article covers the implementation; that one covers the measurement thinking.
What Website Demographics is genuinely good for
The most underused capability, and the one that needs no attribution stack.
Because it reports aggregate professional attributes rather than individuals, Website Demographics answers questions that are otherwise expensive to answer. Are the people reading our content the people who buy? Which industries are over-represented relative to our ICP? Did the traffic from that campaign match the audience we targeted?
Used as a targeting feedback loop rather than a reporting curiosity, it will tell you within weeks whether a campaign is reaching the right professional profile, long before conversion data reaches significance.
Where Hey Sid fits
Hey Sid runs person-based advertising to named individuals and reports at account level, connecting engagement back into HubSpot so sales can see which target accounts have been warmed before the first conversation. That addresses the same problem this article is about, from the other direction: rather than reconstructing account-level insight from click data, the program is built around named accounts from the start.
It suits mid-sized B2B companies with long cycles, a defined account list, and the internal need to show which accounts are progressing. It does not suit teams wanting to operate their own stack, or organizations that require direct click-to-close attribution for every euro. If it fits, see how it works or book a demo.
Common mistakes to avoid
Installing before configuring consent. For EEA traffic the default snippet is non-compliant, and retrofitting consent leaves a documented gap.
Treating li_gc as your consent record. It is LinkedIn's internal state, not a legal basis for your site.
Leaving conversion values empty. Return calculations become impossible without them.
Accepting the default attribution window. B2B cycles routinely outrun it, so conversions get attributed to nothing.
Installing on some pages only. Retargeting audiences and demographics both degrade with partial coverage.
Expecting the tag to prove pipeline. It measures site actions. Pipeline proof needs CRM and account-level attribution on top.
Conclusion and next steps
Install the LinkedIn Insight Tag through Google Tag Manager, gate it behind advertising consent before it ever fires, verify that no cookies are set on rejection, then configure conversions with realistic windows and real values. Use Website Demographics as a fast feedback loop on targeting quality, and treat the tag as the first of three layers rather than an attribution system in itself.
For cost and targeting decisions, see our LinkedIn ads playbook. For format selection, see our comparison of document ads and video ads. For the inbox formats and their EU restriction, see our conversation ads guide. For attribution strategy rather than implementation, see our account-based marketing attribution guide.
If you would rather have account-level advertising and reporting run for you, explore how Hey Sid works or read more in our resources.
FAQ
What is the LinkedIn Insight Tag?
It is a JavaScript snippet added to your website that enables three LinkedIn advertising capabilities: conversion tracking, website retargeting, and Website Demographics, which reports the professional attributes of your visitors in aggregate. It is sometimes called the LinkedIn pixel, and it collects page URLs, referrers, IP address, device metadata, and timestamps.
How do I install the LinkedIn Insight Tag?
The recommended route is Google Tag Manager: create a tag using the LinkedIn template, add your Partner ID from Campaign Manager, and set the trigger. You can also paste the snippet directly into your site or use a native platform integration such as HubSpot. GTM is preferable because it makes consent-conditional firing straightforward.
Does the LinkedIn Insight Tag require GDPR consent?
Yes, for EEA visitors. The tag sets advertising cookies and does not qualify as strictly necessary, so the ePrivacy Directive requires prior consent. LinkedIn's own documentation states that advertisers using it in the EEA must obtain explicit opt-in consent before the tag fires, which means the default snippet must be blocked until a visitor accepts advertising cookies.
What is the difference between the LinkedIn Insight Tag and the LinkedIn pixel?
They are the same thing. LinkedIn's official name is the Insight Tag, while pixel is the informal term carried over from other advertising platforms. Some teams also use pixel to refer specifically to the conversion-tracking function, but there is only one tag and it handles conversions, retargeting, and demographics together.
Can the LinkedIn Insight Tag prove pipeline impact?
Not on its own. It measures site actions connected to ad interactions, which stops well short of a B2B deal involving several stakeholders over many months. Proving pipeline needs the tag plus CRM integration to connect leads to accounts, plus an account-level attribution layer such as Dreamdata or Factors.ai to stitch exposure and outcomes together.
