LinkedIn tracking that reports pipeline, not form fills
LinkedIn's value is almost never the form fill — it's the pipeline that form fill becomes sixty to a hundred and twenty days later. That means the click ID has to survive into your CRM and the outcome has to come back, or the channel gets judged on cost per lead and switched off. Judging LinkedIn on form fills is how good B2B accounts get killed.
Free30 minutesNo obligation
LinkedIn CAPI · what breaks
Why LinkedIn gets cancelled unfairly
- 01
Cost per lead looks terrible against other channels
It usually is higher per lead and better per closed deal.
- 02
No li_fat_id on CRM records
So no closed deal can ever be tied back to a LinkedIn click.
- 03
Only form fills sent back
Bidding optimises toward whoever fills forms most readily.
- 04
Attribution window shorter than the sales cycle
Deals discarded before they close.
LinkedIn CAPI · the fix
What you get out of it — LinkedIn CAPI
Pipeline visible per campaign
Which is the only fair basis for judging the channel.
Bidding optimising on qualified stages
Rather than raw submissions.
Closed-won revenue in Campaign Manager
Where budget decisions actually get made.
Windows matched to your real cycle
So long deals aren't discarded.
LinkedIn CAPI · architecture
Why the numbers were wrong before you got here — LinkedIn CAPI
Worth understanding before buying anything, because it decides which tier you need — and for some readers the answer is that you don't need us yet.
- 1
The browser is the weakest link, and it is getting weaker on purpose
Every browser-side tag has to survive the page loading, the visitor staying, the script running and the request leaving. All four are now contested. The order in your database is certain; the browser event reporting it is not.
- 2
Safari caps the cookie your attribution depends on
Intelligent Tracking Prevention limits JavaScript-set cookies to seven days whatever expiry you set, so a customer who takes longer than a week to decide returns as a stranger. A cookie your own server writes in an HTTP response is not capped — the single largest practical difference between browser-side and first-party server-side.
- 3
Ad blockers remove the tag with no error
A blocked pixel does not warn anyone. The customer buys, the order lands, and no platform hears about it. First-party events from your own subdomain are not a third-party request and are not filtered the same way.
- 4
Consent is enforced by hope, not by architecture
Client-side consent means trusting each vendor script to honour a flag. A server container decides at the container: a denied destination receives nothing. That is a materially stronger position, and it also stops the over-blocking that discards data no law required losing.
- 5
Checkout can end where your tag isn't
Wallets and hosted payment pages can be abandoned after the money moves. Sending the purchase from the order record means it arrives whether or not anyone came back.
LinkedIn CAPI · diagnose
How we scope the linkedin build
Before quoting. Each step narrows what the work actually is, so the price reflects your account rather than an average.
- 01
Confirm li_fat_id is captured and stored
On a real ad click, through to the CRM record.
- 02
Trace one lead end to end
Click, form, CRM, stages, close.
- 03
Check the offline conversion match rate
High upload volume with low match rate is a formatting problem.
- 04
Audit which conversion is the optimisation goal
If it's the form fill, that's the finding.
- 05
Verify the window covers your sales cycle
A 30-day window on a 90-day cycle discards most of your conversions.
LinkedIn CAPI · prove
How the work gets proven — LinkedIn CAPI
A dashboard turning green proves a dashboard turned green. These are what we hand over instead.
Source of truth
Your CRM's opportunity and closed-won records
- li_fat_id present on the large majority of CRM records from LinkedIn traffic.
- Offline uploads running on schedule with a match rate you've actually read.
- Closed-won revenue visible against originating campaigns in Campaign Manager.
- One lead traced end to end from click through to signed contract.
- Conversion window at least the length of your real median cycle.
- Reconciled over a fully closed window, matched on ID rather than on totals — totals hide equal and opposite errors.
- Payload evidence captured from real transactions, saved to your own records.
- The same reconciliation repeated 30 days later, because a setup that works once and drifts is the harder failure.
LinkedIn CAPI · free audit
What we check in the free audit
- Confirm li_fat_id is captured and stored
- Trace one lead end to end
- Check the offline conversion match rate
- Audit which conversion is the optimisation goal
- Verify the window covers your sales cycle
Checked against
Your CRM's opportunity and closed-won records
Free30 minutesNo obligation
LinkedIn CAPI · when not to buy
When you shouldn't buy this — LinkedIn CAPI
We would rather say it now than three weeks into an engagement.
- You sell direct to consumers. LinkedIn's cost structure rarely works and the pipeline plumbing has nothing to carry.
- Your deals close in the same session. A standard conversion tag is sufficient.
- You have no CRM, or one nobody updates. The loop requires genuinely maintained stage data.
- LinkedIn is a small test at low spend. Prove the channel first.
LinkedIn CAPI · what we deliver
What's included in the linkedin build
li_fat_id capture and storage
Onto the CRM record at first touch.
Lead Gen Form integration
Where you use them, since there's no site visit to track.
Stage mapping
MQL, SQL, opportunity and closed-won sent as offline conversions.
Values attached
So bidding can distinguish a large deal from a small one.
Windows aligned
To at least your real median cycle length.
Match rate monitoring
So a formatting failure surfaces rather than accumulating.
Written guarantee
95%+ tracking accuracy
Measured against Your CRM's opportunity and closed-won records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
The correct browser-side build, done properly and verified on a live transaction. Honest about its ceiling: it will not survive Safari's cookie cap, an ad blocker, or a checkout that ends somewhere your tag isn't. If you spend $1K+/month on paid media, start one tier up.
- Correct events, correct parameters, correct values
- Verified on a live transaction, not in preview
- Reconciled against your own order records
- Written handover you keep
1st-party server-side
Recommended$800One-time fee · most popular
The tier that changes the outcome rather than patching it. Your money events stop depending on the browser: they are sent from your order records through a first-party server container on your own subdomain, so iOS, ad blockers, consent banners and interrupted payment redirects can no longer take them away. Built in 2–4 days. You own the stack outright, with no monthly SaaS.
- First-party server container on your own subdomain
- Money events sent from your order records, not the browser
- Meta, Google, TikTok, Microsoft and LinkedIn all fed server-side
- Deduplicated on a shared event ID, verified at every destination
- First-party cookies beyond Safari's 7-day cap on JavaScript-set cookies
- 95%+ conversion accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid-media channel server-side, plus the offline loop that connects closed revenue back to the click. For advertisers whose spend makes an attribution leak more expensive than the build.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop, so closed revenue reaches bidding
- Refunds and cancellations reversed at every destination
- Klaviyo identity stitching, BigQuery and Looker Studio
- Monitoring, so the next break surfaces in days rather than a quarter
FAQ
LinkedIn CAPI questions, answered
It usually is, and that's the wrong metric for it. The channel tends to look expensive per lead and reasonable per closed deal, which is exactly why the outcome loop matters here more than anywhere.
Yes. The form completes inside LinkedIn so there's no site visit, but the lead data can still be mapped to your CRM and the outcome sent back.
Optimise on a stage inside the window and report closed revenue separately. Anything closing beyond 90 days can't be credited to the click.
It improves match rates meaningfully, particularly for offline outcomes. Whether it's worth it depends on your spend and how much of your pipeline comes from LinkedIn.
Free · 30 min
Judge LinkedIn on pipeline, not leads
WhatsAppFree30 minutesNo obligation
