LinkedIn Conversions API: Complete Setup Guide for B2B

What is the LinkedIn Conversions API?

The LinkedIn Conversions API (CAPI) is a server-side tracking integration that sends conversion events directly from your server to LinkedIn's advertising platform. It works alongside the LinkedIn Insight Tag (browser pixel) to provide more complete conversion measurement for your LinkedIn Ads campaigns.

Think of it as LinkedIn's version of Meta's Conversions API or Google Enhanced Conversions — the same principle of server-side event delivery applied to LinkedIn's advertising ecosystem.

Why the Insight Tag alone isn't enough

LinkedIn's browser-based Insight Tag relies on JavaScript execution and cookies. Here's what breaks it:

The result: LinkedIn Ads reports show significantly fewer conversions than actually occurred, making your campaigns appear less effective than they are. This causes LinkedIn's optimization algorithm to receive incomplete training data, reducing campaign performance over time.

---

Why B2B needs LinkedIn CAPI more than e-commerce needs Meta CAPI

B2B companies are hit harder by tracking gaps than e-commerce for several structural reasons:

1. Higher ad blocker usage among professionals

The average consumer ad blocker adoption is 30-37%. Among technology professionals, marketers, and enterprise decision-makers — exactly the audience most B2B companies target on LinkedIn — the rate is 40-55%. Your ideal customer profile is disproportionately invisible to browser-based tracking.

2. Long sales cycles break cookie-based attribution

When your sales cycle exceeds 7 days, Safari users lose attribution entirely. For enterprise deals with 3-6 month cycles, even Chrome cookie persistence is insufficient. Server-side tracking with hashed email matching is the only way to connect the original LinkedIn ad click to the eventual conversion.

3. Multi-stakeholder buying decisions

In B2B, the person who clicks your LinkedIn ad is often not the person who fills out the form. A VP sees your ad, forwards the link to their team lead, who evaluates and later submits a demo request from a different device and browser. Browser-based tracking can't connect these touchpoints. Server-side tracking can — by matching the form submission's email hash to LinkedIn's database of ad viewers.

4. Downstream conversions matter most

In e-commerce, the purchase is the final conversion. In B2B, the form submission is just the beginning:

Form fill → MQL → SQL → Opportunity → Closed-Won ($$$)

LinkedIn's browser pixel only sees the form fill. The Conversions API lets you send every downstream stage back to LinkedIn, so the algorithm learns to optimize for qualified leads and closed deals, not just form volume.

---

Setting up the LinkedIn Conversions API

Prerequisites

Before you start, you need:

• A LinkedIn Campaign Manager account with admin access
• At least one active LinkedIn Ads campaign
• Server-side infrastructure to send HTTP requests (or a tool like SignalBridge)
• Conversion events defined in LinkedIn Campaign Manager

Step 1: Create a Conversions API access token

1. Go to LinkedIn Campaign Manager → Account Settings
2. Navigate to Conversions API section
3. Click Generate Access Token
4. Copy and securely store the token — you will need it for API calls
5. Note your Ad Account ID (visible in Campaign Manager URL)

Step 2: Define your conversion events in Campaign Manager

Set up the conversion events that your server will send:

In LinkedIn Campaign Manager:

1. Go to Analyze → Conversion tracking
2. Click Create a conversion
3. Select Conversions API as the data source
4. Name the conversion and set the conversion type
5. Repeat for each event in your funnel

Step 3: Implement server-side event sending

The LinkedIn Conversions API accepts POST requests with conversion event data. Here's the data flow:

User fills out form on your website
→ Your server captures form data (email, company, etc.)
→ Server hashes the email address (SHA-256)
→ Server sends POST request to LinkedIn Conversions API:
   - Conversion rule ID
   - Hashed email (for matching)
   - Conversion timestamp
   - Conversion value (if applicable)
→ LinkedIn matches hashed email to LinkedIn member
→ Conversion attributed to the original ad click/view

Required data for each event:

Matching identifiers (in order of match quality):

1. SHA256 email — Most reliable. Hash the lowercase, trimmed email with SHA-256 before sending
2. LinkedIn first-party cookie — The li_fat_id cookie from the Insight Tag, if available
3. First + last name + company — Fallback matching when email isn't available

Step 4: Configure deduplication

If you're running both the LinkedIn Insight Tag and the Conversions API (recommended), you need deduplication to prevent double-counting conversions.

LinkedIn uses eventId for deduplication:

1. Generate a unique eventId for each conversion event
2. Include the same eventId in both the Insight Tag event and the CAPI event
3. LinkedIn automatically deduplicates events with matching IDs, keeping the server-side event for attribution

Step 5: Implement offline conversion tracking

This is where LinkedIn CAPI delivers the most B2B value. Send downstream funnel events back to LinkedIn:

MQL event (when a lead qualifies):

• Fire when your marketing team qualifies a lead
• Include the lead's hashed email
• LinkedIn attributes this to the original ad interaction

SQL event (when sales accepts the lead):

• Fire when sales confirms the lead is worth pursuing
• Signals to LinkedIn that this ad click produced a sales-worthy lead

Closed-Won event (when the deal closes):

• Fire when the deal is signed
• Include the deal value in conversionValue
• LinkedIn can now optimize for revenue, not just leads

Timeline example:
Day 1: VP clicks LinkedIn ad → visits landing page
Day 3: Team lead fills out demo form → CAPI sends Lead event
Day 14: Lead qualifies as MQL → CAPI sends MQL event
Day 30: Sales qualifies as SQL → CAPI sends SQL event
Day 75: Deal closes for $50,000 → CAPI sends Closed-Won with value

LinkedIn now knows: this ad click → $50,000 in revenue
Next time: LinkedIn optimizes to find more VPs like this one

---

Measuring LinkedIn CAPI effectiveness

After implementing, track these metrics to verify the integration is working:

---

LinkedIn CAPI vs. Meta CAPI vs. Google Enhanced Conversions

The key difference for B2B: LinkedIn CAPI's offline conversion capability lets you close the loop on deals that take weeks or months, which is rare in Meta or Google (where conversions are typically immediate).

---

Getting started with server-side tracking for LinkedIn

SignalBridge simplifies server-side tracking across all ad platforms, including LinkedIn. For B2B companies running LinkedIn Ads alongside Google Ads and Meta Ads:

1. Install the SignalBridge pixel on your website
2. Connect your first-party subdomain for cookie persistence
3. Connect LinkedIn alongside your other ad platforms
4. Define conversion events that map to your B2B funnel stages
5. Set up offline conversion imports for MQL, SQL, and Closed-Won events

Server-side events are deduplicated with Insight Tag events automatically. Your tracking health dashboard monitors delivery status across all connected platforms.

For B2B lead generation best practices beyond LinkedIn, see our complete guide to server-side tracking for lead generation.

---

FAQ

Does the LinkedIn Conversions API replace the Insight Tag?

No. LinkedIn recommends running both the Insight Tag and CAPI together. The Insight Tag handles real-time retargeting audiences and some event tracking, while CAPI provides server-side conversion data for attribution and optimization. The deduplication system ensures events aren't double-counted.

What LinkedIn Ad formats benefit most from CAPI?

All formats benefit, but Sponsored Content (single image, video, carousel) and Message Ads see the largest improvement because they drive traffic to your website where ad blockers and cookie issues are most impactful. Lead Gen Forms, which keep users on LinkedIn, are less affected by browser-based tracking issues but still benefit from offline conversion imports.

How long does it take for LinkedIn to start optimizing on CAPI data?

LinkedIn's algorithm needs approximately 15-30 conversions tracked via CAPI to begin meaningful optimization. For campaigns with lower volume, this may take 2-4 weeks. Offline conversion data (MQL, SQL, Closed-Won) takes longer to accumulate but provides the highest quality optimization signal once LinkedIn has enough data.

Can I track LinkedIn Lead Gen Form submissions via CAPI?

LinkedIn Lead Gen Forms are handled differently since the form submission happens on LinkedIn's platform, not your website. However, you can use CAPI to send downstream events (MQL, SQL, Closed-Won) for leads that originated from Lead Gen Forms by matching the lead's email hash. This closes the loop between lead capture and revenue.

Is LinkedIn CAPI available for all ad account types?

LinkedIn CAPI is available for all Campaign Manager accounts with active campaigns. There are no minimum spend requirements. However, you need admin access to the ad account to generate the API access token and configure conversion events.

How does LinkedIn CAPI handle data privacy and GDPR?

All identifiers sent via CAPI must be hashed with SHA-256 before transmission. LinkedIn never receives raw email addresses or personal data through the API. You are responsible for having a legal basis for processing (typically legitimate interest or consent) and for including LinkedIn CAPI in your privacy policy's data sharing disclosures.