# LinkedIn Insight Tag: GTM setup and Consent Mode v2 in the EU

**Author:** Piotr Litwa - GTM & Analytics Specialist
**Published:** 2026-06-19
**URL:** https://piotrlitwa.com/articles/en/linkedin-insight-tag-gtm.html
**Language:** en
**Keywords:** ["linkedin insight tag gtm", "linkedin conversion tracking", "linkedin insight tag consent", "linkedin capi"]

---

The LinkedIn Insight Tag is a JavaScript snippet that tracks conversions, builds retargeting audiences, and reports demographic data about who visits your site. Deploying it through Google Tag Manager takes about ten minutes.

Making it legal in the EU takes longer, and this is where most B2B setups quietly fail.

**Google Consent Mode doesn't control the LinkedIn Insight Tag.** Consent Mode governs Google tags. LinkedIn isn't a Google tag. If your entire consent architecture is built on Consent Mode v2, and you assume it covers everything in your container, the Insight Tag is firing on users who denied consent, right now, and has been since you installed it.

That isn't a theoretical compliance risk. It's a cookie being written, on an identified professional, without a legal basis, in the jurisdiction that fines hardest for exactly this.

This article covers the GTM deployment, the consent gap and how to close it, conversion tracking, and the mistakes I find in most B2B containers.

> **Key Takeaways**
> - Google Consent Mode v2 doesn't govern the LinkedIn Insight Tag. You must gate it in GTM yourself, using consent checks or trigger conditions.
> - The Insight Tag writes cookies (`li_sugr`, `UserMatchHistory`, `lidc`, `bcookie`). All of them require consent in the EU.
> - Partner ID is all you need for the base tag. Conversions are defined in LinkedIn Campaign Manager, not in GTM.
> - LinkedIn's Conversions API (CAPI) is the server-side counterpart and needs the same deduplication discipline as Meta.
> - B2B traffic is low volume and high value, so a broken Insight Tag costs proportionally more than a broken Meta pixel.

## What the Insight Tag actually does

Three jobs, and they are worth separating because people conflate them.

**Conversion tracking.** It reports back to LinkedIn Campaign Manager when someone who clicked your ad completed an action. Without it, LinkedIn's optimisation is blind and you're bidding on clicks rather than outcomes.

**Retargeting audiences.** It builds a pool of site visitors you can target later. In B2B this is often the highest-ROI use, because your ad audience is measured in thousands, not millions.

**Website demographics.** This is the one that is genuinely unique to LinkedIn, and it's why people put up with the rest. It tells you the job titles, company sizes, industries, and seniority of people visiting your site, in aggregate. No other platform can do this, because no other platform knows where its users work.

That third feature is also why the consent question is sharper here than elsewhere. This tag is matching your visitors against a database of real named professionals and their employers.

**Not sure what your container is firing without consent?** The [Free GTM Audit](https://piotrlitwa.com/checkGTM/) checks which tags respect consent and which don't. Enter a URL, get a report in about 10 minutes. No signup.

## GTM setup, step by step

You need one thing before you start: your **Partner ID**. Find it in LinkedIn Campaign Manager under Account Assets, then Insight Tag.

1. In GTM, go to **Tags**, then **New**, then **Tag Configuration**.
2. Choose **LinkedIn Insight Tag** from the community template gallery. It's a verified template, so you don't need custom HTML.
3. Enter your **Partner ID**.
4. Set the trigger. **Do not use All Pages.** See the next section, because this is where the compliance work happens.
5. Save, preview, publish.

That's the whole base tag. There's no conversion configuration in GTM, and this trips people up: **LinkedIn conversions are defined in Campaign Manager**, not in your container. You create a conversion rule there based on a URL pattern or an event, and the Insight Tag reports against it automatically.

If you want event-based conversions rather than URL-based ones, that is where the second tag comes in, and we will get to it.

## The consent gap, and how to close it

Here is the mechanism, precisely.

Google Consent Mode v2 works by passing consent signals to Google tags, which then adjust their own behaviour: a Google tag receiving `ad_storage: denied` will fire a cookieless ping instead of writing a cookie. The tag is consent-aware. It knows what to do when told no.

**The LinkedIn Insight Tag has no such mechanism.** It isn't built by Google, it doesn't read Google's consent signals, and it doesn't have a cookieless mode. It either runs and writes cookies, or it doesn't run. There's no middle state.

So the question isn't "does Consent Mode handle it" (it doesn't). The question is whether *your container* stops the tag from firing at all.

### Option 1: Additional Consent Checks (recommended)

GTM has built-in consent settings on every tag, including community templates.

1. Open the LinkedIn Insight Tag in GTM.
2. Scroll to **Consent Settings** (under Advanced Settings).
3. Set **Additional Consent Checks** to **Require additional consent for tag to fire**.
4. Add `ad_storage` and `ad_user_data`.

Now GTM itself withholds the tag until those signals are granted. The tag never runs for a user who denied. This is clean, native, and auditable, and it works regardless of which CMP you use.

### Option 2: Trigger condition on a consent variable

If your CMP writes consent state into the data layer or a cookie, you can read it into a GTM variable and add it as a trigger condition: fire only when `marketingConsent equals true`.

This works, but it's more fragile. It depends on your CMP firing before the trigger evaluates, and consent timing is the single most common source of tag leakage. I built the [Universal Consent Adapter](https://piotrlitwa.com/uca/) specifically because CMPs are slow and tags are fast, and the gap between them is where compliance quietly breaks.

### How to verify it actually works

Do not trust the configuration. Test it:

1. Open your site in a fresh incognito window.
2. **Deny** consent in the banner.
3. Open DevTools, go to **Application**, then **Cookies**.
4. Look for `li_sugr`, `UserMatchHistory`, `bcookie`, or `lidc`.

If any of them exist, your tag fired despite the denial, and your consent configuration is decorative. This test takes ninety seconds and I have never run it on an unaudited B2B site without finding something.

## Conversion tracking that actually reflects B2B

URL-based conversions are the default and they are usually the wrong choice.

A thank-you page URL works for a whitepaper download. It doesn't work for a demo request that opens a Calendly modal without changing the URL, and it doesn't work for a form submitted via AJAX. Most serious B2B funnels have at least one of these.

For event-based conversions, add a second GTM tag:

1. Create a new **LinkedIn Insight Tag**, but set the tag type to the **conversion** variant.
2. Enter the **Conversion ID** from Campaign Manager.
3. Trigger it on your actual conversion event from the data layer: `demo_requested`, `form_submit`, whatever your site pushes.
4. Apply **the same consent settings** as the base tag. This gets forgotten constantly, and a consent-gated base tag with an ungated conversion tag isn't a consent-gated setup.

That last point is the most common mistake on this page. People carefully gate the tag they installed first and never revisit the one they added three months later.

## LinkedIn Conversions API: the server-side half

LinkedIn has a Conversions API, the same idea as Meta's: send conversions from your server instead of the browser, so ad blockers and cookie restrictions don't eat them.

Two things to know.

**Deduplication works the same way, and matters the same amount.** If you send a conversion from both the browser and the server without a shared event identifier, LinkedIn counts it twice. Same failure mode as [Meta CAPI in a server-side migration](https://piotrlitwa.com/articles/en/server-side-tagging-migration.html), same fix: one ID, generated once, sent to both.

**It doesn't solve consent.** Sending the conversion from your server doesn't create a legal basis you didn't have. If the user denied consent, you may not process their personal data for advertising purposes, and the location of the code is irrelevant to that. This is the same trap as server-side tagging generally, and LinkedIn isn't an exception to GDPR because it's B2B.

### The two tags people forget to gate

Beyond the Insight Tag itself, two more things leak in most B2B containers:

- **The conversion tag**, added later and never given consent settings.
- **The LinkedIn "Follow Company" or share widget**, if you embedded one. It loads LinkedIn scripts and sets cookies independently of your Insight Tag, and no consent configuration in GTM touches it, because it is hardcoded in your page template.

That second one is invisible from inside GTM, which is exactly why container-only audits miss it.

## Why this matters more in B2B than you think

A broken Meta pixel on a consumer e-commerce site costs you optimisation signal across tens of thousands of conversions. Painful, but statistically recoverable.

A broken Insight Tag on a B2B site costs you signal across maybe forty conversions a quarter. There's no statistical recovery from that. LinkedIn's algorithm can't optimise on forty data points that never arrived, and your cost per lead stays high for reasons nobody can explain, because the reason is invisible.

The economics are inverted: low volume makes each data point more valuable, not less. And LinkedIn's CPCs are the highest of any major platform, so the wasted spend per missing signal is larger too.

This is why the tag deserves the same scrutiny as GA4, and gets a fraction of it.

## Frequently asked questions

**Does Google Consent Mode v2 control the LinkedIn Insight Tag?**
No. Consent Mode passes signals to Google tags, which adjust their own behaviour. LinkedIn isn't a Google tag and has no cookieless mode. You must block it in GTM yourself, using Additional Consent Checks or a trigger condition.

**What cookies does the LinkedIn Insight Tag set?**
Mainly `li_sugr`, `UserMatchHistory`, `lidc`, and `bcookie`. All of them require consent in the EU before they are written.

**Where do I set up LinkedIn conversions, in GTM or Campaign Manager?**
Conversions are defined in LinkedIn Campaign Manager. GTM only deploys the tag. For event-based conversions (AJAX forms, modals) you add a second conversion tag in GTM with the Conversion ID from Campaign Manager.

**Do I need the LinkedIn Conversions API?**
Only if ad blockers or browser restrictions are costing you meaningful signal, which in B2B they often are. It requires the same deduplication discipline as Meta CAPI: one event ID, shared between browser and server.

**Does server-side sending remove the consent requirement for LinkedIn?**
No. Moving the code to your server doesn't create a legal basis for processing you didn't have. If a user denied consent, you can't process their data for advertising, regardless of where the request originates.

**How do I check whether my Insight Tag respects consent?**
Open your site in incognito, deny consent, then check DevTools, Application, Cookies for `li_sugr` or `UserMatchHistory`. If they are there, the tag fired anyway and your consent configuration isn't working.

## Next steps

The LinkedIn Insight Tag is easy to install and easy to install wrongly, and the wrong version looks identical to the right one until someone opens DevTools.

Do the ninety-second test first. Incognito, deny consent, check for `li_sugr`. That single check tells you whether the last two years of your B2B tracking were compliant, and it's the fastest audit on this site.

Then gate the tag properly using GTM's Additional Consent Checks rather than trigger gymnastics, and apply the same settings to your conversion tag, not just the base one.

And take the tag seriously in proportion to what it costs you when it fails. Forty missing B2B conversions a quarter isn't a rounding error. It's the reason your cost per lead won't come down.

If you want your container checked, the [Free GTM Audit](https://piotrlitwa.com/checkGTM/) inspects which tags respect consent and which don't. And if you want it monitored monthly rather than discovered during a DPA review, that is what [GTM monitoring](https://piotrlitwa.com/services.html#gtm) is for. €150/month, written report, no calls, cancel anytime. [Full pricing here](https://piotrlitwa.com/pricing.html).

---

**Sources and further reading**
- [LinkedIn Insight Tag documentation](https://www.linkedin.com/help/lms/answer/a418880) (LinkedIn)
- [LinkedIn Conversions API](https://learn.microsoft.com/en-us/linkedin/marketing/conversions/) (Microsoft)
- [GTM consent settings and additional consent checks](https://support.google.com/tagmanager/answer/10718549) (Google)

---

*Written by [Piotr Litwa](https://piotrlitwa.com/about.html), independent GTM & Analytics specialist.*