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

    CONNECTIONS / Wasabi / Wasabi to Meta Offline CAPI

    Wasabi objects into Meta, built for Meta's offline optimization.

    Connect Wasabi and point Signals at your Wasabi objects; it credits dealer, branch, and phone sales to the Meta campaigns behind them each time a new file lands, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    wasabi -> meta-offline-capi :: live

    1. ● wasabi → meta.capi :: live
    2. > read closed_deals rows=42,079
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 37,030 matched

    WHAT THIS ENABLES

    Wasabi to Meta Offline CAPI

    Wasabi to Meta Offline CAPI: your Wasabi objects, hashed and consent-checked, feed Meta as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them each time a new file lands.

    • Offline and in-store sales from your Wasabi objects activated for Meta, as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them.
    • In-store and phone revenue joining Meta's optimization loop, drawn from your Wasabi objects by teams archiving to Wasabi.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta File drop sync recorded in Wasabi S Signals hash · dedupe Offline Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Considered-purchase brands closing revenue far from the browser, with the records already in Wasabi hot-storage buckets and objects.

    Teams archiving to Wasabi activating Meta's offline optimization 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 Meta's Offline Conversions API, sized for Meta's 62-day event window.

    2. Map

      Signals picks up your Wasabi objects, and its columns map to Meta's Offline Conversions API in the visual mapper, hashed and checked for Meta's 62-day event window.

    3. Deliver

      On each run, Signals pulls your Wasabi objects, credits dealer, branch, and phone sales to the Meta campaigns behind them, and processes only the newly dropped file, with Meta's 62-day event window 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.meta-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=wasabi.closed_deals
    3. event_name "Purchase" · event_time 2026-07-13T06:41:14
    4. value 34609.00 · currency GBP
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-87874"
    6. ✓ accepted match=88%
    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 Meta Offline CAPI

    ActiveCampaign to Meta Offline CAPI: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Offline CAPI

    Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Wasabi Meta 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 Meta on that cadence. Each run processes only the newly dropped file, so campaign learning fed by real-world purchases holds up on Meta's 62-day event window. The live debugger confirms every delivery inline.

    What match rate should a Wasabi-sourced Meta 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 Meta; one missing both cannot. First-run feedback from Offline Conversions API pinpoints Meta's 62-day event window, the number teams archiving to Wasabi tune against.

    NEXT STEP

    Wasabi to Meta Offline CAPI, in production this week.

    Talk to our team All Wasabi use cases