In our Meta CRM feedback loop guide we explained how much difference it makes to feed CRM outcomes back into the ad platform with Meta's Conversions API. For B2B companies, the natural next step is to bring the same logic to LinkedIn.
Because in B2B the problem is even bigger. The real conversion does not happen the day a form is filled in, but perhaps three months later when a proposal is signed. Browser-based tracking struggles to see a journey that long.
Why the Insight Tag Is Not Enough
The LinkedIn Insight Tag is a JavaScript tag added to your site. It needs two conditions to work: the browser must not block it, and the cookie must still be there when the conversion happens.
In B2B both conditions are weak. Corporate networks and ad blockers frequently block the tag. More importantly, the truly valuable event (a qualified opportunity, a signed contract) happens in the CRM, not on the site. A tag in the browser has no way of seeing it.
The result: your LinkedIn campaigns optimize for "form submitted". Yet most people who fill in the form never become customers.
What the Conversions API Does
The LinkedIn Conversions API is a server-to-server connection through which you send conversion events to LinkedIn from your own server rather than the browser. Where the conversion happens stops mattering: when an opportunity changes stage in the CRM, that information can be passed to LinkedIn.
That enables two things:
- Accurate measurement: seeing which campaign actually brought leads that turned into sales.
- Accurate optimization: letting LinkedIn's algorithm look for audiences that resemble buyers, not form fillers.
Mapping CRM Stages to LinkedIn Events
The most critical setup decision is commercial, not technical: which CRM stage maps to which conversion type? The LinkedIn API offers conversion types that fit the B2B funnel. A typical mapping might look like this:
| CRM stage | LinkedIn conversion type | Note |
|---|---|---|
| Form submitted | LEAD | High volume, weak signal |
| Marketing qualified lead | MARKETING_QUALIFIED_LEAD | API version 202608 and later |
| Sales qualified lead | SALES_QUALIFIED_LEAD | API version 202608 and later |
| Closed-won opportunity | PURCHASE | Should be sent with a value |
There is an important balance here. A closed-won deal is the strongest signal, but there are so few of them that they may not be enough for the algorithm to learn from. That is why the qualified lead stage is usually chosen as the optimization goal, while sales are sent for measurement.
How It Works Technically
The flow has three steps: create the conversion rule, associate campaigns with it, and send events. Sending an event is a simple JSON request:
{
"conversion": "urn:lla:llaPartnerConversion:123",
"conversionHappenedAt": 1789459200000,
"conversionValue": { "currencyCode": "USD", "amount": "12000" },
"user": {
"userIds": [
{ "idType": "SHA256_EMAIL", "idValue": "e3b0c442..." },
{ "idType": "LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID", "idValue": "df5gf5-..." }
]
},
"eventId": "crm-deal-48213-won"
}Points to watch:
User identifiers
An event is only useful to the extent LinkedIn can match it to a member; unmatched events are used for neither measurement nor optimization. You can send a hashed (SHA256) email, LinkedIn's first-party tracking ID, an IP address, or first and last name with company details. Sending several identifiers improves the match rate. So capturing the LinkedIn tracking ID at form submission and storing it in the CRM should be the first task of the setup.
Time limit
The event time must be within the last 90 days. Older events are rejected. In long sales cycles this means stage changes must be sent as they happen, not batched up later.
Attribution window
For lead and qualified lead types, the post-click attribution window can be set to 180 or 365 days. For the long B2B cycle, that is far more realistic than short default windows.
Duplicate events
If you send the same event through both the Insight Tag and the API, use the same eventId on both sides. Otherwise conversions may be counted twice.
Limits
A single batch request can carry up to 5,000 events; there is a limit of 600 requests per minute and 500,000 per day per access token. These limits rarely cause trouble at typical B2B volumes, but a bulk historical upload needs batching.
Common Setup Mistakes
- Hashing email without normalizing it: a hash taken before trimming spaces and lowercasing will not match.
- Sending only the "form" event: the API gets set up but only sends what the browser tag already sees; the CRM stages, the real gain, are missing.
- Forgetting to associate campaigns with the rule: only associated campaigns can receive conversion attribution.
- Not tracking the API version: LinkedIn marketing APIs are versioned and old versions are sunset on set dates. For example, version 202510 sunsets on 15 October 2026.
Conclusion
The root of the measurement problem in B2B marketing is that valuable events happen in the CRM, not in the browser. The LinkedIn Conversions API closes that gap: the ad platform can now learn from real customers instead of form fillers.
The technical part of the setup is a few days of work. The real effort goes into defining CRM stages correctly and capturing identifiers properly from the start of the data flow. We build this feedback loop between ad platforms and the CRM end to end under our RevOps service.
