Key takeaways
- The Insight Tag is the foundation: without it, there's no conversion tracking and no retargeting.
- Installation either directly in the page code or through Google Tag Manager, on every page, then verify it fires.
- Consent first: the tag only loads after the visitor accepts marketing cookies.
- Cookie and browser blockers cut off up to 40% of conversions. The tag alone isn't enough.
- The Conversions API measures up to 42% more conversions server-side. Three tracking types work together: Insight Tag, Conversions API, offline CSV.
Almost every LinkedIn Ads setup stands or falls on one thing many people skip: tracking. No tracking, no reliable numbers, no optimization. The foundation is the Insight Tag, a small piece of code on your website. The technical upgrade is the Conversions API, which recovers the conversions the tag alone loses. This page covers both, from setup to how they work together. For how to correctly interpret the numbers afterward, and how to avoid the attribution trap in a long B2B cycle, see the overview on Tracking and Attribution.
What the Insight Tag is, and why it's the foundation
The LinkedIn Insight Tag is a small JavaScript snippet you install once on your website. It reports back to LinkedIn what a visitor does after clicking your ad: which pages they visit, whether they submit a form, whether they land on a thank-you page. These signals create two things LinkedIn Ads can't work without in B2B.
First, conversion measurement. Only when LinkedIn knows which click led to a lead can the algorithm learn and optimize toward the right people. Second, retargeting. The tag quietly builds audiences of your website visitors in the background, which you then target again later. Both come from the same root. No tag, no either. That makes it the mandatory first step, and at the same time the cheapest lever there is: it costs nothing but a few minutes of setup, and yet plenty of accounts don't run it at all.
You don't need a separate tag for every campaign. The Insight Tag is generated once per ad account and installed once on your website. From there, it collects data for every campaign at once. If you run multiple domains, the same tag belongs on each of them.
Setting up the Insight Tag, step by step
Setup takes about fifteen minutes. Just don't skip a step, or the tag won't end up firing where it should.
- Generate the tag in Campaign Manager. Under Analyze, then Insight Tag, you'll find your code. LinkedIn shows you two paths: install the tag yourself or load it through a tag manager.
- Install it on your website. Either directly in the page code just before the closing body tag, or, cleaner and lower-maintenance, through Google Tag Manager. The tag manager is usually the better choice, since it lets you manage tracking changes without a developer.
- Deploy it on every page. The tag belongs on every subpage, not just the homepage. That's the only way LinkedIn sees the full journey across landing page, offer, and thank-you page.
- Define your conversion actions. Decide what counts as a conversion: a download, a contact request, a booked meeting. Once the tag is installed, LinkedIn can also automatically suggest clicks and page views as conversions, and you just pick which ones should count.
- Check that it's firing. Using the preview mode in Google Tag Manager or a tag-checking browser extension, confirm the tag fires on every page before you trust the data. In Campaign Manager, the status switches to active after the first hits come in.
Set up conversion tracking completely before your first campaign launches, not after. If you go live and add the tag later, you lose the first days of data for good and start the algorithm's learning phase on an empty base. A test lead through the built-in feature shows you whether the chain really holds all the way into your CRM, before real budget is running.
GDPR and consent: the tag only loads after consent
The Insight Tag sets cookies and processes personal data, so it belongs behind your consent banner. In practice, that means the tag may only load after the visitor has accepted marketing cookies, wired in cleanly through your consent management platform. If it loads earlier, you're collecting data without a clean legal basis, and that's not where you want to be.
The server-side Conversions API is generally considered more privacy-friendly in practice, since you control what data your server passes to LinkedIn yourself. But it also requires consent. Exactly how you configure consent and tracking is a legal question, not a technical one: when in doubt, clarify the details with whoever handles data protection at your company, rather than relying on a blanket rule of thumb. This is deliberately implementation guidance, not legal advice.
Why the Insight Tag alone isn't enough
The Insight Tag runs in the visitor's browser, and that's exactly where its weakness lies. Cookie blockers, iOS restrictions, ad blockers, and rejected consent banners all stop it from firing. The result: up to 40 percent of your conversions stay invisible. They happen, but they never show up in Campaign Manager.
For your numbers, that's a real problem. Your campaign looks worse than it actually is, you end up optimizing on half the data, and you may shift budget away from what's actually working well. The browser-based tag isn't wrong, it's incomplete. What's missing is a second channel that doesn't depend on the browser. That's exactly what the Conversions API is.
The Conversions API: the server-side upgrade
The Conversions API, CAPI for short, flips the logic. Instead of the visitor's browser reporting the conversion, your own server sends it directly to LinkedIn. No cookie, no blocker in between. In practice, that surfaces up to 42 percent more conversions, almost half of which simply weren't measurable before. There are two ways to connect it:
- Direct API connection. Your dev team sends events straight to the interface via webhooks. Maximum control, at the highest technical effort.
- Partner integration. Through a ready-made connection from your CRM or an automation tool like Zapier, you report events such as "lead created" or "demo booked" without writing any code yourself. The pragmatic path for most B2B teams.
Server-side tracking through Google Tag Manager is a technical middle ground: if you have a server container environment, you can send events to LinkedIn from there too, without building the full direct connection. Whichever path you choose, one thing is critical, or you'll end up overcounting.
If the Insight Tag and the Conversions API both report the same conversion, it should only count once. Deduplication via a unique event ID takes care of that. Set up CAPI through a CRM or a tool like Zapier, and this usually happens automatically. With a self-built setup through Google Tag Manager, you need to actively secure deduplication yourself, or you'll count conversions twice and think your campaign is performing better than it is.
When the Conversions API is worth it
The Insight Tag is mandatory, the Conversions API is the upgrade. Not everyone needs it from day one. As a rough guide:
- Almost always worth it if you use a CRM and have a long B2B sales cycle. Every recovered conversion counts double then, since the algorithm already has few data points to work with.
- Especially worth it when meetings or requests happen in external tools, say a booking tool on a different domain where the Insight Tag doesn't reach. The API reports the booking anyway.
- Can wait if you're just getting started, moving little budget, and still collecting your first data. A cleanly installed Insight Tag already covers most of the ground at that stage.
The effort is one-time, the benefit is ongoing. Once your budget starts to matter and you want to optimize toward real closed deals instead of mere downloads, there's no way around CAPI. For how to draw the right conclusions from the more complete data, see Optimizing Your Campaigns.
How the Insight Tag, CAPI, and offline conversions work together
LinkedIn recognizes three ways to count a conversion. A strong setup doesn't treat them as either-or, but combines them depending on the goal:
| Tracking type | How it measures | What it's strong for |
|---|---|---|
| Insight Tag | Browser-based and automatic. Detects actions on your website, such as a visit to the thank-you page. | The foundation. Classic website forms with their own thank-you page. The basis for retargeting. |
| Conversions API | Server-side. Your server reports the conversion directly, independent of cookies and browsers. | Recovers the up to 40% the browser loses. Meetings booked in external tools. Up to 42% more measured conversions. |
| CSV offline conversions | Manual. You export won deals from your CRM and upload them, LinkedIn matches by email address. | Optimizing toward real revenue instead of mere downloads. Invaluable for a long sales cycle. |
The Insight Tag delivers the fast online conversion, the API plugs the hole the browser tears open, and the CSV upload brings real revenue back into the system. Together, they make sure LinkedIn optimizes on complete data instead of a distorted picture.
That takes care of clean measurement. The second half of the truth is attribution: in a long B2B cycle with more than 30 touchpoints, who gets credit for the conversion, and why does LinkedIn often see less than your CRM? The overview on Tracking and Attribution covers that question. Once the foundation is in place, the next logical step is bringing warm website visitors back through retargeting. And one of the most common beginner mistakes is launching without tracking at all, more on that in common LinkedIn Ads mistakes.