Last updated November 5, 2026 · Ghazanfar · 8 min read
LinkedIn conversion tracking records leads, sign-ups and sales from people who saw or clicked your LinkedIn ads. It uses the Insight Tag on your website, the Conversions API for server and CRM data, and Lead Gen Form results recorded inside LinkedIn, all reported in Campaign Manager.
LinkedIn is usually the most expensive click in a B2B account, and it is also where tracking tends to get the least attention. In the setups I audit, the Insight Tag is installed, a page-load conversion points at a thank-you URL, and nobody has looked at it since. That counts form fills reasonably well. It says nothing about which of those leads became pipeline, which is the question LinkedIn spend is supposed to answer.
LinkedIn matches conversions to members who interacted with your ads within the click and view-through windows you choose. Conversions come in from three places, and you can combine them.
LinkedIn’s help center has an overview in getting started with LinkedIn conversion tracking. The concepts are the same as on other ad platforms, which I cover in my conversion tracking guide.
Install the Insight Tag on every page, create a conversion in Campaign Manager, and attach it to your campaigns. I prefer event-specific conversions fired from GTM over page-load rules.
Page-load conversions on a thank-you URL are quicker to set up, but they count reloads and direct visits. If you use them, keep the thank-you page out of search and out of navigation.
It sends conversions from your server or CRM to LinkedIn with identifiers LinkedIn can match, such as a hashed email or LinkedIn’s click ID. It is the route for qualified leads and closed deals.
LinkedIn documents the API in its Conversions API overview. In practice there are three ways to run it: native CRM integrations LinkedIn supports, a server-side GTM container on Stape with a LinkedIn Conversions API tag, or your own integration. The data I send is the same as for Google’s offline uploads: hashed email, the LinkedIn click ID captured from the landing page when present, conversion time, value and a stable event ID. My offline conversion tracking guide covers how to capture click IDs into a CRM, and it applies here too.
Send the same eventId from both. When LinkedIn receives an Insight Tag event and a Conversions API event with the same ID from the same account, it keeps the Insight Tag event and discards the API one.
The behavior is described in LinkedIn’s deduplication documentation, which also requires a separate conversion rule for each data source, both attached to the campaign. Reporting then shows two conversions, and the server one only counts what the browser missed. With GTM, I push the ID with the form event and pass it to the Insight Tag event tag:
window.dataLayer.push({
event: 'generate_lead',
event_id: 'lead-8812'
});
// Insight Tag event (or the GTM template field)
window.lintrk('track', { conversion_id: 1234567, event_id: 'lead-8812' }); This is a different rule from Meta, where whichever event arrives first is kept. I explain Meta’s version in my Facebook Ads conversion tracking guide.
LinkedIn counts Lead Gen Form opens and submissions itself, so they need no website tag. The gap is what happens to those leads afterwards.
Lead Gen Form leads flow to your CRM through LinkedIn’s integrations or a download. To tell LinkedIn which of them became qualified or closed, send those outcomes back through the Conversions API. Without that, campaigns optimize toward the cheapest form fills, which in B2B often means the least qualified.
LinkedIn also expects consent to be respected for members in regions where it applies. I wire the Insight Tag to the same consent setup as the Google and Meta tags, so one choice controls them all. The Microsoft side of the B2B mix is in my Microsoft Advertising conversion tracking guide.
If LinkedIn reports form fills but not the pipeline behind them, I can set up the Insight Tag, the Conversions API and CRM outcomes, and verify them against your leads.
It is LinkedIn’s JavaScript tag for your website. It records page views and conversions from visitors who saw or clicked your LinkedIn ads, and powers website retargeting audiences.
If your sales happen after the form, in a CRM, yes. The Conversions API lets you send qualified leads and closed deals back to LinkedIn, which the Insight Tag can never see. It also recovers some conversions the browser tag misses.
When both send an event with the same eventId from the same account, LinkedIn counts the Insight Tag event and discards the Conversions API one. You need a separate conversion rule for each source, both attached to the campaign.
No. Lead Gen Forms are filled in on LinkedIn, so LinkedIn records them natively in Campaign Manager. What you still need is a way to send the outcome of those leads, such as qualified or won, back through the Conversions API.
LinkedIn only counts conversions it can tie to a LinkedIn ad interaction within the attribution windows you set. Most of your form submissions come from other channels. A large gap on LinkedIn-sourced leads, though, usually points to a tag that fires late or not at all.
Yes. Load the Insight Tag base code in GTM on all pages, then fire event-specific conversions from the same form success events you use for Google Ads and Meta, passing an event ID if you also send the Conversions API.
About the author
I’m Ghazanfar, founder of Analytigrow and a conversion tracking specialist. For 7+ years I’ve set up and fixed conversion tracking across LinkedIn, Google Ads, Meta, Microsoft Advertising, GA4 and server-side GTM on Stape for B2B and ecommerce businesses in the US, UK, EU and UAE. I’m Top Rated on Upwork with 100% Job Success. Reach me at [email protected] or on WhatsApp.
A tracking audit tells you exactly which events are wrong, why, and what it takes to fix them. No pitch deck, just the findings.