LinkedIn Insight Tag Conversions Not Tracking: Fixes

Olamide Sule, founder of Dolphin Analytics: a digital analytics expert based in London delivering solutions for agency and in-house clients.

We fix broken conversion tracking for agencies and in-house B2B teams most weeks, and LinkedIn conversions are one of the first things to go quiet after a site rebuild or a consent change. This is the checklist we run when a client’s Insight Tag conversions stop reporting: what breaks, how to confirm it, and the exact fix. LinkedIn Campaign Manager menu paths were checked on 6 September 2026; verify the current labels, since LinkedIn moves them.

Why are my LinkedIn Insight Tag conversions not tracking?

LinkedIn Insight Tag conversions fail when the signal never reaches LinkedIn, or reaches it against the wrong rule. The tag might not load on the page where the conversion happens, a consent tool might block it before it fires, or the conversion rule in Campaign Manager might watch a URL or event that no longer matches your site. Fix the signal first, then the rule.

The shortlist of faults, in the order worth checking:

1. The Insight Tag is not loading on the conversion page.
2. A consent banner blocks the tag before it fires.
3. The conversion rule points at the wrong URL or event.
4. The attribution window has not elapsed, or reporting is still catching up.
5. GTM fires the tag on the wrong trigger, or not at all.
6. The partner ID is wrong, so signals go to the wrong account.
7. A single-page app never re-fires the tag on the confirmation view.

Most broken setups are one of the first three. Work down the list rather than guessing, because a wrong conversion rule looks identical to a blocked tag until you check where the signal stops.

How does the LinkedIn Insight Tag record a conversion?

The LinkedIn Insight Tag is a small JavaScript snippet that loads on every page, drops a first-party cookie called li_fat_id, and sends a page signal to px.ads.linkedin.com. A conversion is recorded one of two ways: a URL-based rule that fires when someone reaches a matching page, or an event-specific pixel that fires on a defined action. LinkedIn then matches that signal to a member who saw or clicked your ad inside the conversion window.

That two-part design is where most faults hide. The base tag can load perfectly while the conversion rule watches the wrong page, and the conversion rule can be flawless while consent blocks the base tag from ever loading. Knowing which half broke saves hours.

Is the Insight Tag actually loading on the conversion page?

Check the tag loads on the exact page where the conversion happens, not just the homepage. In LinkedIn Campaign Manager, go to Analyze, then Insight Tag, and confirm your domain shows an active tag with a recent signal. Then verify it in the browser, because Campaign Manager only tells you the domain is reporting, not which pages carry the tag.

To check a specific page:

1. Open the confirmation or thank-you page in Chrome.
2. Open DevTools (F12), select the Network tab, and reload.
3. Filter the requests for px.ads.linkedin.com.
4. A working tag shows a request to px.ads.linkedin.com/collect returning a 200 status, plus a snap.licdn.com script load.
5. Check Application, then Cookies, for the li_fat_id cookie.

The fault we find most here is a tag that sits site-wide but goes missing on the one page that matters. Payment confirmations that redirect to a gateway subdomain, or lead forms that submit to an external booking tool, sit outside your site template, so the tag never loads where the conversion completes. Move the conversion signal onto that page, or track the return-to-site step instead.

Is a consent banner blocking the tag?

If your consent tool holds the tag back and the visitor rejects, no signal is ever sent, so the conversion cannot be counted. The Insight Tag is a marketing cookie, so consent platforms like OneTrust and Cookiebot block it by default until the visitor accepts. This is the fault that appears overnight after a new banner goes live, and it hits UK and EU traffic hardest.

To confirm and fix it:

1. Load the page, reject the banner, and check the Network tab: there should be no px.ads.linkedin.com call.
2. Reload, accept the banner, convert, and confirm the call now fires.
3. In your consent tool, confirm the Insight Tag is categorised as marketing or targeting and is set to fire once that category is granted.
4. If you deploy through GTM, gate the tag with a consent-aware trigger so it waits for acceptance rather than being blocked outright.

A blocked tag is a real data-loss problem, not just a LinkedIn one. The same mechanism quietly drops a slice of every marketing tag on the page. We walk through the wider version of this in how consent settings lose analytics data.

Is the conversion rule mapped to the right URL or event?

If the tag loads but nothing records, the conversion rule is usually watching a page or action that no longer exists. In Campaign Manager, go to Analyze, then Conversion tracking, open your conversion, and select Edit. Conversions run on one of two rule types, and each breaks differently.

• URL-based rules fire when a visitor reaches a matching page. The common fault is an exact-match rule set on a thank-you URL that changed, or that now carries query strings (?utm_source=...). Switch the match type to “starts with” or “contains” the stable part of the path, so tracking parameters do not break it.
• Event-specific pixels fire on a defined action, such as a form submit. The fault here is the pixel never being placed on the action, or firing on page load rather than on the submit. Fire it on the event, not the pageview.

Set a sensible value and the correct counting behaviour while you are in there, so downstream bid strategies optimise on the right number.

Have you waited for the attribution window and reporting delay?

LinkedIn only counts a conversion when a member saw or clicked your ad inside the conversion window set on that conversion, so a lead outside the window will never show. Open the conversion in Campaign Manager and check its attribution window and model against LinkedIn’s conversion tracking documentation, which explains the click-through and view-through settings. Reporting also lags, so a conversion that just happened may take time to appear.

This one is a check, not a fix: before you rebuild anything, rule out that the data is simply not in yet. If the leads are recent, or came from channels LinkedIn cannot see, the absence is expected, not a bug.

Is GTM firing the tag on the right trigger?

If you deploy the Insight Tag through Google Tag Manager, the base tag should fire on every page and the conversion should fire on the conversion event. Broken GTM setups usually fire the base tag only on some pages, or never fire the conversion event at all.

Check it in GTM Preview:

1. Enter Preview mode and load the conversion page.
2. Confirm the LinkedIn base tag shows under “Tags Fired”.
3. Trigger the conversion action and confirm the conversion tag fires on that event, not on the initial pageview.
4. Open the tag and confirm the partner ID matches your account.

Firing on the wrong trigger is one of the most common tag faults full stop. The same diagnostic approach applies across every tag in the container, which we cover in how to debug GTM tags that will not fire.

Is the partner ID correct?

Every Insight Tag call carries a partner ID that routes the signal to your account, so a wrong ID sends conversions nowhere useful. This bites when a container is copied from another site, or when a developer hardcodes the wrong _linkedin_partner_id. The tag fires, the network call succeeds, and the conversions land in an account you cannot see.

Confirm the partner ID in the outgoing px.ads.linkedin.com/collect request matches the Insight Tag ID shown under Analyze, then Insight Tag in Campaign Manager. If they differ, correct the ID in your tag or GTM variable and republish.

Does your single-page app re-fire the tag?

On a single-page app, the base tag loads once and never reloads, so a URL-based conversion rule never sees the confirmation view. Frameworks like React, Vue and Angular change the route without a full page load, which means the thank-you “page” your rule is watching for never triggers a fresh tag fire.

Fix it by firing the conversion as an explicit event instead of relying on the URL. Push the conversion on the route change with the LinkedIn tracking function:

window.lintrk('track', { conversion_id: 1234567 });

Replace the ID with your conversion’s ID from Campaign Manager, and call it on the route change that reaches the confirmation state. In GTM, wire the same call to a History Change trigger or a custom event your app pushes on conversion.

How we fix LinkedIn conversion tracking

We audit and fix broken conversion tracking for agencies and in-house B2B teams most weeks, and the pattern above is the order we work through it. When we review a broken setup, the fault we find most is a tag that loads fine on the homepage but is absent, or consent-blocked, on the exact page that counts, so the campaign looks like it stopped converting when the ad spend is still doing its job. On one B2B engagement, our fix helped the agency protect a six-figure retainer.

If you want to see what is actually on your pages first, Sonar scans your site from the outside in one click, with no account and nothing to install, and reports the tags, pixels and consent setup it can prove from the scan, including whether the LinkedIn Insight Tag is present. Run a free Sonar scan. If the tag is there but the numbers still look wrong, talking to us gives you a considered reply from a person on where the signal is being lost. For the Google side of the same problem, see our Google Ads conversion tracking guide.