How to Set Up the LinkedIn Conversions API: Step by Step, No Developer
LinkedInConversions APIServer-Side TrackingB2B

How to Set Up the LinkedIn Conversions API: Step by Step, No Developer

LinkedIn clicks are expensive, and every conversion the Insight Tag misses makes your campaigns worse. This guide explains what the LinkedIn Conversions API is, which data LinkedIn needs to match conversions and how to set it up without a developer or a GTM server.

Published October 26, 20269 min read

On LinkedIn, B2B advertisers often pay far more per click than on Meta. At the same time, they usually collect only a handful of leads per month: demo requests, whitepaper downloads, contact forms. If part of them never reaches LinkedIn, the algorithm lacks exactly the signal it is supposed to optimise for. With small conversion numbers, every lost lead makes a noticeable difference.

The LinkedIn Conversions API closes that gap. In this article you will learn how it differs from the Insight Tag, which data LinkedIn needs to match conversions and how to set it up step by step, without a developer and without your own tracking server.

Insight Tag vs. Conversions API: what is the difference?

The LinkedIn Insight Tag is a JavaScript pixel on your website. It measures conversions in the visitor's browser and sends them straight to LinkedIn. The Conversions API is an interface that sends conversions to LinkedIn from a server instead of the browser.

Insight TagConversions API
Where does it run?In the visitor's browserOn a server
Affected by ad blockersYesNo, the browser does not send directly to LinkedIn
Affected by browser restrictions like ITPYes, cookies may live shorterLess, matching uses hashed email or the click ID
Matching viaLinkedIn cookies in the browserHashed email and the LinkedIn click ID li_fat_id
SetupAdd a scriptNeeds a technical connection to a server

LinkedIn recommends using both together. The Insight Tag delivers the browser signals, the Conversions API catches what gets lost there. So that LinkedIn does not count the same conversion twice, both send a shared event ID. This is called event deduplication.

Why B2B campaigns benefit in particular

Three reasons make the Conversions API especially interesting for B2B:

  • Ad blockers and company laptops. Many B2B visitors browse on work devices with ad blockers, browser extensions or security policies that block tracking scripts. The Insight Tag never gets a chance to fire.
  • Few conversions. If you get 20 demo requests a month, you cannot afford five of them to stay invisible. The algorithm learns from every single one.
  • Business email addresses. B2B leads almost always leave their work email. Many people are registered on LinkedIn with exactly that address, which is a good basis for matching via the Conversions API.

Which data LinkedIn needs to match conversions

For LinkedIn to attribute a conversion to an ad click, the event must contain at least one identifier LinkedIn can recognise the user by. LeadSignal only sends a conversion to the Conversions API if one of these two is present:

  • The email address, as a SHA-256 hash. LinkedIn does not receive the address in plain text but a fingerprint of it, which it compares with its own data.
  • The li_fat_id, LinkedIn's click ID. It is added to the URL when someone clicks your ad, provided enhanced conversion tracking is enabled in your Campaign Manager account.

First and last name, country and, if set, conversion value and currency are sent as well. That improves the match rate and helps LinkedIn recognise more valuable conversions.

Check in your Campaign Manager account settings that enhanced conversion tracking is switched on. Only then does LinkedIn append the li_fat_id to the click URL. The exact label in the interface changes now and then.

What to prepare

For the setup you need access to LinkedIn Campaign Manager with sufficient permissions on the ad account, plus four things:

  1. The partner ID of your Insight Tag.
  2. At least one conversion in Campaign Manager, for example "Lead form".
  3. The conversion ID of that conversion.
  4. An access token for the Conversions API.

The menu paths below reflect October 2026. LinkedIn redesigns Campaign Manager regularly, but the terms usually stay the same.

Step by step with LeadSignal

1. Copy the partner ID

In Campaign Manager you find the partner ID under Analyze, Insight Tag. It is a short number. You do not need to install the Insight Tag code yourself, the LeadSignal script takes care of that.

If the Insight Tag is already on your website directly or via a plugin: remove it once LeadSignal is running. Otherwise the tag loads twice and bypasses your cookie banner.

2. Create a conversion and note the conversion ID

Under Analyze, Conversion tracking create a conversion for every action you want to measure, such as "Demo requested" or "Whitepaper downloaded". Note the conversion ID LinkedIn assigns.

Use the same conversion for browser and server. Only then can LinkedIn merge the two reports via the shared event ID.

3. Generate an access token

The token allows LeadSignal to send conversions to LinkedIn on behalf of your ad account. You generate it in Campaign Manager in the Insight Tag or Conversions API area. Treat it like a password and do not share it by email.

4. Connect LinkedIn in LeadSignal

Open the integrations in your LeadSignal project and choose LinkedIn. Enter the partner ID and the access token and enable both paths:

  • Client-side: loads the Insight Tag in the browser after the visitor has consented.
  • Server-side (Conversion API): additionally sends the conversions from the server.

The connection test immediately checks whether the token is valid. LeadSignal automatically adds the LinkedIn cookie li_fat_id to your banner's cookie list.

5. Map events to conversions

Now link your LeadSignal events to the LinkedIn conversions. For every event that should go to LinkedIn, enter a name and the conversion ID from step 2. A typical B2B setup:

LeadSignal eventTriggerLinkedIn conversion
Demo requestedPage /thank-you-demoDemo requested (conversion ID 1)
WhitepaperPage /thank-you-whitepaperDownload (conversion ID 2)
ContactPage /thank-you-contactLead (conversion ID 3)

A thank-you page as the trigger is the most reliable option, because only people who actually submitted a form see it. Our article on conversion tracking in WordPress shows how to set this up, for example.

6. Make sure the email arrives

For the Conversions API, the email is the most important data point. LeadSignal detects fields like email, phone, first and last name in forms on your site automatically and attaches them to the following events. For most contact and demo forms you do not need to do anything else.

Two special cases:

  • Embedded forms from third-party tools often run in an iframe. A script on your page cannot read what is typed there. Passing the contact data to the thank-you page as URL parameters or calling leadsignal.identify() helps here.
  • Booking tools such as calendar widgets often redirect to a page of your own after the booking. If you pass email and name as URL parameters, LeadSignal can pick them up.

If neither email nor li_fat_id is present, LeadSignal does not send the conversion to the Conversions API. The Insight Tag still measures in the browser, as long as it was allowed to load.

7. Test

Run a real test: open the site in a private window, accept in the cookie banner, submit the form with a test email.

  • In LeadSignal you see the event in the event log with all details and the session timeline.
  • In Campaign Manager the conversion overview shows whether data is arriving. New conversions do not appear instantly, allow a few hours.

LeadSignal only loads the Insight Tag after the visitor has consented to the marketing category. For server-side forwarding there is one important setting:

  • In standard consent mode, events can reach the Conversions API before consent.
  • In restricted consent mode, nothing but the consent decision leaves the browser before marketing consent.

For websites with visitors from the EU we recommend the restricted mode. It matches a privacy policy that promises data only goes to ad platforms after consent. Read more in the guide to GDPR-compliant tracking.

Common mistakes and how to avoid them

The conversion fires before the email is known. A click on "Book a demo" is not a demo request yet. If you send a button click event to LinkedIn, the email is often missing at that moment. Measure the completion, the thank-you page after the form.

Wrong conversion ID. A swapped or outdated ID sends the data nowhere. Compare the IDs with Campaign Manager once after setup.

Expired token. Access tokens are not valid forever. If server-side conversions suddenly stop, check the token with the connection test and generate a new one if needed.

Redirects drop the li_fat_id. Some redirect or language plugins strip URL parameters. Test this by adding ?li_fat_id=test to your landing page URL and checking whether the parameter survives the redirect.

LinkedIn Lead Gen Forms. If your ads use LinkedIn's native forms, the conversion happens on LinkedIn, not on your website. LinkedIn measures those itself. You need the Conversions API for everything that happens on your own site.

What about deals from the CRM?

In B2B, the lead is rarely the real goal. It gets interesting when the demo turns into a proposal and the proposal into a deal. Those steps happen in the CRM, often weeks later, not on your website.

LeadSignal measures what happens on your website and sends it to LinkedIn. If you also want to send opportunities and won deals from your CRM back to LinkedIn, our sister product LeadMetrics is built for that.

Conclusion

For B2B campaigns, the LinkedIn Conversions API is one of the most effective levers for better data: it catches conversions the Insight Tag loses and gives the algorithm more signals when lead numbers are scarce anyway. Three things matter: the same conversion for tag and API, an email or li_fat_id on every event, and clean consent.

The LinkedIn integration page shows what the connection looks like in LeadSignal. And to see how the approach works across all platforms, read the guide to server-side tracking without GTM.

Terms in this article

Related guides

More articles