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

    CONNECTIONS / Wasabi / Wasabi to Snap Offline CAPI

    Wasabi objects into Snapchat, built for Snapchat in-store conversions.

    Connect Wasabi and point Signals at your Wasabi objects; it reports in-store purchases against the Snapchat campaigns that reached the buyer each time a new file lands, hashed and consent-checked for Snapchat.

    Talk to our team Explore the setup

    wasabi -> snap-offline-capi :: live

    1. ● wasabi → snap.capi :: live
    2. > read closed_deals rows=65,887
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 52,051 matched

    WHAT THIS ENABLES

    Wasabi to Snapchat Offline CAPI

    Wasabi to Snapchat Offline CAPI: your Wasabi objects, hashed and consent-checked, feed Snapchat as Signals reports in-store purchases against the Snapchat campaigns that reached the buyer each time a new file lands.

    • Offline and in-store sales from your Wasabi objects activated for Snapchat, as Signals reports in-store purchases against the Snapchat campaigns that reached the buyer.
    • Physical-world sales counted inside Snapchat performance, drawn from your Wasabi objects by teams archiving to Wasabi.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Snap credits the campaign that sourced the conversion conversion happens off-platform Ad click on Snap 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.

    Retail and QSR advertisers whose Snapchat audience buys in person, with the records already in Wasabi hot-storage buckets and objects.

    Teams archiving to Wasabi activating Snapchat in-store conversions 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 Snapchat's Conversions API, sized for offline event timing.

    2. Map

      Signals picks up your Wasabi objects, and its columns map to Snapchat's Conversions API in the visual mapper, hashed and checked for offline event timing.

    3. Deliver

      On each run, Signals pulls your Wasabi objects, reports in-store purchases against the Snapchat campaigns that reached the buyer, and processes only the newly dropped file, with offline event timing 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.snap-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /v2/conversion source=wasabi.closed_deals
    3. event_type "PURCHASE" · event_conversion_type "OFFLINE"
    4. hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
    5. timestamp 1784161325 · price 44453 · currency USD
    6. ✓ accepted · match=true
    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 Snap Offline CAPI

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

    Learn more

    generic

    Snap Offline CAPI

    Deliver offline conversions to Snap on a schedule that fits your operations.

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Wasabi Snap 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 Snapchat on that cadence. Each run processes only the newly dropped file, so in-person conversions Snapchat can bid on holds up on offline event timing. The live debugger confirms every delivery inline.

    What match rate should a Wasabi-sourced Snap 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 Snapchat; one missing both cannot. First-run feedback from Conversions API pinpoints offline event timing, the number teams archiving to Wasabi tune against.

    NEXT STEP

    Wasabi to Snap Offline CAPI, in production this week.

    Talk to our team All Wasabi use cases