LinkedIn Insight Tag & Conversions API: The Setup
Insight Tag plus Conversions API for B2B funnels. The destination where lead events matter more than carts.
Event setup at a glance
- Browser tag
- LinkedIn Insight Tag
- Server-side API
- Conversions API
- Recommended path
- Hybrid: browser + server-side with deduplication
- Deduplication
- Yes, via event IDs
Identifiers
RequiredeventId
Recommended for match qualityli_fat_idem (SHA-256)
Event mapping
Leads
LeadSign UpDemo Request
Consent constraints
- Fires only with marketing consent; B2B is no exemption, GDPR covers business contacts too.
- Hashed emails lift the match rate considerably but need a clean consent basis.
Consent-aware routing assumed. Privacy fit depends on the concrete setup; the legal assessment stays with your privacy team (legal review required).
Implementation methods
- Insight Tag via GTM Web, Conversions API via the GTM Server-Side container
- eventId from the web container to both paths
Debugging checklist
- LinkedIn Campaign Manager conversion diagnostics
- sGTM preview mode
Common mistakes
- Insight Tag only, long B2B funnels lose attribution after the click.
- li_fat_id not carried along, the Conversions API matches poorly.
Runs on (our setups)
A fit when
- LinkedIn carries meaningful B2B budget with lead goals.
- Long decision cycles between click and closed deal.
- CRM data allows later conversion matching via email.
Not a fit when
- Campaigns target reach only; the Insight Tag is enough then.
- The consent basis for processing hashed contact data is missing.
What this destination is about
LinkedIn is the B2B destination: few, expensive conversions, long cycles. That is exactly why every lost lead event weighs more than on the consumer platforms.
The hybrid path with eventId deduplication and hashed email is our standard. The comparison with the other platforms is on the ad platform hub.
For a self-run QA pass: the Consent Mode audit checklist, the CMP QA template, and the consent mapping worksheet.
Sources
- LinkedIn Marketing API documentation (accessed 2026-07-03)
Related services
Topical context
- LinkedIn Conversions API setup
- LinkedIn Insight Tag server-side
- LinkedIn Ads B2B tracking
Do your conversions actually arrive in the ads platforms? The Paid Media Tracking Audit settles it.
Request a Paid Media Audit →What does the Conversions API add in B2B, concretely?
It carries conversions through long decision cycles: the lead converts weeks after the click, and server-side with a hashed email the campaign attribution survives.
More integrations we work with
- Ads & Conversion APIsCriteoRetargeting lives on product context. OneTag in the browser stays the default path; server-to-server is the exception.
- Ads & Conversion APIsOutbrainNative ads with postback logic. Server-to-server over the click ID is the sturdier path here, not the exception.
- AnalyticsGoogle Analytics 4 (GA4)The web analytics standard with a huge ecosystem. Free including BigQuery export, but consent-dependent and US cloud.
- AnalyticsPiwik PROEU-hosted analytics platform. GDPR-compliant by default, enterprise-ready, and the go-to GA4 migration target for consent-critical setups.
- AnalyticsPlausible Community EditionSelf-hosted, cookieless web analytics. GDPR-compliant without a consent banner, full data ownership. This very site runs on it.
- AnalyticsPostHogOpen-source product analytics, feature flags, and experimentation in one. EU self-hosting possible, usable as an assignment layer for server-side experiments.