LinkedIn Ads
How to Set Up the LinkedIn Conversions API With Your CRM
Create a LinkedIn conversion rule for each CRM stage, connect it through a partner like Zapier or a direct API build, and stream hashed CRM events with matching identifiers. Validate match rate in Campaign Manager before trusting the numbers, since LinkedIn's counts will always vary somewhat from your CRM's.
Key takeaways
- The Conversions API sends offline CRM events like MQL, opportunity and closed-won to LinkedIn; it's meant to run alongside the Insight Tag, not replace it.
- Direct API builds authenticate with a non-expiring access token generated in Campaign Manager's Signals Manager; you only need a developer app if you're building as a Marketing Partner.
- Salesforce isn't on LinkedIn's Conversions API or offline conversions partner lists, and HubSpot sits only on the legacy offline conversions list, so most CRM teams bridge through Zapier or build directly.
- Each CRM funnel stage needs its own conversion rule, with closed-won typically sent as a PURCHASE type carrying the real deal value for ROAS reporting.
- Match rate, attribution windows, multi-campaign attribution and GMT reporting all create a normal, persistent gap between LinkedIn's conversion count and your CRM's.
The LinkedIn Conversions API is a server-to-server connection that sends conversion events, like marketing qualified leads, opportunities and closed-won deals, from your CRM straight to LinkedIn Campaign Manager. You need it the moment a conversion happens somewhere other than your website, because the LinkedIn Insight Tag can only see browser-side activity.
What the Conversions API does that the Insight Tag can't
The LinkedIn Insight Tag is a piece of lightweight JavaScript code that you can add to your website, and it works by creating a cookie on a visitor's browser. With Conversions API, you can connect both your online and offline data to LinkedIn so you can see how your campaigns influenced actions taken on your website, sales completed over the phone, or leads collected in-person at an event. That covers the parts of a B2B funnel that never touch your website again: sales accepting a lead, a deal moving to an opportunity, a deal closing.
Run both together, not one instead of the other. Microsoft's Conversions FAQ says to strengthen your existing conversion tracking, you can use the Conversions API and the Insight Tag together to measure and optimize both online and offline events across your customer journey, or when you need a secure way to connect data to LinkedIn without relying on cookie-based tracking. The tag catches the top of the funnel; the API catches what happens in the CRM afterward.
What you need before you start
Four things have to be in place before you stream a single event:
- An access token, not necessarily a developer app. If you're building a Direct API integration yourself, advertisers who want to send their conversion data directly to LinkedIn, without integrating through supported partner platforms, can generate access tokens for authentication from their Campaign Manager ad account, and don't need to create a developer application or apply for the Conversions API through the developer portal. You generate it under Data, then Signals Manager, then Direct API, and the token doesn't expire. A developer app and Company Page Verification are only required if you're building as a Marketing Partner through the Developer Portal.
- Ad account permissions. The account user authorizing the connection needs the
rw_conversionsandr_adsscopes, and must hold the Account Billing Admin, Account Manager, Campaign Manager or Creative Manager role on the ad account, per LinkedIn's Conversions API documentation. - A conversion rule for each CRM stage you want to track, each with its own name, conversion type and attribution settings, built in Campaign Manager or via the
POST /conversionsendpoint. - Matching identifiers and consent. You need at least one hashed or plaintext identifier per event, and a legal basis to share that data. Email addresses are hashed using SHA256, and LinkedIn's Data Processing Agreement covers Conversions API, but hashing isn't a substitute for consent. Treat it the same as any other server-side data share with an ad platform.
Partner integration vs a custom build: which one fits Salesforce or HubSpot
LinkedIn gives you two implementation paths, and the choice comes down to developer time. Per the Conversions FAQ, you can leverage a partner integration or build a direct integration with developer resources.
| Option | How it works | Effort | Best for |
|---|---|---|---|
| Partner integration | Route events through a LinkedIn Marketing Partner such as Google Tag Manager, Zapier, Dreamdata, Supermetrics or Tealium (Adobe was listed as in testing) | One-time setup, little engineering | Teams without a developer to spare, or who already use one of these tools for other reporting |
| Direct API build | Your developers call the /conversions and /conversionEvents endpoints directly from your server or CRM middleware | Developer resources required; implementation takes 1-2 weeks on average per LinkedIn's FAQ | Teams who want control over field mapping, custom CRM objects, or who already pipe CRM data through an internal event bus |
Salesforce doesn't appear on LinkedIn's Conversions API partner list or its separate offline conversions partner list, so Salesforce teams typically bridge through Zapier or write a direct integration. HubSpot isn't on the core Conversions API partner list either, but it is one of LinkedIn's offline conversions partners, alongside Adverity, LeadsBridge, LiveRamp and Make. LinkedIn is winding that channel down, though: offline conversions at LinkedIn are being updated, and LinkedIn recommends choosing a Conversions API partner to help ensure you won't have a disruption in features. For new setups, that means most HubSpot and Salesforce teams land on Zapier or a direct build rather than the legacy offline partner path.
Step-by-step: connect a CRM stage to a LinkedIn conversion rule
The setup sequence is the same regardless of which CRM you run, because the conversion rule and the data source are separate steps in Campaign Manager.
- Create the conversion rule. In Campaign Manager, go to Analyze, then Conversion tracking, click Create Conversion and select Conversions API or CSV conversion, then choose Direct API or a partner as your source, per LinkedIn's Direct API setup guide.
- Set the conversion type and attribution window. Pick a type that matches the CRM stage, such as
LEAD,QUALIFIED_LEAD,MARKETING_QUALIFIED_LEADorPURCHASEfor closed-won. The default lookback is a 30-day post-click and 7-day view-through window, both adjustable up to 90 days, or 180 and 365 days for a limited set of types, according to LinkedIn's Conversions API schema documentation. - Associate the campaigns you want credited. Auto-associate up to 200 active, paused or draft campaigns with
autoAssociationType=ALL_CAMPAIGNS, or match campaigns to the rule's type withOBJECTIVE_BASED, which has no 200-campaign cap, per the same schema documentation. - Wire up the CRM trigger. In Zapier, build a Zap that fires on the stage change (new MQL, moved to Opportunity, marked Closed Won) and maps the lead's email and name into the fields the partner exposes. Building direct, have developers call the CRM's API to detect the stage change and stream it to LinkedIn's endpoint using the access token from Signals Manager.
- Send matching identifiers with every event. At minimum, send a SHA256-hashed email. LinkedIn's FAQ lists the accepted identifiers as SHA256_EMAIL, LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID, PLAINTEXT_IP_ADDRESS, SHA256_IP_ADDRESS, GOOGLE_AID, ACXIOM_ID, firstName, lastName, companyName, title, countryCode, lead, and externalIds, and recommends sending both the hashed email and LinkedIn's first-party click ID for the best match rate.
- Hash correctly. The Conversions API supports hashed emails and hashed IP addresses using SHA-256 without salting, and LinkedIn recommends converting emails to lowercase before hashing for better match rates. A raw mixed-case email hashed without lowercasing first will silently fail to match.
Clean UTMs matter here too. If your conversion rule depends on knowing which campaign a lead came from, that starts with consistent UTM parameters on every ad, not just the API payload; see our guide to UTM parameters for B2B paid campaigns for naming conventions that keep CRM source fields usable.
Sending opportunity and closed-won as conversion events
LinkedIn doesn't have a conversion type literally called "opportunity" or "closed-won." You build it with multiple conversion rules, one per CRM stage, each pointed at the same campaigns. Microsoft's use case documentation is explicit: create multiple conversion rules to attribute the impact of ad campaigns on your different sales stages in CRM that represent both pipeline and closed won deals.
A typical setup is three or four rules against the same campaigns:
- A
LEADorMARKETING_QUALIFIED_LEADrule firing when the record is created or marked MQL.MARKETING_QUALIFIED_LEADandSALES_QUALIFIED_LEADbecame available starting with the 202608 API version, per LinkedIn's schema documentation, so confirm your integration is on that version or later. - A
QUALIFIED_LEADor custom-named rule firing when the deal becomes an opportunity, with no dollar value yet. - A
PURCHASErule firing on Closed Won, withconversionValueset to the deal's actual amount so LinkedIn reports total conversion value and you can calculate ROAS.
LinkedIn's guidance is direct: for upper-funnel rules, divide spend by conversions for cost per influenced conversion; for lower funnel pipeline objectives and closed won deals, conversion value can be passed dynamically through CRM which can help you to calculate ROAS as total conversion value divided by spend. That's the point of piping CRM stages into the API instead of stopping at form-fill tracking.
How to validate the integration before you trust the numbers
Don't make budget decisions off this data the day you turn it on. Check three things first:
- Confirm events are arriving. In Campaign Manager, open the rule's status. You can check the conversions status in Campaign Manager to validate that the conversion events were received and user identities were matched with LinkedIn profiles. Data can take up to 72 hours to fully appear, since it takes up to 24 hours to complete ingestion and an additional 48 hours for reporting.
- Check match rate, not just volume. If you see Low Match Rate below Active on your conversion rule, this means that the information streamed to LinkedIn has a low likelihood of successful event-to-profile matching. Events received but Low Match Rate usually means missing or badly hashed identifiers, not a tracking failure.
- Spot-check a known deal. Pick a closed-won account from the last week, confirm it shows up in the Conversions & Leads view with the right value, and trace it back to the CRM record. If it's missing, check whether the stage actually fired the event, and whether that lead had an identifier attached at the time.
Why LinkedIn's conversion count will never exactly match your CRM
Even a clean setup won't tie out to your CRM report. This is expected, not a sign something's broken; LinkedIn's own documentation explains several structural reasons:
Expect a persistent gap between the two systems. Pick one as your source of truth for pipeline reporting, usually the CRM, and use LinkedIn's number as a directional signal for optimization. Our breakdown of B2B attribution tools for paid media covers how teams reconcile CRM pipeline against ad platform data at scale. A CRM-first approach also helps before reconciliation even becomes necessary: Tofu Ads Agent reads closed-won and closed-lost deals, pipeline and deal size directly from Salesforce or HubSpot to build audiences, then writes dynamic UTMs back to the CRM so the source data feeding your Conversions API events is consistent from the start.
Common mistakes that break the integration
- One conversion rule for the whole funnel. Without a separate rule per stage, you can't calculate cost per influenced conversion separately from closed-won ROAS.
- Forgetting to lowercase emails before hashing. The hash is case-sensitive, so an unhashed case mismatch silently tanks match rate.
- Not associating new campaigns with the rule. A rule with no auto-association won't attribute events to campaigns launched after it was created.
- Treating Low Match Rate as a bug. It almost always means the event payload is missing identifiers, not that the pipe is broken.
Once validated, the API runs in the background. The harder ongoing work is making sure budgets and bids respond to what the CRM is telling you, the weekly loop Tofu Ads Agent's bid optimization agent for LinkedIn is built to handle using that same CRM-sourced signal.
Frequently asked questions
Do I still need the LinkedIn Insight Tag if I set up the Conversions API?
Yes. LinkedIn recommends using the Conversions API and the Insight Tag together rather than one instead of the other, since the tag covers on-site browser behavior and the API covers offline CRM events. Running both and setting up deduplication gives you the most complete picture of the customer journey.
Can I connect Salesforce or HubSpot directly to the LinkedIn Conversions API?
Not through a native, LinkedIn-built connector. Salesforce doesn't appear on LinkedIn's Conversions API or offline conversions partner lists, and HubSpot sits only on the legacy offline conversions partner list, which LinkedIn is winding down in favor of Conversions API partners. Most teams bridge the gap with Zapier or build a direct API integration that reads the CRM's own API.
How long does it take for Conversions API data to show up in Campaign Manager?
LinkedIn's documentation says ingestion takes up to 24 hours and reporting takes up to another 48 hours, so full data can take up to 72 hours to appear. Don't judge a new integration's accuracy before that window has passed.
What does a Low Match Rate warning on a conversion rule mean?
It means the identifiers you're sending, like hashed emails or click IDs, aren't matching LinkedIn member profiles reliably. It almost always points to a data problem, such as unhashed or incorrectly cased emails, not a broken connection.
How do I send closed-won deals with a dollar value to LinkedIn?
Create a separate conversion rule, typically typed as PURCHASE, and set the conversionValue field to the deal's actual amount when the CRM marks it Closed Won. LinkedIn then reports total conversion value so you can calculate return on ad spend.
Why will LinkedIn's reported conversions never exactly match my CRM?
LinkedIn can only attribute conversions it successfully matches to a LinkedIn member, and matched events still need an ad click or view inside the conversion rule's attribution window, which maxes out around 180 days for most types. Add in GMT-based reporting and the fact that one conversion can be credited to several campaigns at once, and some variance from your CRM's single count is normal.
Should I build the Conversions API integration myself or use a partner?
Use a partner like Zapier if you don't have developer time to spare; it's a one-time setup with limited engineering work. Build directly if you need control over custom CRM fields or objects; LinkedIn estimates direct builds take 1-2 weeks of developer time on average, and you can authenticate with an access token generated in Campaign Manager without building a developer app.
Sources
- Set up and create a conversion in Campaign Manager using Direct API · LinkedIn Help
- LinkedIn Conversions API · LinkedIn Help
- Set up a Conversions API integration in Campaign Manager · LinkedIn Help
- LinkedIn Insight Tag · LinkedIn Help
- Offline conversions partners · LinkedIn Help
- Compare Campaign Manager Conversions with Third-Party Reporting · LinkedIn Help
- Third-party reporting doesn't match Campaign Manager · LinkedIn Help
- Conversions FAQ · Microsoft Learn
- Conversions API · Microsoft Learn
- Conversions API Schema · Microsoft Learn
- Conversions API Use Cases · Microsoft Learn
- Getting Access to Conversions API · Microsoft Learn


