LinkedIn Conversions API

Leads, Qualified, WonMatched by li_fat_id
HubSpot and HighLevelAny CRM by Webhook

The LinkedIn Conversions API sends the results your Insight Tag never sees: the qualified lead, the booked demo, the won deal. DataCops sends them from HubSpot, HighLevel or any CRM to LinkedIn Ads, matched to the member who clicked, with no code.

Setup in 5 minutes
No credit card
One demo request from a LinkedIn ad
From form fill to sales-qualified in HubSpot
With DataCops
Demo requestHeld until qualified
Qualified in HubSpotSent to your ads
Bot demo requestNever sent
Matched to the ad click from the first visit

Trusted by agencies and brands running paid media

AffilinoBigfishClever DigitalKeetraxLegendListingLogicNumeroStormZealdBurst Digital
Definition

What is the LinkedIn Conversions API?

The LinkedIn Conversions API is the server-to-server way to report conversions to LinkedIn Ads. Instead of waiting for the Insight Tag to fire in a browser, your system sends each conversion to LinkedIn directly, with a conversion rule and identifiers such as a hashed email or the li_fat_id from the ad click. That covers LinkedIn offline conversions too: the sales-qualified lead and the closed deal that happen in your CRM weeks after the click.

DataCops keeps the li_fat_id on your own domain when the visitor lands, then sends each stage your CRM reports to LinkedIn through the Conversions API, and to Meta, Google Ads and TikTok in the same step. No developer, no CSV exports.

DataCops sends leads, qualified stages and won deals from HubSpot, HighLevel or any CRM to the LinkedIn Conversions API, matched by li_fat_id and hashed email.

What LinkedIn learns from

B2B on HubSpot
What your ads see today Form Qualified
With DataCops Form Qualified
Agencies and services on HighLevel
What your ads see today Form Booked Showed Won Paid
With DataCops Form Booked Showed Won Paid
Salesforce or any CRM by webhook
What your ads see today Form Any stage you post
With DataCops Form Any stage you post
Why LinkedIn misses the deal

Why LinkedIn Ads optimize for the wrong leads

LinkedIn learns from what it is told. For most B2B accounts that is the form fill, and nothing that happens after it.

Events Meta received
Lead Received
Booked call Never seen
Deal won Never seen
The pixel stops at the form

The Insight Tag stops at the form

The tag sees the page view and the form fill. It never sees the demo, the proposal or the signed contract, and ad blockers stop it from seeing even the form.

Opportunity in your CRM
StageWon
ClosedOn a sales call
Came fromA Meta ad
Meta never hears about it

The deal closes in the CRM

B2B deals are qualified and won in HubSpot, Salesforce or HighLevel, often weeks later. Nothing tells LinkedIn which clicks became pipeline.

The ad click, in the browser
Day 1Ad click saved
Day 8Safari clears the cookie
Day 23Deal won
No click left to match

The click is gone when the deal closes

Safari clears cookies set by a browser script after 7 days. A deal that closes a month later has no ad click left to match.

Leads sent to your ads
Real lead Counted
Bot lead Counted
Real lead Counted
Your ads now look for more bots

Fake leads teach the algorithm

Bot and junk form fills count as conversions too, and each one tells LinkedIn to find more people like it.

How DataCops sends LinkedIn offline conversions

Four steps from the ad click to the won deal, with nothing to build against the LinkedIn Conversions API.

  1. Step 01
    Saved on yourdomain.com
    fbclid from Meta Kept
    gclid from Google Ads Kept
    ttclid from TikTok Kept
    Kept for up to 90 days

    A member clicks your LinkedIn ad. DataCops keeps the li_fat_id on your own domain for up to 90 days.

  2. Step 02
    Stages your CRM reports
    Booked call Reported
    Showed up Reported
    Won, with value Reported

    The lead qualifies, books, shows up or buys, and your CRM reports it.

  3. Step 03
    Finding the ad click again
    Won dealby email or phone
    Ad click, 23 days earlierMatched

    DataCops finds the original click by email and attaches the li_fat_id and hashed email.

  4. Step 04
    Won deal sent
    Meta Sent once
    Google Ads Sent once
    TikTok Sent once
    LinkedIn Sent once

    The stage goes to its LinkedIn conversion rule, and to Meta, Google Ads and TikTok if connected.

Each stage goes out as your CRM reports it: HighLevel stages right away, HubSpot within 5 minutes.

Andrew Forsyth

“15 minutes to get server-side tracking live. After 3 days failing with another app and a DIY server-side Google Tag Manager, that alone sold me. Then support jumped on a Google Meet with me on a Sunday afternoon to finish the job. Nothing else comes close.”

Andrew Forsyth
Chief Executive Officer, Zeald
Conversion rules

Which LinkedIn conversion rule each stage lands on

LinkedIn counts a conversion against a conversion rule in Campaign Manager. Every event DataCops sends through the LinkedIn Conversions API names one, so your campaigns can optimize for it.

  • Rules created when you connect

    DataCops creates a DataCops Lead and a DataCops Purchase conversion rule in your ad account, so leads and sales have a place to land from day one.

  • Sales carry their value

    A won deal or paid invoice goes out with its amount and currency, so LinkedIn can report return on ad spend, not just a count.

  • Other stages use the first rule

    Booked and showed have no DataCops rule of their own yet. They go to the first conversion rule in your ad account, so check which one that is.

Stage to conversion rule
Form lead Lead DataCops Lead
Signup CompleteRegistration DataCops Lead
Won deal, with value Purchase DataCops Purchase
Paid invoice Purchase DataCops Purchase
Booked Schedule First rule in the account
Showed Showed First rule in the account
Matching

How LinkedIn matches a conversion to the member

LinkedIn can only credit an ad if it can tell which member converted. DataCops sends every identifier it has for the lead, so a deal that closes weeks later still finds its way back to the campaign.

  • The li_fat_id from the ad click

    When LinkedIn adds li_fat_id to your landing page link, DataCops keeps it on your own domain with the lead for up to 90 days and sends it back with every later stage.

  • The hashed work email

    The email is lowercased and hashed with SHA-256 before it leaves DataCops. LinkedIn matches it to the member who owns it.

  • Name, company and title

    When your CRM or form passes first and last name, company, job title and country, they go with the event to help LinkedIn find the member.

  • Nothing to match, nothing sent

    An event with no email, no li_fat_id and no name is skipped, and the delivery log says why.

Ad click landing page
yoursite.com/demo?li_fat_id=4c1e...
Sent with the won deal Delivered
LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID li_fat_id from the click
SHA256_EMAIL 9f86d0...a08e
firstName, lastName jane, cole
companyName, title Acme, Head of Ops
countryCode GB

Everything behind each LinkedIn conversion

Capture Background

One first-party script, served from your own domain

  • Runs first-party from datacops.yourdomain, not a blockable third-party host
  • One script, one CNAME, live in about 5 minutes, no container to host
  • Server-side collection on Cloudflare's edge, close to every visitor
  • Captures click IDs at the network level, so fbclid and gclid still reach your CAPI feed after browsers strip them
  • Recovers 15 to 25% of the sessions other setups lose

Traffic Visibility

10%
20%
30%
40%
50%
60%
70%
80%
90%
100%

First-Party Script

~78%

Blockers and ITP cut your sessions

Where the deal comes from

LinkedIn offline conversions from your CRM

Connect the place where your deals move. DataCops listens for the stages you pick and sends each one to LinkedIn.

HighLevel

Install once for your agency and pick the sub-accounts to connect. Each stage is sent as HighLevel reports it. Cancellations, no-shows and lost deals are never sent, and you can switch any stage off.

Sends Form leadBookedShowedWon, with valuePaid invoice
Offline conversions for agencies

Salesforce, Pipedrive and any other CRM

Post the sale to your private DataCops webhook with the customer's email or phone, the value and the order ID. Your CRM can send it directly, or through Zapier, Make or n8n.

Sends Any stage you postValue and currencyOrder ID

Google Sheets and CSV

On a paid plan, upload up to 20,000 past customers or sales from a CSV and pick the platforms to send them to. Rows go out with the date you send them, so use it to warm up an ad account. For sales you add to a sheet every day, send each row through Zapier or Make to your webhook.

Sends LeadPurchaseSchedule
See Ads Warmup
Real people only

Filter fake leads before you send

A bot that fills in your form becomes a lead your ads try to find more of. DataCops checks every visit for bots and datacenter traffic, and for VPNs and proxies if you choose. Switch on Real people only for a platform and flagged visits never reach it.

Sales that come from your CRM are sent as your CRM reports them, with no bot check, so qualify them there before you send.

How DataCops spots bots
Meta, delivery
Real people only
Bots and datacenter traffic never reach Meta. VPNs and proxies too, if you choose.
Send everything
Meta gets every visitor, bots included.
Lead from a bot Skipped
Delivery log
every event, every platform, with a reason
Live
Won deal to LinkedIn
li_fat_id + hashed email
Delivered
Qualified to LinkedIn
waiting for the HubSpot stage
Held
Lead to LinkedIn
no email or li_fat_id
Skipped
Lead to LinkedIn
bot, Real people only is on
Skipped
Won deal to Google Ads
gclid, as a purchase
Delivered
Delivery log

Why LinkedIn offline conversions fail to show up

A LinkedIn upload can report success and still count nothing. DataCops logs every send, per platform, with its status and the reason.

  1. 1
    The conversion is too old
    LinkedIn drops conversions older than 90 days. DataCops sends each stage when it happens, while it is still in range.
  2. 2
    Nothing to match on
    No hashed email, no li_fat_id and no name means LinkedIn cannot find the member. DataCops attaches every identifier it kept.
  3. 3
    The wrong conversion rule
    An event sent to a rule your campaign does not optimize for counts nowhere useful. DataCops creates its own Lead and Purchase rules.
  4. 4
    Nobody saw it fail
    Each send shows as sent, held, skipped or failed, with the reason next to it.

DataCops vs a CSV upload, HubSpot and Zapier

Four ways to get LinkedIn offline conversions into Campaign Manager. Checked September 2026 against each tool's own help pages.

DataCops
LinkedIn CSV upload
HubSpot built-in
Zapier
Sends each stage as it happens
As your CRM reports it
Manual upload
Lifecycle stages
Once you build the Zap
Sends the same stage to Meta, Google Ads and TikTok
Every platform you connect
Meta and Google too
A Zap per platform
Works with any CRM
HighLevel, HubSpot, any CRM by webhook
Any CRM export
HubSpot only
Apps Zapier connects
Checks leads for bots before sending
Real people only, per platform
What it takes
One install, about 5 minutes per site
A CSV each time, rows under 90 days
Marketing Hub Starter or higher
A paid plan, one task per send
Good to know

Good to know before you start

Better to know now than after you connect LinkedIn.

DataCops creates its own rules

Leads and sales go to the DataCops Lead and Purchase rules. Booked and showed go to the first rule in your ad account.

LinkedIn matches on email, not phone

LinkedIn's API does not take phone numbers. Leads need an email, li_fat_id or name.

HubSpot sends the stage you pick

The lifecycle stage you choose as qualified goes to LinkedIn.

Stripe and Paddle payments come later

Checkout purchases, Shopify orders and won stages from your CRM are sent today.

Set up the LinkedIn Conversions API

About 5 minutes per site. Agencies: about 15 minutes per client.

  1. Step 1
    code

    Add the DataCops script
    One script and one DNS record, so every li_fat_id and ad click is kept on your own domain.

  2. Step 2
    ads_click

    Connect LinkedIn
    Sign in and pick the ad account. DataCops creates its Lead and Purchase conversion rules.

  3. Step 3
    hub

    Connect where your deals happen
    HubSpot, HighLevel, your webhook or a CSV. Pick the stages to send.

In short

The LinkedIn Conversions API with DataCops, in short

DataCops is a tool that sends leads, qualified stages and won deals from HubSpot, HighLevel or any CRM to the LinkedIn Conversions API, matched by li_fat_id and hashed email, with every send logged.

How DataCops does it

1

Keep li_fat_id for you

DataCops reads li_fat_id from the landing URL on your own domain and keeps it on the server for up to 90 days, so your CRM never has to store it. A signed server-set cookie on your domain lasts up to 400 days where enabled. With your DNS on Cloudflare, the free Worker reads it at the edge before the page loads.

2

Match by li_fat_id and hashed email

Conversions go to LinkedIn with the SHA-256 email and li_fat_id, plus first and last name, job title, company name and country where known, and value and currency when the value is above zero. LinkedIn is not matched by phone. With no identifier, the event is skipped and logged.

3

Send the stages after the form

HubSpot through one lifecycle stage, HighLevel natively (form lead, booked, showed, won with value, paid), any CRM by private webhook. Lead, Signup and Complete registration go to the DataCops Lead rule, Purchase to the DataCops Purchase rule, and any other event to the first rule in your conversion rules.

4

Counted once

LinkedIn counts an event sent by both the Insight Tag and the Conversions API once. DataCops sends the same event ID from the pixel and the server, and a purchase with an order ID reaches LinkedIn once.

5

Keep bots and fake leads out

Every visit gets a bot verdict against 360+ billion IPs and 350+ monitoring points, with a Real people only switch per platform, off by default. CRM events carry no bot flags. Every form email is checked for disposable providers, domains with no mail server and an email risk score, and LeadCops can hold a lead.

6

See every send

A delivery log row for every conversion: sent, held, skipped or failed, with the reason. LinkedIn delivery was verified live in September 2026.

Best for: B2B advertisers on LinkedIn whose leads qualify and close in HubSpot, HighLevel or another CRM, and agencies running LinkedIn for B2B clients.

Free to start. See pricing.

When not to use DataCops

You need a stage-mapping screen

DataCops has no per-stage mapping screen for LinkedIn. Other events go to the first rule in your conversion rules.

You need phone matching on LinkedIn

LinkedIn conversions are matched by li_fat_id and email, not phone.

HubSpot's built-in LinkedIn events cover you

HubSpot sends lifecycle stages to LinkedIn, Meta and Google on Marketing Hub Starter or higher. If one stage to one platform is enough, that may do.

Conversions older than 90 days

LinkedIn accepts conversions up to 90 days old, so a deal that closes later cannot be credited beyond that.

Sources

Platform rules checked October 2026. Rules change; check the platform's own page before you build.

FAQ

The LinkedIn Conversions API lets a business send conversions to LinkedIn from its own server instead of the browser. Each event names a conversion rule in Campaign Manager and carries identifiers such as a hashed email or the li_fat_id from the ad click, so LinkedIn can credit the campaign even when the Insight Tag was blocked or the sale closed in a CRM.

Let LinkedIn learn from real pipeline

Send qualified leads and won deals from your CRM to the LinkedIn Conversions API, logged per send.

Setup in 5 minutes. No credit card.

Live traffic quality

Updated just now

Visits · last 24h

487
Real users
35873.5%
Bots · auto-filtered
12926.5%

Without filtering, 26.5% of your reported traffic is bot noise inflating dashboards and draining ad spend.

Don't trust your analytics!

Make confident, data-driven decisions withactionable ad spend insights.

Setup in 2 minutes
No credit card