Integrations
LinkedIn Conversions API
Send LinkedIn conversions from the server, so your B2B leads arrive even when the browser blocks the Insight Tag. Every event is assembled from the whole DataCops platform, not a bare tag, so LinkedIn receives the click ID plus a verified work email, counted once. One-click connect, no code.
What it is
The LinkedIn Conversions API is the server-to-server way to report LinkedIn conversions, instead of relying on the LinkedIn Insight Tag in the browser. DataCops connects it for you in one click, with no code, and sends each conversion from the server with the click ID and the hashed email LinkedIn needs to match it to the member who saw or clicked your ad.Server-side sending is only half of it. A B2B conversion is only as good as the match data attached to it. What makes DataCops different is where that data comes from: every part of the platform, first-party capture, the edge worker, the 400-day identity, IP intelligence, and email verification, feeds one clean LinkedIn event. LinkedIn is not receiving a tag firing. It is receiving the full, verified record of a real lead.
Why the Insight Tag loses leads
The LinkedIn Insight Tag runs in the browser, which is exactly where tracking is weakest, and it fails in three ways at once:
- It gets blocked. Ad blockers strip it, Safari and iOS limit it, and consent rejection removes it. The lead never reaches LinkedIn, and B2B traffic is especially heavy with ad blockers.
- It arrives thin. When the tag does fire, it often carries just a cookie. LinkedIn cannot confidently tie a cookie to a real member, so the lead goes unmatched and your cost per lead looks worse than it is.
- It counts fakes. A raw tag fires for anything, including bots and form-fill fraud, so LinkedIn learns from fake leads and spends your budget finding more.
Every one of these is a data problem, and that is what DataCops fixes before LinkedIn ever sees the event.
How DataCops builds each event
A DataCops LinkedIn event is not captured in one place. It is assembled. As a visitor moves through your site, each part of the platform adds what it knows, so that by the time a lead converts, the event is already complete, verified, and ready to match.Here is what each part adds to that middle step, in order:
- First-party capture keeps the ad click alive. The LinkedIn click ID (li_fat_id) is captured on your own domain, so ad blockers and Safari cannot strip it the way they strip a third-party tag.
- The edge worker recovers what the browser drops. If the click ID would have been lost, it is caught server-side at the edge, so the strongest match signal survives even when the browser fails.
- The 400-day durable identity attaches the real person. If someone fills a form anonymously today but identified themselves earlier, DataCops finds that stored profile and attaches their work email, name, and company, so a lead that would have gone out with nothing to match on goes out with a verified identity behind it. B2B sales cycles are long, and this is where a 400-day memory matters most.
- IP intelligence supplies a clean IP and location. The same IP checked for fraud is the one sent to LinkedIn, so location and device signals are real, not a datacentre or VPN address.
- Email verification makes the match key trustworthy. The work email is confirmed to be a real, deliverable address before it becomes a hashed match key, so you are not matching LinkedIn against a fake or throwaway inbox, the most common form of B2B lead fraud.
- The fraud verdict gates out the fakes. Bots and form-fill fraud are stopped here. By default only verified, human leads are sent, so LinkedIn never learns from noise.
- The consent gate decides if it is allowed. Where consent is required, the event is only sent if consent is in place, resolved server-side, so you stay compliant without dropping the leads you are allowed to keep.
Only after all of that does the event become a LinkedIn conversion, fully built and ready to match.
The match signals sent to LinkedIn
LinkedIn matches a conversion to a member using match signals, and for B2B the verified work email is the strongest one there is. A browser tag usually manages only a cookie. DataCops assembles the full set, every customer detail normalised and securely hashed on the server before it leaves, so LinkedIn can match on it without ever receiving a raw email.
| Signal | What it does for matching | Where DataCops gets it |
|---|---|---|
| li_fat_id | The LinkedIn click ID. The single strongest link between a lead and the ad that drove it. | First-party capture, recovered at the edge if the browser drops it |
| Email (hashed) | Matches the lead to their LinkedIn member profile, the strongest B2B match key there is. | Verified real, then normalised and hashed on the server |
| First and last name (hashed) | Extra keys that lift the match when the email alone does not resolve. | Stored profile from the 400-day durable identity |
| Company and title | B2B context that helps LinkedIn confirm the member and value the lead. | Stored profile from the 400-day durable identity |
| External ID (hashed) | Your own stable ID for the person, so LinkedIn can join repeat events to one lead. | 400-day durable identity |
| IP address | A match and location signal LinkedIn expects on a server event. | IP intelligence, the same clean IP used for the fraud verdict |
| User agent | Pairs with the IP so LinkedIn can resolve the device. | First-party capture |
Alongside the person, each event carries the conversion itself: the conversion mapped to your LinkedIn conversion rule, the real time it happened, and the lead value where you track one. Nothing is fabricated, and no raw personal detail is ever sent, only the securely hashed version LinkedIn asks for.
Counted once, never twice
Every DataCops event carries one steady ID, and that same ID is the one LinkedIn uses to spot a repeat on its side. So if you keep your existing Insight Tag running next to DataCops, LinkedIn sees the tag event and the server event share an ID and keeps only one. Your numbers do not double.
This is what lets you switch on server-side delivery without ripping anything out. Run both, confirm the server leads are landing and matching better, and retire the tag whenever you are ready. DataCops also catches a repeat of the same lead before it goes out, so a form that submits twice still only reports once.
Connect in one click
This is the whole setup. No code, no container, no developer, no access tokens to paste.
Connect your LinkedIn account
Log in to LinkedIn once from DataCops. That is the only permission step.
Pick your conversion
Choose the LinkedIn conversion rule you want leads sent to.
Map your events
In Event Manager, map each conversion to that rule, one time.
From then on, every clean lead is built, matched, and delivered to LinkedIn automatically. There is nothing to maintain, and no tag that can silently break.
Higher match rate
LinkedIn attributes and values more of your leads the more strong signals you send, and for B2B the verified work email is the one that matters most. Because a DataCops event arrives with the click ID plus a verified, hashed work email, and not just a cookie, LinkedIn can match far more of your leads to a real member. That does three things for your ads:
- It recovers volume. The leads ad blockers and Safari used to hide now reach LinkedIn, so it optimises on your whole audience, not a fraction, and B2B traffic loses the most to blockers.
- It sharpens matching. A verified work email connects far more leads to a real member than a cookie ever could, so your cost per lead and optimisation both improve.
- It cleans the signal. Only verified, consented, human leads go out, so the algorithm learns from real buyers and finds more of them, instead of chasing the form-fill fraud a raw tag counted.
More leads, better matched, all real. That is why a verified server-side conversion outperforms a browser tag firing into the void.
An honest delivery log
A browser tag fires and forgets. It never learns whether LinkedIn accepted the lead or dropped it, so a conversion path can be broken for weeks while your tag still shows as installed. DataCops records every send: one record per event, marked sent, skipped, or failed, with LinkedIn's own reason shown, like an expired click or a connection that needs reauthorising. If a send fails for a temporary reason, it is retried. So you can see, per lead, exactly what reached LinkedIn and why, instead of trusting that a tag is still working.