LinkedIn Leads Conversions API
LinkedIn Leads Conversions API, past the form fill.
Datahash sends CRM lead events to LinkedIn server-side, so campaigns optimize toward qualified leads and closed revenue rather than raw form fills. Deal-stage changes and closed-won values stream through automatically, with identifiers hashed throughout.
- ● linkedin.leads_capi :: live
- > conversion qualified_lead stage=SQL
- hash sha256(em) source=crm
- map stage → conversion ok
- ✓ delivered · lead conversion accepted
Built for the teams that own the number.
Teams already sending CRM stage changes to other ad platforms from the same source.
From kickoff to verified events.
-
Connect
Connect the LinkedIn ad account with scoped access, then choose the CRM stages that should fire conversion events.
-
Map
Map stages and fields to destination events in the visual mapper.
-
Deliver
Verify sample events in the live debugger, then go live with a delivery status on every event.
WHAT FLOWS WHERE
One use case, every source.
A lead advances a stage in your CRM, Signals hashes the business email and maps the stage, then delivers it to LinkedIn's Leads Conversions API so campaigns optimize on qualified pipeline.
A lead advances a stage in your CRM, Signals hashes the business email and maps the stage, then delivers it to LinkedIn's Leads Conversions API so campaigns optimize on qualified pipeline.
What ships with this offering.
Lead status and deal-stage changes delivered to LinkedIn as conversion events.
Closed-won revenue passed through with values for value-based optimization.
Per-event delivery status and match diagnostics for troubleshooting.
ON THE WIRE
What the platform actually receives.
Identifiers are hashed with SHA-256 at source. The payload the destination sees never contains raw PII.
- ● signals :: conversion payload
- > POST /rest/conversionEvents
- conversion "urn:lla:llaPartnerConversion:77192" · eventId "crm-77192"
- user idType=SHA256_EMAIL idValue "7b2d…"
- conversionHappenedAt 1789002233000 · stage "closed_won" · amount 8400
- ✓ 201 created · accepted
Bring it from where the data lives.
Every source that supports this use case. Pick a platform to see the exact setup.
CRM
Databases
Files / storage
Data warehouses
Datahash API
Custom
Questions your team will ask.
Which CRM stages should feed LinkedIn Leads Conversions API?
Most teams map MQL, SQL, and closed-won as distinct events, so LinkedIn can optimize toward down-funnel outcomes instead of raw form fills. Datahash sets the initial mapping during onboarding, and stage definitions can change later without a new integration project.
How fast do CRM stage changes reach LinkedIn?
Stage changes stream to LinkedIn Leads Conversions API in near real time, arriving without waiting on a scheduled export or nightly batch job. That speed keeps optimization signal close to the moment sales actually qualifies or closes a lead, rather than days later once a report is pulled and reviewed.
Is customer PII stored to run LinkedIn Leads Conversions API?
No. Identifiers are hashed with SHA-256 at ingestion and no PII is stored on host servers in Datahash Cloud. A self-hosted Core deployment is available if lead data cannot leave your own environment, and the same hashing approach applies to every CRM stage sent to LinkedIn.
NEXT STEP
Live in fifteen minutes. Measurable in a week.
Talk to our team of solutions engineers. We map your source data, propose an integration plan, and give you a live setup in the same call where possible.