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

    CONNECTIONS / Cockroach / Cockroach to Snap Offline CAPI

    From Cockroach tables to Snapchat in-store conversions.

    Connect Cockroach and point Signals at your Cockroach tables; it reports in-store purchases against the Snapchat campaigns that reached the buyer each time the read runs, hashed and consent-checked for Snapchat.

    Talk to our team Explore the setup

    cockroach -> snap-offline-capi :: live

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

    WHAT THIS ENABLES

    Cockroach to Snapchat Offline CAPI

    Snapchat Offline CAPI for Cockroach: Signals reports in-store purchases against the Snapchat campaigns that reached the buyer straight from your Cockroach tables, hashed and consent-screened each time the read runs.

    • Offline and in-store sales from your Cockroach tables 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 Cockroach tables by platform teams running CockroachDB.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Snap credits the campaign that sourced the conversion conversion happens off-platform Ad click on Snap Scheduled read sync recorded in Cockroach 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 Cockroach tables and secondary indexes.

    Platform teams running CockroachDB activating Snapchat in-store conversions straight from Cockroach tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the Cockroach tables you name to feed Snapchat's Conversions API, sized for offline event timing.

    2. Map

      A scheduled read pulls your Cockroach tables, 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 Cockroach tables, reports in-store purchases against the Snapchat campaigns that reached the buyer, and reads only the records changed since the last run, 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 Cockroach records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: cockroach.snap-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /v2/conversion source=cockroach.closed_deals
    3. event_type "PURCHASE" · event_conversion_type "OFFLINE"
    4. hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
    5. timestamp 1784585811 · price 41214 · currency SAR
    6. ✓ accepted · match=true
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Cockroach

    Cockroach to Google OCI

    Google Offline Conversions for Cockroach: Signals reconciles closed-won revenue to the…

    Learn more

    from Cockroach

    Cockroach to Google Store Sales

    Google Store Sales for Cockroach: Signals matches in-person transactions to Google accounts…

    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 Cockroach Snap Offline CAPI sync run?

    The pace follows your Cockroach tables: Signals sends changes from Cockroach to Snapchat each time the read runs. Because it reads only the records changed since the last run, physical-world sales counted inside Snapchat performance stays current while platform teams running CockroachDB keep offline event timing in view. Delivery needs no export and no manual upload.

    What match rate should a Cockroach-sourced Snap Offline CAPI batch expect?

    Coverage of hashed identifiers across your Cockroach tables decides it, and platform teams running CockroachDB own that inside Cockroach. A live email or phone matches into Snapchat; neither, and it will not. First-run feedback flags offline event timing, which platform teams running CockroachDB then raise inside your Cockroach tables.

    NEXT STEP

    Cockroach to Snap Offline CAPI, in production this week.

    Talk to our team All Cockroach use cases