Quick Summary
Summarize this article instantly with your preferred AI model.
LinkedIn Conversions API for B2B SaaS: Why Offline Conversions Matter
LinkedIn Conversions API for B2B SaaS: Why Offline Conversions Matter
In B2B SaaS, the conversions that actually matter (sales-qualified leads, opportunities, closed-won deals) happen offline, weeks or months after the click, on sales calls and inside your CRM. LinkedIn never sees them. So by default, LinkedIn optimizes and attributes on the thin slice it can track: online form-fills. That is the core reason so many accounts optimize toward cheap leads instead of pipeline. The LinkedIn Conversions API (CAPI) fixes it by streaming your online and offline conversions server-side back to LinkedIn, which LinkedIn has found reduces cost per acquisition by around 20 percent and increases attributed conversions by around 31 percent. This is why offline conversions matter, and how to send them.
Key takeaways
- Most B2B SaaS conversions (SQLs, opportunities, deals) happen offline in the CRM, so LinkedIn never sees them.
- By default LinkedIn optimizes on online form-fills, which pushes it toward cheap leads, not pipeline.
- The Conversions API streams online and offline conversions server-side to LinkedIn, connecting CRM and pipeline data.
- CAPI has been found to reduce CPA ~20 percent and increase attributed conversions ~31 percent.
- Only matched events optimize and attribute, so send multiple hashed identifiers to lift match rates.
The problem: LinkedIn optimizes on what it can see
LinkedIn’s algorithm optimizes toward the conversions you feed it. Out of the box, the only conversions it can track are online events on your website via the Insight Tag: a form submit, a page view, a click. But in B2B SaaS, those online events are not the outcomes that matter. The outcomes that matter (a lead becoming an SQL, an opportunity opening, a deal closing) happen later and offline, in conversations with sales and as stages in your CRM. So LinkedIn is optimizing and reporting on a proxy (form-fills) that is only loosely connected to revenue, which is exactly how an account ends up generating cheap leads that never become pipeline. You cannot optimize for an outcome the platform cannot see, and by default it cannot see your pipeline.
This is compounded by privacy changes. Cookie restrictions and the phase-out of third-party cookies make client-side (pixel) tracking increasingly unreliable, so even the online conversions LinkedIn used to see are being under-counted. The combination (offline conversions it never saw, plus online conversions it is losing to privacy changes) means the default setup shows LinkedIn a shrinking, unrepresentative slice of what its ads actually produced.
What the Conversions API is
The Conversions API is LinkedIn’s server-side conversion tracking (the successor to Offline Conversions). Instead of relying only on a browser pixel, you send conversion data directly from your server or CRM to LinkedIn, connecting both your online and offline data. That lets LinkedIn see how your campaigns influenced actions across the full journey: form fills on your website, sales completed over the phone, leads collected in person at an event, and stage changes in your CRM like MQL, SQL, opportunity, and closed-won. In other words, CAPI is how you tell LinkedIn what actually happened to the leads it generated, so the platform can measure and optimize against real outcomes rather than a form-fill proxy.
The data: why it works
Feeding LinkedIn real conversion data changes two things, and the numbers back it up. On optimization, LinkedIn has reported that Conversions API implementations reduce cost per acquisition by around 20 percent, because the algorithm can now optimize toward the conversions that matter instead of the ones it happened to see. On measurement, CAPI has been found to increase attributed conversions to LinkedIn ads by around 31 percent, because it captures conversions the pixel missed (offline ones, and online ones lost to privacy changes). It is also privacy-resilient by design: a server-to-server connection does not depend on cookies, so it holds up as browser tracking degrades. The one rule that governs all of this: only matched events can be used for attribution and optimization, so match quality determines how much of this benefit you actually capture.
Why it matters for optimization
This is the underrated half. Because LinkedIn optimizes toward whatever conversions you feed it, feeding it SQLs and opportunities (not raw form-fills) redirects the algorithm to find more of the people who become qualified pipeline, not more of the people who fill out forms. It is the difference between telling LinkedIn “find me more of these leads” and “find me more of these buyers.” Garbage in, garbage out applies directly: optimize on cheap form-fills and LinkedIn gets better at producing cheap form-fills; optimize on SQLs fed back through CAPI and it gets better at producing SQLs. This is why CAPI is not just an attribution tool, it is one of the highest-leverage optimization changes you can make.
Why it matters for attribution
The other half is closing the loop. Without offline conversions flowing back, LinkedIn undercounts what it produced, so it looks more expensive than it is, and teams underinvest in a channel that is actually working (the attribution gap in reverse). CAPI feeds the offline, later-stage conversions back to LinkedIn so the platform (and your reporting) can connect a February impression to an August closed-won deal. Combined with a CRM as your source of truth and appropriately long conversion windows, it is how you measure LinkedIn on pipeline rather than on the fraction of conversions the pixel caught.
How to set it up
There are two ways to implement CAPI: a partner integration or a direct integration. Most B2B teams use a partner (LinkedIn’s original supported integrations were Dreamdata, Google Tag Manager, and Zapier, with more since), which lets you sync CRM and pipeline data to LinkedIn without heavy engineering. The steps are straightforward: create a conversion rule in Campaign Manager for each conversion type you want to track (with the method set to Conversions API), associate the relevant campaigns to it, and stream the events. Four configuration points decide how much value you get:
- Feed the right conversions. Send your real pipeline stages (SQL, opportunity, closed-won), not just form-fills, so the platform optimizes on outcomes that map to revenue.
- Maximize match quality. Send as many hashed user identifiers as you have (email, and others where available), because only matched events optimize and attribute, and more identifiers means higher match rates.
- Set the right conversion windows. LinkedIn recommends 90-day click and 90-day view for lower-funnel conversions like leads (and 30-day click, 7-day view for website conversions), which fits B2B’s longer cycle.
- Choose the right attribution model and associations. Associate each conversion to as many applicable campaigns as possible, and consider LinkedIn’s Last Touch - Each Campaign model, which credits every campaign that had an ad interaction inside the window. If you run both the Insight Tag and CAPI for the same events, deduplicate so a single conversion is not double-counted.
Get those four right and LinkedIn is working from your actual pipeline data, which is what makes the CPA and attribution gains real rather than theoretical.
If you want CAPI set up to feed your pipeline data into LinkedIn for you, book a demo.
Frequently Asked Questions
Q1. What is the LinkedIn Conversions API?
It is LinkedIn’s server-side conversion tracking (the successor to Offline Conversions), which lets you send conversion data directly from your server or CRM to LinkedIn instead of relying only on the browser pixel. It connects both online and offline data, so LinkedIn can see how your campaigns influenced website form-fills, phone sales, in-person leads, and CRM stage changes like SQL and closed-won. This lets the platform measure performance across the full customer journey and optimize campaigns toward real outcomes rather than a form-fill proxy.
Q2. Why does B2B SaaS need offline conversions in LinkedIn?
Because the conversions that matter (SQLs, opportunities, closed-won deals) happen offline, weeks or months after the click, in your CRM and on sales calls, so LinkedIn never sees them by default. Without them, LinkedIn optimizes and reports on online form-fills, a proxy only loosely tied to revenue, which is how accounts end up producing cheap leads that never become pipeline. Sending offline conversions via CAPI lets LinkedIn optimize toward and attribute the outcomes that actually drive revenue.
Q3. How much does the Conversions API improve results?
LinkedIn has found that Conversions API implementations reduce cost per acquisition by around 20 percent and increase attributed conversions by around 31 percent. The CPA improvement comes from letting the algorithm optimize toward the conversions that matter rather than the ones the pixel happened to see; the attribution lift comes from capturing conversions the pixel missed, both offline conversions and online ones lost to privacy changes. Your actual gain depends on match quality, since only matched events can be used for optimization and attribution.
Q4. How is CAPI different from the LinkedIn Insight Tag?
The Insight Tag is a client-side browser pixel that tracks online actions on your website, and it is increasingly unreliable as cookies are restricted and phased out. The Conversions API is a server-side connection that sends conversion data directly from your server or CRM, so it captures both online and offline conversions and does not depend on cookies. They complement each other, but CAPI is what lets LinkedIn see the offline, later-stage conversions (SQLs, deals) that the pixel can never track, which is what matters for B2B pipeline. If you run both for the same events, deduplicate to avoid double-counting.
Q5. Does the Conversions API help optimization or just reporting?
Both, and the optimization benefit is the underrated half. LinkedIn optimizes toward whatever conversions you feed it, so sending SQLs and opportunities through CAPI redirects the algorithm to find more qualified buyers rather than more form-fillers, which is what drives the roughly 20 percent CPA reduction. On reporting, it captures conversions the pixel missed, lifting attributed conversions by around 31 percent. So CAPI is both an attribution fix and one of the highest-leverage optimization changes available.
Q6. How do you set up the LinkedIn Conversions API?
Use a partner integration (original options included Dreamdata, Google Tag Manager, and Zapier) or a direct integration. Create a conversion rule in Campaign Manager for each conversion type with the method set to Conversions API, associate the relevant campaigns, and stream the events. Then get four things right: feed real pipeline stages (SQL, opportunity, closed-won), send multiple hashed identifiers to lift match rates, set conversion windows to 90-day click and view for lower-funnel events, and associate conversions to as many campaigns as possible using a model like Last Touch - Each Campaign.
Q7. What conversion window and attribution model should you use with CAPI?
LinkedIn recommends a 90-day click and 90-day view window for lower-funnel conversions like leads, and 30-day click, 7-day view for website conversions, since the longer window fits B2B’s months-long cycle. For the model, associate each conversion to as many applicable campaigns as possible and consider Last Touch - Each Campaign, which gives credit to every campaign that had an ad interaction within the window. Pair this with your CRM as the source of truth for revenue attribution, since even the 90-day maximum can miss the tail of a very long cycle.
Q8. Why do only matched conversions count?
Because LinkedIn can only attribute or optimize on a conversion it can tie back to a member who saw or clicked your ad, and that requires matching the conversion’s identifiers (like a hashed email) to a LinkedIn member. Unmatched events cannot be used for attribution or optimization, so match quality directly determines how much value you get from CAPI. That is why the key setup practice is sending as many hashed user identifiers as you have for each conversion, since more identifiers raise the match rate and the share of conversions that actually count.
More Featured Blogs
View All Blogs
Speed to Lead for LinkedIn Ads: Protecting the Pipeline You Paid For
How to Lower Your LinkedIn Ads CPM for B2B SaaS
LinkedIn Ads Audience Overlap and Self-Competition