We’re upgrading our email infrastructure — for immediate response, email andrewjgaber@gmail.com meanwhile.
Skip to main content
Part of Digital Empire
Affiliate / Other

LinkedIn Insight Tag (_linkedin_partner_id) conversion tracking

LinkedIn · Web Pixels API replacement · confidence: medium

Dies 2026-08-26

Paste-ready snippet
analytics.subscribe('checkout_completed', (event) => {
  const { checkout } = event.data;
  if (!checkout || !checkout.totalPrice) return;

  // The LinkedIn Insight Tag is a browser script that sets a first-party
  // pixel and reports conversions from the page — no DOM in the sandbox, so
  // conversions must be reported via LinkedIn's Conversions API (server-side
  // equivalent) instead. Replace CONVERSION_ID and ACCESS_TOKEN (Campaign
  // Manager > Conversion Tracking > your conversion > API details).
  fetch('https://api.linkedin.com/rest/conversionEvents', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: 'Bearer ACCESS_TOKEN',
      'LinkedIn-Version': '202405',
    },
    keepalive: true,
    body: JSON.stringify({
      conversion: 'urn:lla:llaPartnerConversion:CONVERSION_ID',
      conversionHappenedAt: Date.now(),
      conversionValue: {
        currencyCode: checkout.totalPrice.currencyCode,
        amount: String(checkout.totalPrice.amount),
      },
      eventId: checkout.token,
    }),
  });
});

Legacy pattern detected via: _linkedin_partner_id|snap\.licdn\.com\/li\.lms-analytics

What this does NOT cover

What this does NOT cover: LinkedIn's page-level Insight Tag used for retargeting-audience building — that is a separate, onsite script unrelated to checkout events. It also does not handle multi-partner LinkedIn setups where more than one Insight Tag/Conversion ID needs to fire on the same order.

Test-event verification checklist

  • eventId uses checkout.token for dedup consistency with the pattern used across every other network template in this library.
  • conversionValue.amount is passed as a STRING per LinkedIn Conversions API schema, not a number — a common integration bug if copied without this cast.
  • Requires a LinkedIn Marketing Developer Platform access token with the r_ads / rw_conversions scope on the server making this call — if this snippet is run directly from the sandbox, the ACCESS_TOKEN is exposed client-side, which LinkedIn's API accepts but is a real credential-exposure tradeoff; recommend routing through your own backend relay endpoint instead of embedding a long-lived token in pixel code shipped to every visitor's browser. Fires once per completed order.
  • Verify live against the platform's own test-event tool: https://www.linkedin.com/campaignmanager/

Related paste-ready snippets

Secondary paid-social pixels · LinkedIn Insight Tag + Twitter/X Pixel — small-share paid social channels pasted alongside Meta Pixel.