Jump to a popular page, or start typing.

    CONNECTIONS / Clickhouse / ClickHouse to Snap Leads CAPI

    From ClickHouse tables to Snapchat qualified-lead reporting.

    Signals reads your ClickHouse tables through a read-only database user scoped to the ClickHouse tables you name, then sends qualified-lead events so Snapchat bids toward leads that convert offline so Snapchat sees lead conversions without an export.

    clickhouse -> snap-lead-gen-capi :: live

    1. ● clickhouse → snap.capi :: live
    2. > read lead_pipeline rows=34,972
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 26,928 matched

    WHAT THIS ENABLES

    ClickHouse to Snapchat Leads CAPI

    Snapchat Leads CAPI for ClickHouse: Signals sends qualified-lead events so Snapchat bids toward leads that convert offline straight from your ClickHouse tables, hashed and consent-screened each time the read runs.

    • Signals sends qualified-lead events so Snapchat bids toward leads that convert offline, reading your ClickHouse tables each time the read runs.
    • Spend steered toward leads that qualify, with no export step out of your ClickHouse tables.

    WHAT FLOWS WHERE

    Clickhouse to Lead Gen CAPI, mapped.

    Each sync hands the qualified-lead and pipeline signals from your ClickHouse tables to Signals, which hashes and filters every record, then Snapchat's Leads Conversions API logs the lead conversions for qualified-lead signals.

    Each sync hands the qualified-lead and pipeline signals from your ClickHouse tables to Signals, which hashes and filters every record, then Snapchat's Leads Conversions API logs the lead conversions for qualified-lead signals.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Snapchat lead-gen advertisers qualifying leads after the form, working out of ClickHouse tables and materialized views.

    Analytics engineers on ClickHouse who need Snapchat optimizing on qualified leads instead of raw submissions 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 Leads Conversions API and tuned for qualified-lead signals.

    2. Map

      Columns from your ClickHouse tables align to Snapchat's Leads Conversions API in the visual mapper, hashed as the read runs and checked for qualified-lead signals.

    3. Deliver

      Each time the read runs, Signals reads your ClickHouse tables and sends qualified-lead events so Snapchat bids toward leads that convert offline, reads only the records changed since the last run, with qualified-lead signals watched in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Snapchat optimizing on qualified leads instead of raw submissions from your ClickHouse tables, delivered each time the read runs.

    Spend steered toward leads that qualify out of your ClickHouse tables, delivered each time the read runs without read load on the database climbing.

    Match feedback on qualified-lead signals from Snapchat's Leads Conversions API each run, tied back to your ClickHouse tables.

    ON THE WIRE

    What Lead Gen CAPI actually receives.

    signals :: clickhouse.snap-lead-gen-capi :: wire

    1. ● signals :: event payload
    2. > POST /v2/conversion source=clickhouse.lead_pipeline
    3. event_type "QUALIFIED_LEAD" · event_conversion_type "OFFLINE"
    4. hashed_email "4ac910…" · hashed_phone_number "7e30bc…"
    5. timestamp 1784484140
    6. ✓ accepted · match=true
    FAQ

    Asked on almost every call.

    How often does the ClickHouse Snap Leads 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, Snapchat optimizing on qualified leads instead of raw submissions stays current while analytics engineers on ClickHouse keep qualified-lead signals in view. Delivery needs no export and no manual upload.

    What match rate should a ClickHouse-sourced Snap Leads 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 Leads Conversions API report shows analytics engineers on ClickHouse where qualified-lead signals needs work, a data-quality task handled in ClickHouse.

    NEXT STEP

    ClickHouse to Snap Leads CAPI, in production this week.