LinkedIn Insight Tag vs Conversions API: which one do you need?

Short answer: the Insight Tag watches what people do in the browser, while the Conversions API sends events from your server or CRM. Most B2B teams end up wanting both, because the tag catches on-site actions and the API catches what happens after the visitor leaves.

Let me use a made-up example. A consulting firm runs LinkedIn ads to a whitepaper page. The Insight Tag records the download. Three weeks later a sales call happens, and two months later the client signs. None of that happens in a browser the tag can see. Without the API, LinkedIn only knows about the download.

The Insight Tag is a script on your pages. It builds audiences from site visitors, reports page-based conversions, and gives you demographic reporting. It is easy to install and it works without any developer time beyond adding the script. Its weak points are the usual ones for browser tracking: ad blockers, consent choices and tightened browser privacy can stop it.

The Conversions API is different. You send an event, such as a qualified lead or a closed deal, from your own system, along with something LinkedIn can use to match it to a member. That makes it a good fit for anything that happens offline or later, like calls, demos and signed contracts.

Matching is where people get stuck, so here it is plainly. LinkedIn can match on a hashed email address, on the li_fat_id click identifier, or on a combination of name plus company or job title. It does not match on phone number. If your CRM mostly holds phone numbers, that will hurt, so make sure you capture email at the form.

Another detail: conversions can be up to 90 days old when you send them. Check the current documentation for the exact rules, since these limits can change. A deal that closes on day 120 will not be accepted, so send an earlier stage if your cycle is long.

The li_fat_id is worth capturing. When the ad is clicked, LinkedIn can add that identifier to your landing page address. If you save it with the lead and send it back with the event, matching improves because LinkedIn no longer has to guess from an email.

So which one do you need? A simple way to decide.

If you only care about on-site actions and audience building, and your visitors mostly accept tracking, the Insight Tag alone is enough.

If your real goal is a signed deal, a booked call or a paid invoice, you need the API, because those events live in your CRM.

If you want the most complete picture, run both, and make sure the same event is not counted twice. Use a shared event identifier where the platform supports it, and check the current documentation for how deduplication works.

Honest limit: the API only helps if your CRM stores the identifiers at the moment of the lead. If a form did not capture email or the click ID, the event cannot be matched later, and no tool can rebuild that.

Which stage of your funnel are you trying to send to LinkedIn?