LinkedIn CAPI: How to Set Up the Conversions API for B2B SaaS

Tracking conversions gets harder as the B2B SaaS buying journey gets longer. Someone might click a LinkedIn ad, visit your website, request a demo, and only become a qualified lead or customer weeks later. Browser-based tracking can struggle to connect those later actions back to the original ad.

LinkedIn CAPI helps close that gap by sending conversion data directly from your server or CRM to LinkedIn. That gives your team a more complete view of the leads, demos, and deals coming from LinkedIn ads. 

In this guide, we'll walk through how LinkedIn CAPI works, how to set it up, and how to make sure your conversion data is being matched correctly.

What Is LinkedIn CAPI?

LinkedIn CAPI is a server-to-server connection that lets you send conversion events to LinkedIn Campaign Manager without depending on a browser. LinkedIn says you can send both online and offline events, and that the API works best when used together with the Insight Tag.

A conversion event is a record of something valuable a person did. Examples include a demo request, a free trial signup, a sales qualified lead, or a closed deal. Each event carries a timestamp and at least one identifier, such as a hashed email address. LinkedIn uses that identifier to match the event to a member who saw or clicked your ad.

You will see three names for the same integration: LinkedIn CAPI, LinkedIn Conversions API, and LinkedIn conversion tracking API. The phrase "LinkedIn conversion tracking" is broader. It covers every way to record conversions, including the Insight Tag, Lead Gen Forms, and the API.

Why Do B2B SaaS Teams Need LinkedIn CAPI?

B2B SaaS teams need LinkedIn CAPI because the buying journey happens in many places, and the Insight Tag can only watch one of them. A buyer might see your ad on a phone, read your pricing page on a laptop, and book a demo two weeks later after talking to a colleague. The moments that matter most often happen inside your CRM, where a browser tag cannot reach.

Three gaps show up again and again:

1. Browser gaps. Ad blockers, privacy settings, and expired cookies stop some Insight Tag events from firing. CAPI sends events from your own systems, so the browser plays no part.
2. Funnel gaps. A form fill is only the first step toward a customer. Without CRM stages, LinkedIn learns to find people who fill out forms instead of people who buy.
3. Time gaps. B2B deals take weeks or months to close. A conversion that happens long after the click needs a path back to the original ad exposure.

These gaps cost real money. When we built the LinkedIn program for Oneleet, a SOC 2 compliance platform, LinkedIn's own dashboard showed a 0.36x return. Multi-touch attribution later credited roughly 7x more revenue than the platform reported. It also showed $1.63M in LinkedIn-influenced closed-won revenue across 150 deals. 

You can read the full Oneleet LinkedIn Ads case study for the details.

Those numbers came from attribution software rather than from CAPI. They show how far native reporting can drift from reality in a long sales cycle. CAPI helps on LinkedIn's side of that gap, because LinkedIn can only use matched events for attribution and optimization. Every deal stage you send is one more signal the platform can learn from.

How Does LinkedIn CAPI Work?

LinkedIn CAPI works by passing a conversion from your system to LinkedIn, where it is matched to a member and then to an ad. Here is the flow:

1. Someone clicks your LinkedIn ad. When enhanced conversion tracking is on, LinkedIn adds a click ID called li_fat_id to your landing page URL.
2. Your site stores that ID with the visitor record or form submission.
3. The person converts, or your CRM moves them to a new stage. Your system then sends an event to LinkedIn with the click ID and a hashed email.
4. LinkedIn matches the event to a member, then checks whether that member clicked or viewed your ad inside the attribution window.
5. Matched events appear in Campaign Manager and feed your bidding and optimization.

LinkedIn describes two separate match steps. Identity matching asks whether the identifiers belong to a LinkedIn member. Attribution matching asks whether that member was served your ad and engaged with it inside the window. An event has to pass both steps to count toward a campaign.

Do You Need Both the Insight Tag and CAPI?

Yes, you should run both. LinkedIn recommends sending events through the Insight Tag and the Conversions API together, because the tag covers browser actions and the API covers everything your servers and CRM know. 

The table below shows how they split the work.

[table]
Feature | Insight Tag | Conversions API
Where it runs | The visitor's browser | Your server, CRM, or a partner tool
What it sees | Page loads and on-site actions | Anything your systems record, online or offline
Affected by ad blockers and cookie limits | Yes | No, because no browser is involved
Offline and CRM events | No | Yes
Website retargeting and demographics | Yes | No
How it matches people | Browser cookies | Hashed email, click ID, and other identifiers
Setup effort | Low, one code snippet | Medium, needs a partner tool or a developer
Duplicate handling | Counted when both send the same event ID | Discarded when the Insight Tag already sent it
[/table]


The last row matters for your reports. LinkedIn's deduplication guide explains that when both sources send the same event ID, LinkedIn keeps the Insight Tag event and discards the API event. If you see both conversions in your breakdown, the Insight Tag count should be the higher one.

What Do You Need Before You Start?

Gather these items first. Each one prevents later delays.

• Campaign Manager access with permission to create conversions.
• A working Insight Tag. If you have not installed it yet, start with our LinkedIn Insight Tag guide.
• A short event list. Write down each valuable action and where it is recorded: your website, your product, or your CRM.
• A way to capture the click ID and email at the moment someone fills out a form.
• A developer or a partner tool that can send events to LinkedIn.
• A privacy review. Hashing protects the email in transit, but you still need to follow your consent rules. Involve your legal team early.

Which LinkedIn CAPI Setup Path Should You Choose?

LinkedIn lists two options: use a partner integration or build a direct integration. A partner gives you a quick, one-time setup with limited technical work, though some partners charge fees. A direct build gives you the most control, but it needs developer time and ongoing upkeep. LinkedIn puts the average direct build at 1 to 2 weeks.

In practice, B2B SaaS teams choose among three paths:

• A partner or CRM connector. LinkedIn names Google Tag Manager, Zapier, Dreamdata, Supermetrics, Tealium, and Adobe among its partners. This path suits lean teams whose key conversions already live in HubSpot or Salesforce.
• Server-side Google Tag Manager. This suits teams that already run a server container. You add a LinkedIn CAPI tag template, connect your access token and conversion rule, and fire it from your existing events.
• A direct API build. This suits teams whose key events live in a product database or a custom backend, and teams that want full control over the data they share.

Our rule of thumb is simple. If your most valuable conversions sit in a CRM, start with a connector. If they sit in your product, build direct.

How to Set Up LinkedIn CAPI Step by Step

Follow these eight steps to set up LinkedIn CAPI. 

Step 1: Turn On Enhanced Conversion Tracking

Enhanced conversion tracking lets LinkedIn add the li_fat_id click ID to your landing page URLs. This ID is LinkedIn's first-party click identifier, and it sharply improves matching. LinkedIn stores the link between a li_fat_id and a member profile for 365 days. You can still use the ID within that window, even after the browser cookie expires.

Step 2: Create the Conversions API Data Source

In Campaign Manager, go to Analyze, then Conversion tracking, then Data sources. Select Create source, then choose Conversions API or CSV. Pick Direct API, a partner logo, or an offline conversions partner. Finish the prompts and agree to the terms. You must complete this before you can create the conversion itself.

Step 3: Create One Conversion Rule Per Event and Per Source

Create a conversion rule for each business action, and name it plainly, such as "Demo request" or "Sales qualified lead." Choose the category that fits, such as Lead, Sign up, Qualified lead, or Purchase.

Then set the attribution windows. LinkedIn suggests 90-day click and 90-day view for lead or lower-funnel conversions, and 30-day click and 7-day view for website conversions. For several lead and purchase categories, you can also choose 180 or 365 days. Match the window to your real sales cycle.

One detail trips up many teams. For any event you send through both the browser and the server, create a separate conversion rule for each source. A common naming pattern is "Demo request (Insight Tag)" and "Demo request (CAPI)." Deduplication needs this setup to work.

Step 4: Capture and Hash Your Identifiers

LinkedIn needs at least one valid identifier on every event. Supported options include a hashed email, the li_fat_id, IP address, and a few others. LinkedIn recommends sending both the hashed email and the li_fat_id for the best matching.

Capture the click ID from the landing page URL and store it with the visitor record. When someone submits a form, save their email too. Before sending, convert the email to lowercase and hash it with SHA-256, without salting. Hashing turns the email into a fixed string of characters that LinkedIn can match without seeing the plain address.

Step 5: Send Your Events to LinkedIn

Your system sends each event with a POST request to https://api.linkedin.com/rest/conversionEvents. The Conversions API reference shows the full format. Keep these rules in mind:

• The conversion value points to the conversion rule you created in Step 3.
• The time must be in milliseconds. If your system records seconds, add three zeros.
• The eventId is optional, but you need it for deduplication.
• You can send up to 5,000 events in one batch request.
• LinkedIn allows 600 requests per minute and 500,000 requests per day per access token.
• Send events as they happen, or at least within a day, so LinkedIn can use them while the campaign data is fresh.

Authentication takes a few extra pieces. You create a LinkedIn developer app, request access to the Conversions API product, and generate an access token with the conversions write permission. Tokens expire, so plan how you will renew them. LinkedIn also retires old API versions. For example, version 202510 is scheduled to sunset on October 15, 2026, so check which version your setup uses.

Step 6: Set Up Deduplication

Generate one unique ID for each conversion event. Send that same ID with the browser event from the Insight Tag and with the server event from the API. On a manual Insight Tag install, you pass it in the lintrk call as event_id. In Google Tag Manager, you push it to the data layer and read it with a variable.

When LinkedIn sees the same ID from both sources, it counts the Insight Tag event once and removes the duplicate. This protects you from inflated numbers.

Step 7: Test Before You Trust the Data

Send a test event and check the response. A 201 response means LinkedIn accepted it. A 422 error usually means a required field is missing. The most common cause is a missing userIds field, which must be present even when you identify the person another way, in which case you send it as an empty list.

Then confirm the data source and conversion rule show activity in Campaign Manager.

Step 8: Review Your Match Rate After 72 Hours

LinkedIn needs up to 24 hours to ingest events and up to 48 more hours to show them in reports. That means complete data can take up to 72 hours to appear. Check both identity match and attribution match once the data lands, then fix gaps using the tips in the match rate section below.

Which Events Should B2B SaaS Teams Send Through CAPI?

B2B SaaS teams should send events from each stage of the funnel, starting with a small set of four or five. LinkedIn supports categories that fit a SaaS pipeline well, including Lead, Qualified lead, and Purchase. Marketing qualified lead and sales qualified lead categories became available with API version 202608.

A practical starting list looks like this:

• Demo request or contact form: send as Lead.
• Free trial or product signup: send as Sign up.
• Marketing qualified lead: send as Marketing qualified lead.
• Sales qualified lead: send as Sales qualified lead.
• Opportunity created: send as Qualified lead.
• Closed won: send as Purchase, with the deal value.

Match your CRM stage names to these categories before you build anything. Then decide which event each campaign should optimize toward. 

One rule of thumb is to optimize toward the deepest event that still gives you steady volume, and to report on the deeper events even when they are too rare to optimize on. 

This is the same logic we explain in our guide to offline conversion tracking for Google Ads, and it applies to LinkedIn just as well.

How Do You Improve Your LinkedIn CAPI Match Rate?

You improve your match rate by sending more identifiers with each event and by sending them accurately. LinkedIn states that the more IDs you include, the more likely it can match an event to a member, and only matched events can be used for attribution and optimization.

Use this checklist:

• Send the hashed email and the li_fat_id on every event that has them.
• Lowercase the email before hashing it.
• Store the click ID at the first page view, so it is available when the person converts weeks later.
• Add extra details LinkedIn supports, such as first name, last name, company name, job title, and country.
• Send CRM events with the same email that the person used when they first engaged.
• Send events quickly instead of in large delayed batches.

Email mismatch is a common cause of weak B2B matching. A buyer may use one email on your form and a different one on their LinkedIn profile. The click ID solves most of this, because it ties the event to the exact ad click.

LinkedIn's conversions FAQ does not set a target match rate. Record your own baseline in the first week, then track whether each fix moves it up.

What Mistakes Break a LinkedIn CAPI Setup?

Most CAPI problems come from small setup errors that fail without any warning. These are the ones we would check first:

• One conversion rule for both sources. Deduplication needs a separate rule for the browser and the server.
• Timestamps in seconds. LinkedIn expects milliseconds.
• Unhashed or inconsistent emails. Always lowercase and hash with SHA-256 first.
• No click ID. Without enhanced conversion tracking, you lose the strongest matching signal.
• Missing user fields. An event without a valid identifier is rejected.
• Late events. Days of delay shrink the value of each event for optimization.
• Windows shorter than the sales cycle. Long deals fall outside the window and disappear from reports.
• Expired tokens or retired API versions. Both can stop events from arriving without an obvious error in Campaign Manager.
• Counting twice in reports. If both conversion rules feed a campaign and deduplication is missing, totals inflate.

What Do Real B2B SaaS Accounts Show About LinkedIn Measurement?

Real accounts show that LinkedIn drives more revenue than native reporting credits, and that the gap grows with sales cycle length. We saw this happen with two of our clients.

In one account, a B2B SaaS client spent $24,162 on LinkedIn Ads over 90 days. The CRM showed mostly direct traffic and Google Ads. Company-level attribution then revealed $779,280 in closed revenue, a 32.25x return on ad spend. Of the 12 won deals, 5 were influenced by both paid and organic touchpoints. We break down the full method in our post on LinkedIn Ads attribution for B2B SaaS.

Wispr Flow had a live LinkedIn account that could not tie activity to revenue. ScalixAI rebuilt the program around a full-funnel structure and deal-level attribution. In 90 days, the account produced 25 closed-won deals and $856K in influenced revenue at a 5.96% click-through rate. You can read the details in the Wispr Flow case study.

Both accounts used attribution software to measure revenue. CAPI plays a different role. It gives LinkedIn the deeper conversion signals it needs to optimize, while your attribution tool keeps judging which deals LinkedIn influenced. The strongest setups use both. 

If you want the full picture of how LinkedIn works alongside search, read our guide on running Google Ads and LinkedIn Ads as one system.

Should You Build LinkedIn CAPI Yourself?

You can build it yourself if you have a developer, a short event list, and a CRM that already holds clean stage data. A basic web conversion setup through a partner tool often takes a few days. A full setup with CRM stages, several conversion rules, and deduplication takes longer and needs ongoing checks.

Outside help makes sense when your sales cycle is long, your CRM stages are messy, or LinkedIn spend is large enough that bad data wastes real budget. ScalixAI builds tracking from click to closed deal for B2B SaaS teams, including Insight Tag setup, offline CRM conversions, and company-level attribution. It does this as part of its LinkedIn Ads management for B2B SaaS. 

If you want a wider view first, start with our playbook on LinkedIn Ads for B2B SaaS or check the LinkedIn Ads cost benchmarks to see what your spend should buy.

The Bottom Line 

LinkedIn CAPI gives B2B SaaS teams a more reliable way to connect LinkedIn ads with the conversions that happen after the initial click. When your server and CRM data are connected properly, LinkedIn gets better signals to optimize campaigns toward the leads and customers that actually matter.

The goal isn't to replace browser tracking. It's to give LinkedIn better data to work with, while your own attribution system shows what those conversions are worth.

Want to see where your LinkedIn tracking could improve? Book a free audit with ScalixAI, and we'll help you identify the gaps.