Debug LinkedIn in Chrome DevTools

What LinkedIn traffic looks like

The Insight Tag's wire format is minimal: an account-level B2B tag whose intelligence happens server-side against the member graph.

Endpoint pattern

Loader snap.licdn.com/li.lms-analytics/insight.min.js; beacons to px.ads.linkedin.com/collect; older setups also hit linkedin.com/px

Transport

Compact GET beacons: fmt is usually gif (image beacon) or js

Key parameters

pid partner ID, the account-level identifier every Insight Tag site carries · conversionId present only on event-specific conversion beacons (a plain page-view beacon has none) · li_fat_id first-party ad tracking click ID, stored in the li_fat_id cookie after a click on a LinkedIn ad · li_sugr / cpuid LinkedIn's browser-matching identifiers · url / time page URL and timestamp

Payload

Typically no cleartext or hashed PII fields in browser beacons. Matching to LinkedIn members relies on the LinkedIn cookie session and the identifiers above

Debugging LinkedIn with Event Watcher

• The LinkedIn parser labels each beacon as either a page view or Conversion <id>, so conversion beacons stand out from ambient page tracking at a glance.
• The detail view surfaces the partner ID, conversion ID, and li_fat_id in the overview, groups li_sugr and cpuid under Identity, and puts version, timestamp, page URL, and session fields under Request data.
• The Cookies section shows the li_fat_id first-party cookie being set and then sent on subsequent hits, useful when verifying click-attribution plumbing after a LinkedIn ad click.

LinkedIn and consent

The extension checks Insight Tag traffic against the marketing consent category. The tag has no consent-mode or cookieless fallback: if px.ads.linkedin.com/collect fires before marketing consent is granted, the hit is a violation and Event Watcher counts it.

Because the Insight Tag is so often pasted site-wide by a marketing team rather than deployed through the tag manager, it is one of the most common tags to leak past CMP gating.

A correctly gated setup shows zero LinkedIn requests until consent, then the page-view beacon on the post-consent (re)load.

Common debugging scenarios

• A conversion is set up in Campaign Manager but never fires. Filter to LinkedIn and check whether beacons carry a conversionId at all. Seeing only page-view beacons means the event-specific rule (URL match or lintrk('track', ...) call) never triggers.
• Two partner IDs on one site. Pivot Grouped view by Tool and compare pid values across hits. A leftover agency tag alongside the current one double-reports demographics.
• Click attribution seems broken. After landing with a li_fat_id query parameter, verify the cookie in the Cookies section and confirm subsequent beacons carry it.
• Insight Tag fires pre-consent. The marketing-consent check flags it. Use the Script Tree to see whether the tag is hardcoded or CMP-gated through the tag manager.
• Full pixel inventory for an audit. See audit all tracking pixels for sweeping LinkedIn alongside the rest of the ad stack.