LinkedIn Insight Tag explained: what it does on your site
6 min read
What the LinkedIn Insight Tag does, what the partner ID identifies, why the code contains no event names at all, and how to check the tag on your own site.
A card in your Tag Explorer results showing a short number and the words LinkedIn Insight Tag is the piece of code that connects your website to LinkedIn advertising. One tag does the whole job: conversion tracking, retargeting audiences, and the aggregated demographic reporting LinkedIn is known for. Paste your page into Tag Explorer to see this tag on your own site.
It is the least talkative of the advertising tags. There is no event vocabulary in the code, no purchase value, no product data. That is by design, and understanding why explains most of what people find confusing about it.
What it actually does
The tag loads a script from snap.licdn.com and reports that a particular browser, already known to LinkedIn, has visited a particular page on your site. That is very nearly the whole of it.
From that one signal LinkedIn produces three things:
- Conversion tracking, by matching those page visits against rules you create in Campaign Manager.
- Retargeting audiences, built from visitors to a page or a set of pages, so you can advertise to people who have already read your pricing page.
- Website demographics, an aggregated profile of who is visiting: job function, seniority, industry, company size. Small segments are suppressed, so this is a picture of an audience and never a list of individuals.
The third is why plenty of businesses install it before running a single ad.
What the partner ID means
The Insight Tag is identified by a numeric partner ID, typically six or seven digits. In the installed snippet it is the value assigned to _linkedin_partner_id.
There is a wrinkle worth knowing. The snippet does not simply set that value, it pushes it into an array called _linkedin_data_partner_ids. A single page can therefore report to more than one LinkedIn account quite legitimately, which happens when an agency runs campaigns alongside the client’s own team. That is unusual elsewhere, where a second ID nearly always means a mistake. So a second LinkedIn ID is not automatically a fault. It is a question: whose account is it, and is anybody still using it?
Why there are no event names in the code
Meta, TikTok and Pinterest all expect the page to announce what happened, using their own event vocabulary. LinkedIn does the opposite. The tag reports visits, and you define what counts as a conversion afterwards, in Campaign Manager. Most rules are page based: a visit to /thank-you/ counts as an enquiry, with a value and a conversion window set against the rule.
Two consequences follow, and both are good news. You can create a conversion rule today and have it start matching without a developer touching the site, because the visits were already being recorded. And the most common LinkedIn tracking failure turns out not to be a broken tag at all: it is a form that submits in place, leaving the URL unchanged, so the rule has nothing to match. Either send people to a real confirmation page, or fire the conversion from Google Tag Manager on the submission itself.
Where JavaScript cannot be used at all, such as an email or a third party landing page, LinkedIn also offers an image based event pixel that reports one conversion. It is a narrow tool, not a substitute for the Insight Tag.
The server-side companion
The LinkedIn Conversions API lets your own systems report conversions directly, without the browser. Its real value is not resilience against ad blockers, though it helps there too. It is that the conversions that matter here often happen away from the website: a qualified lead, a booked meeting, a signed contract, all of which live in your customer records rather than on a thank you page. Sending those back means LinkedIn optimises towards leads that turned into business rather than towards whoever fills in forms most readily. Where a conversion could arrive by both routes, it needs a shared identifier so it is counted once.
What this looks like in Tag Explorer
Tag Explorer draws the page as a tree. Each Tag Manager container is a branch, its tags are leaves underneath, and anything hard coded into the page HTML sits under DIRECT ON PAGE.
The Insight Tag appears as an Advertising card with the partner ID as the card title and the tag type as the subtitle. Because the partner ID is short and numeric, it can read as an ordinary number among the longer codes on the page, so go by the subtitle rather than the digits.
On your result, look at:
- How many LinkedIn cards there are. Given the array behaviour above, two is worth investigating rather than assuming an error.
- The duplicate banner and red attention badge, which appear when the same partner ID is found from two separate sources, usually a hard coded snippet plus a Tag Manager tag.
- The insights panel under the tree, which flags split tracking: one vendor reporting to two different IDs of the same family from a single page.
The published container file holds only the tag type and the tracking ID, never the human names you gave your tags, and the tool reads the published container, so an unsubmitted Tag Manager change is invisible to it. A scan also shows the tag is installed, not that it fired: Preview mode in Tag Manager, and the tag status in Campaign Manager, are what confirm it is reporting.
What to do if it is missing, duplicated or dead
Missing. No LinkedIn card means no conversions and no audience being built. Audiences are cumulative, so every week without the tag is a week of retargeting you cannot recover. Install it through the official LinkedIn template in Tag Manager, trigger it on all pages, publish, then check the tag status in Campaign Manager, which reports whether LinkedIn has actually received traffic.
Duplicated. The same partner ID from two sources inflates audience matching and demographic reporting. Keep the Tag Manager copy and remove the hard coded one. Two different partner IDs, as above, is more often a second stakeholder than a bug, so identify the account before deleting the tag out from under whoever is paying for it.
Dead or stale. The Insight Tag has no retired version to worry about. What goes stale is the account: a partner ID belonging to an agency you no longer work with, quietly building audiences you cannot use. Stand the tag up under an account you own, remove the old one, and accept that the audiences it built do not come with you.
Related guides
- Meta Pixel explained
- Microsoft UET tag explained
- Form submission event listeners explained
- GTM containers explained
- What is Google Tag Manager?
Check which partner ID your site is reporting to, and how many, with Tag Explorer. If the answer includes an ID nobody recognises, or your forms never reach a page a conversion rule could match, the measurement needs fixing before the ad budget is worth increasing. That groundwork is the first thing we do on any paid campaign, including the ChatGPT Ads campaigns we run.
Frequently asked questions
What is a LinkedIn partner ID?
It is the numeric code that ties the Insight Tag to your LinkedIn advertising account, and it is usually six or seven digits. In the installed snippet it appears as the value assigned to _linkedin_partner_id. You can also read it in Campaign Manager under the data sources area, where the Insight Tag is managed.
Why does the LinkedIn code contain no event names?
Because LinkedIn does not define conversions in the page. The Insight Tag reports which pages were visited, and you then create conversion rules inside Campaign Manager, most often a rule that says a visit to a particular thank you page counts as an enquiry. The useful side effect is that a conversion can be created after the fact and still work, because the visits were already being recorded.
Can one Insight Tag snippet carry two partner IDs?
Yes. The snippet pushes the partner ID into an array, so a page can legitimately report to more than one LinkedIn account, which is common when an agency and a client both run campaigns. It only becomes a fault when nobody knows what the second ID is or who owns it, in which case find out before removing anything.
What is the li_fat_id parameter appearing on my landing page URLs?
It is LinkedIn's first-party click identifier, added to the destination URL when enhanced conversion tracking is enabled, and the Insight Tag stores it so a later conversion can be matched back to the click. It looks like tracking clutter, so it is often stripped by a redirect or a canonical rewrite, and doing that silently breaks LinkedIn attribution. Leave it alone unless you know exactly what depends on it.
Does the Insight Tag show me who visited my site?
No. It powers aggregated website demographics such as job function, seniority, industry and company size, and LinkedIn suppresses segments that are too small to be reported without identifying individuals. You get a profile of the audience, never a list of names.