
Why is the LinkedIn Insight Tag not tracking conversions?
When the LinkedIn Insight Tag isn't tracking conversions, the cause is usually one of two things: a Campaign Manager setup gap, or the li_fat_id click ID getting lost before the tag can read it. We ran the live tag in a browser and found that it reads the click ID exactly once, from the page's query string, at the moment the script loads. If a redirect, a router or an iframe has removed it by then, it never gets stored, and the conversion has nothing to tie it to the ad click.
Most audits stop at "the tag is installed." In our tests it can be installed, firing on every page, and still never store the ID LinkedIn needs.
How we tested it
We downloaded the current Insight Tag script (insight.min.js, last modified October 14, 2026) and loaded it on small test pages in headless Chromium, each page reproducing one install pattern we see in tracking reviews. Every request to LinkedIn was captured and answered locally, so nothing reached LinkedIn. We used a made-up partner ID and fake click IDs, and checked two things: what the tag sent to px.ads.linkedin.com, and whether an li_fat_id cookie existed afterwards.
So these results show what the browser sends. They don't show how Campaign Manager attributes the result. For that side, we quote LinkedIn's click ID documentation (updated September 23, 2026) and its help article on reporting discrepancies.
What does the tag do with li_fat_id when it works?
On the clean path, landing on /lp.html?li_fat_id=..., the tag did three things:
- It wrote a first-party cookie named
li_fat_idon the broadest domain it could set,.example.comrather thanwww.example.com, with a 30-day expiry. - It sent the click ID on the page view, as an
li_fat_idparameter on the/collectrequest, next to the partner ID (pid) and the full page URL. - It kept sending it on later pages, including a different subdomain, by reading the cookie back.
That cookie is what later conversions lean on. A second, li_giant, is handled the same way with a 7-day expiry. LinkedIn's docs add a useful detail: the mapping from a click ID to a member is kept for 365 days, so an li_fat_id you save with the lead can still be matched when you send it through the Conversions API months later.
The 7 causes we see most
1. The conversion isn't attached to the ad set
This is a setup problem, not a code one, and it's the first thing LinkedIn's own troubleshooting article lists: a conversion has to be added to one or more ad sets before they can record it. Open the conversion in Campaign Manager and check the ad sets column. No ad set selected means zero conversions, even with a perfect tag.
2. The URL rule doesn't match the real thank-you page
URL-based conversions compare the page URL against your rule. LinkedIn warns about www, extra slashes and characters that differ between what you typed and what the browser loads. Copy the URL from a real test submission, not from the sitemap.
3. A redirect drops the query string
We sent a test click to /redirect-lp?li_fat_id=..., which answered with a 301 to /lp.html and no query string. The tag loaded fine and sent its page view, but without an li_fat_id parameter, and no cookie was written. The same test with a redirect that kept the query string worked normally.
This is common with vanity URLs, http to https or non-www to www rules written by hand, and landing page tools that redirect to a "clean" URL. If you also run Google and Meta ads, the same redirect is probably eating gclid and fbclid too, which we covered in our post on click ID stripping in iOS 26.
4. Something cleans the URL before the tag loads
We tested two versions. In one, a script in the page head called history.replaceState to remove the query string before the Insight Tag ran. In the other, the URL was cleaned at 0.5 seconds and the tag was injected at 2 seconds, the way a delayed Google Tag Manager trigger or a "load scripts on interaction" performance plugin does it.
Both lost the click ID. No cookie, no li_fat_id on the hit. The tag doesn't look at the URL again after it starts, so if anything tidies the address bar first, the ID is gone. Load the Insight Tag on page load (GTM's Initialization or All Pages trigger), and exclude it from script-delay plugins.
5. The click ID ends up in the hash
A landing page reached as /lp.html#li_fat_id=... got a page view hit with the full URL, hash included, but no cookie and no li_fat_id parameter. The tag only parses the query string. This mostly happens when someone pastes a tracking template into the wrong spot, or with hash-routed single-page apps.
6. The tag lives inside a form iframe on another domain
Lots of lead forms are embedded iframes from a form tool on its own domain, and some of those tools ask you to paste your Insight Tag into the form instead of your page. We put the tag inside a cross-origin iframe on a page that had li_fat_id in its URL.
The tag noticed it was in a frame and read the parent's URL from document.referrer. With the browser's default referrer policy, that referrer is only the parent's origin, so the path and query string, click ID included, never reached the tag. No cookie was set, and the hit reported the parent's home page as the URL. The same iframe served from the parent's own domain captured the click ID correctly.
The fix: put the Insight Tag on the parent page, and fire the conversion from the parent when the form reports success, usually through a postMessage event the form tool documents.
One more detail from this test: setting <meta name="referrer" content="no-referrer"> on a normal page did not break tracking. The tag sends the page URL as its own url parameter, so the missing Referer header didn't matter outside the iframe case.
7. A single-page app never reloads the thank-you page
When we changed route with history.pushState, the tag sent no new /collect request. It did send a PAGE_VISIT signal for the new URL to its website-actions endpoint (/wa/), which LinkedIn uses for newer website-based tracking features. But we wouldn't bet a thank-you-page conversion rule on that.
What did work: calling window.lintrk('track', { conversion_id: 1234567 }) right after the route change. That sent a /collect request with the conversion ID and the new /thank-you URL. For single-page apps and AJAX forms, use event-specific conversions fired on success, not URL rules.
A silent one: a bad partner ID
One more we tested because we've seen it in GTM variables: a partner ID with a trailing space, "1234567 ". The tag accepts only digits, so it dropped the ID and still sent the hit, with an empty pid=. There was no console error. If your /collect requests show pid= with nothing after it, the problem is the value, not LinkedIn.
How do you check your own site in 5 minutes?
- Land with a fake click ID. Open your landing page with
?li_fat_id=test-123appended, the same way an ad click would arrive, through any redirect your ads use. - Filter DevTools by
px.ads.linkedin.com/collect. The request should show a numericpidandli_fat_id=test-123. - Check the cookie. In the Application tab, look for
li_fat_idon your root domain with a 30-day expiry. - Walk to the conversion. Submit the form or finish the checkout and look for a
/collectrequest withconversionId=(event-specific) or a page view on the thank-you URL your rule expects. - Repeat on mobile and in the LinkedIn app's browser if most of your traffic comes from there.
If step 2 has no li_fat_id, work back through causes 3 to 6. If it's there but step 4 shows nothing, it's cause 1, 2 or 7.
Should you add the LinkedIn Conversions API?
For lead gen, yes, and it's mostly about the click ID. Capture li_fat_id into a hidden form field on submit (read the cookie, or the URL as a fallback), store it with the lead, and send it as the LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID identifier when the lead qualifies or closes. That's how offline outcomes like a booked call or a signed deal get back to the campaign, the same pattern we use for Meta's Conversions API.
Two rules from LinkedIn's deduplication docs catch most teams out:
- Each source needs its own conversion rule. One for the Insight Tag, one for the Conversions API.
- The same
eventIdhas to come from both sides. In the browser, passevent_idinlintrk('track', { conversion_id, event_id }), which our test showed as aneventIdparameter on the request, or setwindow._linkedin_event_idbefore the base code for page-load conversions. When both arrive with the same ID, LinkedIn keeps the Insight Tag event and drops the server one.
If you'd rather send server events from your own infrastructure than from the browser, the hosting trade-offs are the same as in our server-side GTM comparison. And if your cookie banner gates the tag, check that it actually loads after consent, which is the trap we documented in consent mode conversions dropping.
What we'd fix first
Start with the boring checks: ad set attached, URL rule correct, enhanced conversion tracking on. Then land with a fake li_fat_id and follow it. In our tests, every failure happened before the conversion even existed: the ID was gone by the time the tag looked for it.
Want a second pair of eyes on it? We check the Insight Tag, the click ID path through your redirects and forms, and the Conversions API events that should match it. Get a Free Automation Audit: you'll get your free initial audit report by email within 24 hours. If the fix is part of a bigger tracking cleanup, that's the day-to-day work of our ads management and attribution team.
