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

    CONNECTIONS / Clickhouse / ClickHouse to Snap Offline CAPI

    From ClickHouse tables to Snapchat in-store conversions.

    Signals reads your ClickHouse tables through a read-only database user scoped to the ClickHouse tables you name, then reports in-store purchases against the Snapchat campaigns that reached the buyer so Snapchat sees offline conversions without an export.

    Talk to our team Explore the setup

    clickhouse -> snap-offline-capi :: live

    1. ● clickhouse → snap.capi :: live
    2. > read closed_deals rows=51,528
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 40,192 matched

    WHAT THIS ENABLES

    ClickHouse to Snapchat Offline CAPI

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

    • Signals reports in-store purchases against the Snapchat campaigns that reached the buyer, reading your ClickHouse tables each time the read runs.
    • In-person conversions Snapchat can bid on, with no export step out of your ClickHouse tables.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Snap credits the campaign that sourced the conversion conversion happens off-platform Ad click on Snap Scheduled read sync recorded in Clickhouse 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, working out of ClickHouse tables and materialized views.

    Analytics engineers on ClickHouse who need physical-world sales counted inside Snapchat performance out of ClickHouse tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the ClickHouse tables you name, mapped to Snapchat's Conversions API and tuned for offline event timing.

    2. Map

      Columns from your ClickHouse tables align to Snapchat's Conversions API in the visual mapper, hashed as the read runs and checked for offline event timing.

    3. Deliver

      Each time the read runs, Signals reads your ClickHouse tables and reports in-store purchases against the Snapchat campaigns that reached the buyer, reads only the records changed since the last run, with offline event timing watched 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 Clickhouse records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Clickhouse

    ClickHouse to Google OCI

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

    Learn more

    from Clickhouse

    ClickHouse to Google Store Sales

    Google Store Sales for ClickHouse: Signals matches in-person transactions to 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 ClickHouse Snap Offline CAPI sync run?

    The pace follows your ClickHouse tables: Signals sends changes from ClickHouse 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 analytics engineers on ClickHouse keep offline event timing in view. Delivery needs no export and no manual upload.

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

    In ClickHouse, match rate tracks the email and phone quality your ClickHouse tables carry. Clean identifiers land for Snapchat; blank ones never will. The first Conversions API report shows analytics engineers on ClickHouse where offline event timing needs work, a data-quality task handled in ClickHouse.

    NEXT STEP

    ClickHouse to Snap Offline CAPI, in production this week.

    Talk to our team All Clickhouse use cases