Webclat / Signals
Signals  /  CAPI  /  LinkedIn Conversions API Implementation

LinkedIn Conversions API Implementation

Server-side conversion delivery for B2B campaigns on LinkedIn, including the offline conversions API for deals that close outside the web session - how it works, dedupe, consent, and verification.

Quick answer

LinkedIn Conversions API sends conversion events from your server directly to Campaign Manager, and its offline conversions API lets you feed back deals that close weeks after the original click - both matter more on LinkedIn specifically because of its high CPCs and long B2B sales cycles.

What LinkedIn Conversions API does

LinkedIn's Conversions API sends conversion events (form submissions, sign-ups, purchases) from your server directly to LinkedIn Campaign Manager, the same events your LinkedIn Insight Tag tracks from the browser. It is LinkedIn's version of the same server-side conversion pattern now standard across Meta, TikTok, and Google.

It carries particular weight for B2B advertisers on LinkedIn specifically because of two things measured directly in this practice's own keyword research: LinkedIn CPCs run exceptionally high relative to volume ($47-110+ per click on core conversions-api terms), and B2B sales cycles routinely extend well past the web session where a browser pixel could ever observe the outcome.

How delivery works

A server-side call to LinkedIn's Conversions API endpoint, carrying the conversion event, matched customer data (hashed email is the primary match key), and a conversion ID shared with the corresponding Insight Tag event where one fired.

Offline Conversions API - the B2B-specific mechanism

Separate from the standard Conversions API, LinkedIn's offline conversions capability lets you upload a conversion that happened outside any web session entirely - a closed-won deal, a qualified opportunity, a demo that converted to a contract weeks later. This requires capturing the LinkedIn click ID at the original ad click or form fill, storing it against the CRM record, and uploading the eventual outcome back to LinkedIn. For B2B, this is frequently the more valuable half of the implementation, because it is the only way LinkedIn's bidding algorithm ever sees actual revenue outcome instead of a form-fill proxy.

Dedupe with the Insight Tag

Send both the browser-side Insight Tag event and the server-side Conversions API event with a shared identifier for the same real-world action, so LinkedIn counts one conversion and uses whichever signal actually arrived - the same dedupe discipline as every other platform in this practice.

Consent handling

Gate both the standard Conversions API event and the offline conversion upload on recorded consent state - offline conversions in particular should not carry PII forward for a visitor who did not consent to tracking at the time of the original interaction.

How to verify it worked

  1. In Campaign Manager, open the conversion action and check its source breakdown - a server-side (API) source should appear alongside or instead of Insight Tag, depending on your setup
  2. Confirm match rate on the API-sourced conversions - a low rate usually traces to a missing or improperly hashed email field
  3. For offline conversions, confirm the upload batch shows accepted rows with no rejected matches, and spot-check that a known closed deal appears against the correct original campaign
  4. Fire a test conversion and confirm dedupe against a simultaneous Insight Tag event where applicable

Frequently Asked Questions

What is the LinkedIn Conversions API?

LinkedIn's Conversions API is a server-to-server connection that sends conversion events from your server directly to LinkedIn Campaign Manager, complementing the browser-based LinkedIn Insight Tag. It matters disproportionately for B2B advertisers because LinkedIn's CPCs run high and long B2B sales cycles make offline conversion matching especially valuable.

What is LinkedIn's offline conversions API, and is it different?

The offline conversions API is a related but distinct mechanism for uploading conversions that happen outside a web session - a deal closed by sales weeks after a form fill, matched back to the original click. Where the standard Conversions API covers web events (form submits, purchases), offline conversions cover the CRM-stage events a marketing-only pixel can never see.

Why does LinkedIn CAPI matter more for high-CPC campaigns?

hypothesis, reasoned from CPC data rather than measured on a specific account: when a platform's clicks cost $40-100+, every conversion lost to browser-side tracking failure represents a proportionally larger wasted-spend signal fed back into the bidding algorithm - a lower measured conversion rate on the same actual results makes LinkedIn's optimization worse, not just your reporting.

Does LinkedIn Conversions API need the Insight Tag too?

Yes, run both, deduplicated the same way Meta and TikTok recommend - a shared identifier so a single real conversion is not counted twice, and so LinkedIn can use whichever signal (browser or server) actually arrived.

Running High-CPC LinkedIn Campaigns On Form-Fill Data Alone?

If your bidding algorithm only ever sees a form submission and never the closed deal behind it, we will scope what an offline conversions implementation recovers.

Talk To The Practice