LinkedIn Insight Tag with Google Tag Manager: A Setup Guide

The cleanest way to install the LinkedIn Insight Tag is through Google Tag Manager: you add the base tag once with a built-in template set to fire on all pages, then layer your conversions on top without ever touching your site code again. The Insight Tag is the foundation of everything you measure on LinkedIn, because the same tag powers conversion tracking, retargeting audiences, and the website demographics report. Get it in correctly, verified, and respecting consent, and the rest of your measurement has something to stand on. This guide covers getting your Partner ID, installing the tag in Google Tag Manager, verifying it fires, setting up URL-based and event-based conversions, handling consent, and deduplicating with the Conversions API.

Key takeaways

Install the Insight Tag once in Google Tag Manager with the built-in LinkedIn template, set to the All Pages trigger, then manage conversions on top of it.
Get your Partner ID from Campaign Manager, under Data then Signals Manager (older accounts show it under Account Assets).
The same base tag powers conversion tracking, retargeting, and website demographics, so one correct install unlocks all three.
Use URL-based conversions when the action has its own thank-you page, and event-based conversions when it does not have a unique URL.
Gate the tag behind your consent management platform, add every domain in Campaign Manager, and deduplicate with a shared event ID if you also run the Conversions API.

Why install the Insight Tag through Google Tag Manager?

The Insight Tag is a small piece of code that lets LinkedIn see which of its members visit your site, which is what makes conversion tracking, retargeting, and the website demographics report possible. You can paste it directly into your site, but installing it through Google Tag Manager is cleaner for three reasons. You add the base tag once and never touch the site code again. You manage every conversion and event from one place, with a clear record of what fires where and the ability to gate it behind consent. And you can build event-based conversions, like a button click or a form submit that has no unique URL, without asking a developer to add code each time. For any site that already runs Google Tag Manager, this is the sensible default.

How do you get your LinkedIn Partner ID?

The Partner ID is the number that ties the tag to your ad account, and you get it from Campaign Manager. Open Campaign Manager, then go to Data and Signals Manager (on older accounts this sits under Account Assets, then Insight Tag or Conversion Tracking). Add your domain if you have not already, then choose to manage the Insight Tag and view the tag code with the “I will install the tag myself” or tag-manager option. In the code you copy, the Partner ID is the numeric ID, and that number is all you need for the Google Tag Manager template, so you do not have to paste the whole script. Keep it handy for the next step.

How do you install the Insight Tag in Google Tag Manager?

The install itself takes about two minutes with the built-in template.

In Google Tag Manager, click New to create a tag and give it a clear name like “LinkedIn Insight Tag.”
Open Tag Configuration, search for LinkedIn, and select the LinkedIn Insight template.
Paste your Partner ID into the field provided.
Click Triggering and choose the All Pages trigger, so the base tag fires everywhere.
Save the tag.
Click Preview, load your site, and confirm the tag fires in the debug pane.
Click Submit, name the version, and Publish.

That is the base tag done. Publishing is the step people forget, and an unpublished container means the tag is not live no matter how correct it looks.

How do you verify the tag is firing?

Check it in two places. First, in Google Tag Manager preview mode, load your site and confirm the LinkedIn Insight tag shows as fired in the debug pane; this confirms the tag itself is working. Second, in Campaign Manager, open Signals Manager and look at the Insight Tag status and the last-signal-received indicator, which turns active once LinkedIn receives traffic, and can take up to 24 hours to appear. If the debug pane shows the tag firing but Campaign Manager still shows no signal after a day, the usual causes are an unpublished container, a Partner ID typo, the domain not being added in Campaign Manager, or the tag being blocked because consent was not granted.

URL-based vs event-based conversions

Once the base tag is live, you track conversions in one of two ways, and choosing the right one matters.

Conversion type	Use it when	How it fires
URL-based	The action has its own page, like a thank-you or order-received URL	LinkedIn counts a conversion when someone loads a URL that matches your rule
Event-based	The action has no unique URL, like a button click, PDF download, or on-page form submit	A tag fires on a Google Tag Manager event trigger you define

For a URL-based conversion, you create the conversion in Campaign Manager, choose the type and value, and point it at the page URL, using a “URL contains” rule on the distinctive part of the path so small variations do not break it. For an event-based conversion, Campaign Manager gives you an event-specific code, which you add in Google Tag Manager as a Custom HTML or Custom Image tag fired by the trigger for that action, for example a click trigger that fires on links containing “.pdf.” Both report back to the same base tag.

The one tag, many events model

The mental model that keeps this clean is one tag, many events. You install a single base Insight Tag across every page, and then every conversion you track is just another event layered on top of that one tag, never a second base install. This is why Google Tag Manager is worth it: adding a new conversion later, say a demo-request button you add next quarter, is a two-minute event trigger, not a site-code change and a developer ticket. It also keeps your measurement consistent, because every event reports through the same tag to the same account, so your conversion tracking, retargeting audiences, and website demographics all draw from one clean source rather than a patchwork of scripts.

Three setup details separate a clean install from a leaky one. First, consent: in regions with privacy rules like GDPR, the Insight Tag should only fire once a visitor has consented, so gate it behind your consent management platform or Google Tag Manager’s consent settings rather than letting it fire unconditionally. Second, domains: add every domain you run ads to in Campaign Manager, because the tag only signals on domains you have registered, and registering your domain also lets the tag set first-party cookies there, which recovers some of the tracking that third-party cookie blocking would otherwise lose. Third, deduplication: if you also send conversions through the Conversions API, pass the same unique event ID from both the tag and the API for a given conversion, so LinkedIn counts it once instead of twice. Getting these three right is what keeps the data both compliant and accurate.

Common Insight Tag and Google Tag Manager mistakes

The recurring mistakes are small and avoidable. Forgetting to publish the Google Tag Manager container, so the tag never goes live, is the most common. Copying the wrong part of the tag code instead of the Partner ID is close behind. Not adding your domain in Campaign Manager, which stops the tag from signaling, catches people out. Letting the tag fire without respecting consent creates a compliance risk. Installing the base tag twice, once directly and once through Google Tag Manager, double-counts everything. And assuming the Insight Tag can track submissions on a LinkedIn lead gen form is a misunderstanding: those happen on LinkedIn, so LinkedIn reports them, not your tag.

Get the foundation right, then measure to pipeline

Here is the thread. The Insight Tag is not a nice-to-have; it is the base layer that every other measurement sits on, so installing it correctly through Google Tag Manager, verifying it signals, respecting consent, and layering conversions cleanly is what makes the rest trustworthy. Once it is solid, pair it with server-side conversions to recover what browsers block, build retargeting audiences and read the website demographics it enables, and judge the campaigns on the pipeline those conversions represent, not the raw count. If you want your LinkedIn tracking set up cleanly from the tag up, you can book a demo.

Frequently Asked Questions

Q1. What is the LinkedIn Insight Tag?

The LinkedIn Insight Tag is a small piece of JavaScript you place on your website that lets LinkedIn recognize which of its members visit. It is the foundation for conversion tracking, retargeting audiences, and the website demographics report. One base tag across your site powers all three, which is why installing it correctly is the first step in any serious LinkedIn Ads measurement setup.

Q2. How do I install the LinkedIn Insight Tag with Google Tag Manager?

Get your Partner ID from Campaign Manager under Data then Signals Manager. In Google Tag Manager, create a new tag, choose the LinkedIn Insight template, paste the Partner ID, set the All Pages trigger, and save. Then preview to confirm it fires, and submit and publish the container. Publishing is essential; an unpublished container means the tag is not live.

Q3. Where do I find my LinkedIn Partner ID?

In Campaign Manager, go to Data and then Signals Manager (older accounts show it under Account Assets, then Insight Tag or Conversion Tracking). Add your domain, choose to view the tag with the “install it myself” option, and the Partner ID is the numeric ID in the code. For the Google Tag Manager template you only need that number, not the whole script.

Q4. How do I know if my LinkedIn Insight Tag is working?

Check two places. In Google Tag Manager preview mode, load your site and confirm the Insight tag shows as fired in the debug pane. In Campaign Manager, open Signals Manager and look at the Insight Tag status and last-signal indicator, which can take up to 24 hours to turn active. If the tag fires but never signals, check for an unpublished container, a Partner ID typo, a missing domain, or a consent block.

Q5. What is the difference between URL-based and event-based conversions?

A URL-based conversion fires when someone loads a page that matches your rule, such as a thank-you URL, so use it when the action has its own page. An event-based conversion uses a tag fired by a trigger in Google Tag Manager, so use it when the action has no unique URL, like a button click, a PDF download, or an on-page form submit.

In regions with privacy rules such as GDPR, yes. The tag should only fire after a visitor consents, so gate it behind your consent management platform or Google Tag Manager’s consent settings rather than letting it fire on every page load. This keeps the install compliant, and it is why some conversions go untracked for visitors who decline consent.

Q7. How do I avoid double-counting if I use the Insight Tag and the Conversions API?

Send the same unique event ID, such as an order ID or form submission ID, from both the Insight Tag and the Conversions API for a given conversion. LinkedIn matches the IDs and deduplicates automatically, counting one conversion instead of two. Set this up from the start when you run both, because double-counting makes campaigns look stronger than they are.

Q8. Why is my LinkedIn Insight Tag not recording conversions?

Common causes are an unpublished Google Tag Manager container, the base tag not firing on the conversion page, a conversion URL rule that does not match the live URL, the domain not being added in Campaign Manager, or the tag being blocked because consent was not granted. Also remember the tag cannot track submissions on a LinkedIn lead gen form, since those happen on LinkedIn and are reported there.