LinkedIn Offline CAPI
LinkedIn Offline CAPI, pipeline to Ads Manager.
Datahash routes offline outcomes, like closed deals from your CRM, to LinkedIn with hashed identifiers and event dedupe.
- ● linkedin.offline_capi :: live
- > batch crm_closed_deals rows=1,240
- hash sha256(em) pii=cleared
- match business email 62%
- ✓ uploaded · offline conversions accepted
Built for the teams that own the number.
Teams already sending CRM stages to other ad platforms.
From kickoff to verified events.
-
Source
Ingest offline events from your CRM, warehouse, or file drop.
-
Match
Hashed business email prepared per LinkedIn's matching spec.
-
Deliver
Offline outcomes routed to LinkedIn, deduped and monitored.
WHAT FLOWS WHERE
One use case, every source.
A deal closes in your CRM, Signals hashes the business email on a scheduled batch and matches it, then routes the offline outcome to LinkedIn's Conversions API.
A deal closes in your CRM, Signals hashes the business email on a scheduled batch and matches it, then routes the offline outcome to LinkedIn's Conversions API.
What ships with this offering.
Offline outcomes inside LinkedIn campaign optimization.
Hashed, privacy-safe identifier handling end to end.
The same offline pipeline you already run for other channels.
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 :: offline payload
- > POST /rest/conversionEvents
- conversion "urn:lla:llaPartnerConversion:41880" · eventId "crm-41880"
- user idType=SHA256_EMAIL idValue "a2c9…" · li_fat_id "ACXk…"
- conversionHappenedAt 1789002233000 · amount 15000 · USD
- ✓ 201 created · accepted
Adjacent moves on the same stack.
LinkedIn CAPI
Datahash implements LinkedIn CAPI with hashed identifiers, deduplication, and CRM-driven lead stage delivery for B2B campaigns.
Learn morecross-channel
Lead funnel events
Datahash syncs lead-quality signal from your CRM back to Meta, Google, TikTok, and LinkedIn so campaigns optimize on the leads that actually convert.
Learn more
meta
Meta Offline CAPI
Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to Meta with hashed identifiers, event dedupe, and closed-loop match reporting.
Learn more
x
X Offline CAPI
Datahash routes offline transactions from your POS, CRM, or warehouse to X with hashed identifiers and event dedupe.
Learn moreBring 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.
What offline events can be sent to LinkedIn?
Any conversion your CRM records, most commonly closed deals and pipeline stages such as SQL or Closed Won, mapped to LinkedIn's event taxonomy during setup. Warehouse exports and file drops are supported the same way, so teams whose pipeline data lives outside a single CRM system are not left out. Once mapped, an event type stays mapped without further engineering work.
How do you match offline sales back to LinkedIn ads?
Through hashed business email and the click identifier LinkedIn attaches to ad traffic when a prospect clicks through from an ad. Raw PII never leaves your environment unhashed, since hashing happens before any identifier is sent to LinkedIn. This mirrors the same matching approach used for LinkedIn CAPI, so B2B teams already sending CRM stages elsewhere can extend the same pipeline to offline outcomes.
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.