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

    CONNECTIONS / Wasabi / Wasabi to LinkedIn Offline CAPI

    Wasabi objects into LinkedIn, built for LinkedIn account-revenue reporting.

    Connect Wasabi and point Signals at your Wasabi objects; it reports closed B2B deals so LinkedIn optimizes on account revenue each time a new file lands, hashed and consent-checked for LinkedIn.

    Talk to our team Explore the setup

    wasabi -> linkedin-offline-capi :: live

    1. ● wasabi → linkedin.capi :: live
    2. > read closed_deals rows=45,352
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 38,549 matched

    WHAT THIS ENABLES

    Wasabi to LinkedIn Offline CAPI

    Wasabi to LinkedIn Offline CAPI: your Wasabi objects, hashed and consent-checked, feed LinkedIn as Signals reports closed B2B deals so LinkedIn optimizes on account revenue each time a new file lands.

    • Offline and in-store sales from your Wasabi objects activated for LinkedIn, as Signals reports closed B2B deals so LinkedIn optimizes on account revenue.
    • Pipeline revenue tied to the LinkedIn campaigns that sourced it, drawn from your Wasabi objects by teams archiving to Wasabi.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn File drop sync recorded in Wasabi 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, with the records already in Wasabi hot-storage buckets and objects.

    Teams archiving to Wasabi activating LinkedIn account-revenue reporting straight from Wasabi objects.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only key scoped to the Wasabi bucket you name to feed LinkedIn's Conversions API, sized for long B2B attribution windows.

    2. Map

      Signals picks up your Wasabi objects, and its columns map to LinkedIn's Conversions API in the visual mapper, hashed and checked for long B2B attribution windows.

    3. Deliver

      On each run, Signals pulls your Wasabi objects, reports closed B2B deals so LinkedIn optimizes on account revenue, and processes only the newly dropped file, with long B2B attribution windows 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 Wasabi records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: wasabi.linkedin-offline-capi :: wire

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

    Adjacent moves on the same stack.

    from Wasabi

    Wasabi to Google OCI

    Wasabi to Google Offline Conversions: your Wasabi objects, hashed and consent-checked, feed…

    Learn more

    from Wasabi

    Wasabi to Google Store Sales

    Wasabi to Google Store Sales: your Wasabi objects, hashed and consent-checked, feed Google…

    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.

    How often does the Wasabi LinkedIn Offline CAPI sync run?

    Delivery tracks Wasabi, run by teams archiving to Wasabi: a near-real-time or scheduled sync of your Wasabi objects feeds LinkedIn on that cadence. Each run processes only the newly dropped file, so account revenue attached to the sourcing campaign holds up on long B2B attribution windows. The live debugger confirms every delivery inline.

    What match rate should a Wasabi-sourced LinkedIn Offline CAPI batch expect?

    Match rate follows identifier coverage in your Wasabi objects, which teams archiving to Wasabi control, not Wasabi itself. A record with a current hashed email or phone matches for LinkedIn; one missing both cannot. First-run feedback from Conversions API pinpoints long B2B attribution windows, the number teams archiving to Wasabi tune against.

    NEXT STEP

    Wasabi to LinkedIn Offline CAPI, in production this week.

    Talk to our team All Wasabi use cases