Jump to a popular page, or start typing.
    Talk to our team

    CONNECTIONS / Datahash API / Datahash API to LinkedIn Offline CAPI

    Post offline and in-store sales to the Datahash API, wired to LinkedIn account-revenue reporting.

    Send offline and in-store sales to one documented REST endpoint from any backend, in any language; Signals reports closed B2B deals so LinkedIn optimizes on account revenue, hashed and consent-checked, with no pixel and no warehouse read.

    Talk to our team Explore the setup

    datahash-api -> linkedin-offline-capi :: live

    1. ● datahash-api → linkedin.capi :: live
    2. > POST /v1/events source=api.purchase_events count=51,205
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ 202 accepted · 43,524 forwarded

    WHAT THIS ENABLES

    Datahash API to LinkedIn Offline CAPI

    Datahash API to LinkedIn Offline CAPI: post your offline and in-store sales to one REST endpoint and Signals reports closed B2B deals so LinkedIn optimizes on account revenue, hashed and consent-checked server-side before LinkedIn sees it.

    • Signals reports closed B2B deals so LinkedIn optimizes on account revenue, from events your backend posts server-side.
    • Pipeline revenue tied to the LinkedIn campaigns that sourced it, without a pixel, a connector, or a nightly export.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off LinkedIn, away from any pixel. Here is how Datahash API closes the loop.

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn REST event recorded in Datahash API S Signals hash · dedupe Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    B2B teams whose deals close long after the impression, whose engineers would rather POST an event than maintain a connector.

    Backend and platform teams driving LinkedIn account-revenue reporting by sending offline and in-store sales straight from their own stack.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Create an API key in the Signals console and point your backend at the endpoint that feeds LinkedIn's Conversions API.

    2. Map

      Map your event payload to LinkedIn's Conversions API fields once; per-request validation flags bad events instead of dropping the batch.

    3. Deliver

      Post events as they happen and Signals reports closed B2B deals so LinkedIn optimizes on account revenue, hashing server-side, with long B2B attribution windows shown in the debugger.

    WHAT YOU GET

    What changes when the CSV goes away.

    Capability Manual CSV upload Datahash
    Reporting Offline sales sit in a separate export, reconciled by hand. Revenue counted in the same Offline CAPI reporting as web conversions.
    Deduplication A re-uploaded file risks counting the same conversion twice. Deduped delivery, so a resent record never counts as a second conversion.
    Match visibility Match quality is a guess until the numbers look off. Match rate reported per upload, tied to the source event set that produced it.
    Effort and latency An analyst exports and uploads on a manual cadence. Server-side and automatic the moment Datahash API records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: datahash-api.linkedin-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /conversionEvents source=api.purchase_events
    3. conversion "urn:lla:llaPartnerConversion:84979"
    4. conversionHappenedAt 1784596979000
    5. user.userIds [{ idType: "SHA256_EMAIL", idValue: "9c41af…" }]
    6. ✓ accepted · conversionValue 29710 USD
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Datahash API

    Datahash API to Google OCI

    Datahash API to Google Offline Conversions: post your offline and in-store sales to one…

    Learn more

    from Datahash API

    Datahash API to Google Store Sales

    Datahash API to Google Store Sales: post your offline and in-store sales to one REST…

    Learn more

    same use case

    ActiveCampaign to LinkedIn Offline CAPI

    ActiveCampaign to LinkedIn Offline CAPI: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    LinkedIn Offline CAPI

    Datahash routes offline outcomes, like closed deals from your CRM, to LinkedIn with hashed…

    Learn more
    FAQ

    Asked on almost every call.

    Which backends can send to LinkedIn Offline CAPI through the Datahash API?

    Any backend that can make an HTTPS request. You POST offline and in-store sales as JSON to one documented endpoint and Signals forwards the offline conversions to LinkedIn's Conversions API; identifiers are hashed at ingestion or sent pre-hashed, and B2B teams whose deals close long after the impression track long B2B attribution windows in the debugger.

    How fresh are LinkedIn Offline CAPI events sent over the API?

    As fresh as you post them. The API accepts events in near real time, so pipeline revenue tied to the LinkedIn campaigns that sourced it reaches LinkedIn moments after your backend fires the call, with per-event status returned inline. There is no batch window and no scheduled read, which keeps long B2B attribution windows current for the teams driving LinkedIn account-revenue reporting.

    NEXT STEP

    Datahash API to LinkedIn Offline CAPI, in production this week.

    Talk to our team All Datahash API use cases