LinkedIn Insight Tag installed but no data? The fixes

TL;DR

A LinkedIn Insight Tag firing in the browser does not mean Campaign Manager is receiving usable data. The LinkedIn-specific gotcha that traps everyone: the domain must be added to the Insight Tag in Campaign Manager, or LinkedIn ignores the signal even though the tag loads. Beyond that, the usual suspects: the wrong Partner ID, a conversion rule whose URL/event never matches, a Conversions API path that isn't deduplicating, and consent/ad-blocker loss (heavier on LinkedIn's professional, security-conscious audience). Below: how to tell which you've got, and the fix for each. (Same shape as the Meta and TikTok versions — LinkedIn just has its own quirks.)

---

You drop the LinkedIn Insight Tag on a B2B client's site, wait a couple of days, and Campaign Manager still says the tag is unverified or shows no audience building — or the tag is "active" but your lead-form conversions never register. B2B clients are exactly where attribution matters most (long cycles, expensive clicks), so this is worth getting right. Most of the time it's one of a short list of LinkedIn-specific issues.

The LinkedIn-specific trap: the domain must be on the tag

This is the one that wastes the most hours and appears nowhere obvious. In Campaign Manager → Account Assets → Insight Tag, LinkedIn keeps a list of domains the tag is allowed to report for. If the client's domain isn't on that list, the tag can load and fire all day and LinkedIn will ignore it — no audience growth, no "verified," no conversions.

Check: open the Insight Tag asset and confirm the live domain (and www/subdomain variants you actually use) is listed and shows recent signal. Fix: add the domain; verification flips to active once LinkedIn sees traffic from a listed domain (can take a few hours).

If the domain's listed and there's still nothing

1. Wrong or missing Partner ID

The Insight Tag is keyed to a Partner ID. A snippet with the wrong ID (or a stale one from another account) loads fine and reports to the wrong place — or nowhere you're looking. Check: the Partner ID in the on-page tag vs the one in Campaign Manager. Fix: correct it wherever it's injected (snippet, GTM tag field, CMS integration).

2. The tag loads but you're checking too soon / wrong

LinkedIn's tag status and audiences populate slower than GA4 Realtime. Check: use the LinkedIn Insight Tag Helper browser extension (or watch the network for a request to px.ads.linkedin.com) to confirm it fires now, rather than waiting on Campaign Manager's delayed status. Fix: if it fires in the browser and the domain's listed, give Campaign Manager a few hours before concluding it's broken.

3. Consent or an ad blocker is dropping it

LinkedIn's audience skews professional and security-conscious — higher ad-blocker and stricter-consent rates than a consumer site, so client-side loss is real here. Check: accept consent, test in clean incognito / on mobile. Fix: there's no client-side fix for blockers — which is the case for the Conversions API as a server-side backup, doubly so for B2B.

When the tag works but conversions don't

4. The conversion rule never matches

LinkedIn conversions are defined in Campaign Manager (not in the tag) — usually a URL rule (visits /thank-you) or an event. If the rule's URL doesn't match the real completion page (trailing slash, query params, a SPA route that doesn't change the URL), it never counts. Check: the conversion's rule against the actual post-conversion URL. Fix: correct the rule, or switch to an event-based conversion for SPA flows.

5. Pixel + Conversions API not deduplicating

Running the Insight Tag and the Conversions API is the right 2026 B2B setup — but only if both report the same conversion with consistent identifiers so LinkedIn counts it once. Misconfigured, you double-count or lose events. Check: Campaign Manager's conversion sources. Fix: align the event identifiers across both paths — the dedup contract is the whole game, same as on Meta.

The five-minute diagnostic

1. Domain on the Insight Tag? (the LinkedIn trap) — add it if not.
2. Partner ID match — on-page vs Campaign Manager.
3. Insight Tag Helper — does it fire now? (don't trust the delayed status alone).
4. Incognito + consent — appears? Blockers are eating client-side (→ CAPI).
5. Conversion rule matches the real completion URL/event?
6. Insight Tag + CAPI deduplicating?

Same lesson, B2B stakes

This is the familiar shape — a tag that "loads" answering a smaller question than "is LinkedIn receiving, matching, and attributing?" — with the B2B twist that the domain-allowlist quirk and heavy blocker loss make it bite harder. The durable fix is identical across Meta, Google Ads, TikTok, and LinkedIn: verify conversions on a schedule and back high-value events with server-side.

That standing verification is what Phloz keeps legible — every client's tags, server APIs, and conversion rules modeled as nodes with a health state, so "is LinkedIn actually attributing this B2B client's leads?" is a view, not a quarterly scramble. The tracking-infrastructure map is the surface; CRM for B2B agencies and pricing are the workflow. But start with the domain on the Insight Tag — it's almost always the domain.