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

    CONNECTIONS / BigQuery / BigQuery to Snap Leads CAPI

    From BigQuery datasets to Snapchat qualified-lead reporting.

    Point Signals at the dataset behind a read-only service account, and it sends qualified-lead events so Snapchat bids toward leads that convert offline on the cadence your scheduled query already keeps.

    Talk to our team Explore the setup

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

    1. ● bigquery → snap.capi :: live
    2. > read crm.lead_stage_history rows=22,354
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 19,895 matched

    WHAT THIS ENABLES

    BigQuery to Snapchat Leads CAPI

    BigQuery to Snapchat Leads CAPI: A scheduled query reads the qualified-lead and pipeline signals in your BigQuery tables, and Signals sends qualified-lead events so Snapchat bids toward leads that convert offline, hashed and consent-checked whenever the scheduled query reruns.

    • Signals sends qualified-lead events so Snapchat bids toward leads that convert offline, reading your BigQuery tables whenever the scheduled query reruns.
    • Snapchat optimizing on qualified leads instead of raw submissions, fed by analytics engineers running BigQuery scheduled queries.

    WHAT FLOWS WHERE

    BigQuery to Lead Gen CAPI, mapped.

    A scheduled query hands the qualified-lead and pipeline signals to Signals, which hashes and consent-filters each row before Snapchat's Leads Conversions API logs the lead conversions for qualified-lead signals.

    A scheduled query hands the qualified-lead and pipeline signals to Signals, which hashes and consent-filters each row before 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, with the numbers already modeled in BigQuery tables and GA4 exports.

    Analytics engineers running BigQuery scheduled queries who need Snapchat optimizing on qualified leads instead of raw submissions.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only service account with dataViewer on the one dataset you nominate to feed Snapchat's Leads Conversions API, sized for qualified-lead signals.

    2. Map

      A scheduled query reads your BigQuery tables, and its columns map to Snapchat's Leads Conversions API in the visual mapper, hashed and checked for qualified-lead signals.

    3. Deliver

      Whenever the scheduled query reruns, Signals sends qualified-lead events so Snapchat bids toward leads that convert offline, scans only the rows the query changed, 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 on every run, since Signals scans only the rows the query changed.

    Spend steered toward leads that qualify, delivered whenever the scheduled query reruns without BigQuery slot cost climbing.

    Each run returns a match report on qualified-lead signals from Snapchat's Leads Conversions API, read from your BigQuery tables whenever the scheduled query reruns, at flat BigQuery slot cost.

    ON THE WIRE

    What Lead Gen CAPI actually receives.

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

    1. ● signals :: event payload
    2. > POST /v2/conversion source=bigquery.crm.lead_stage_history
    3. event_type "QUALIFIED_LEAD" · event_conversion_type "OFFLINE"
    4. hashed_email "4ac910…" · hashed_phone_number "7e30bc…"
    5. timestamp 1784192030
    6. ✓ accepted · match=true
    RELATED USE CASES

    Adjacent moves on the same stack.

    from BigQuery

    BigQuery to Meta Conversion Leads

    BigQuery to Meta CAPI for CRM: A scheduled query reads the qualified-lead and pipeline…

    Learn more

    from BigQuery

    BigQuery to Google EC for Leads

    BigQuery to Google EC for Leads: A scheduled query reads the qualified-lead and pipeline…

    Learn more

    same use case

    ActiveCampaign to Snap Leads CAPI

    ActiveCampaign to Snapchat Leads CAPI: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Snap Lead Gen CAPI

    Route qualified lead stages from your CRM back to Snap via server-side CAPI so campaigns…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the BigQuery Snap Leads CAPI sync run?

    The scheduled query sets the pace: rebuild the qualified-lead and pipeline signals nightly and delivery to Snapchat is nightly, or refresh hourly for an hourly feed. Each run only reads the rows the query changed, so Snapchat optimizing on qualified leads instead of raw submissions stays current for qualified-lead signals while BigQuery slot cost barely moves.

    What match rate should a BigQuery-sourced Snap Leads CAPI batch expect?

    Coverage in your BigQuery tables decides the rate, not BigQuery. A row with a current hashed email or phone matches; one missing both cannot, however the query is tuned. The first run's report from Snapchat's Leads Conversions API sets a baseline, the number Snapchat lead-gen advertisers qualifying leads after the form weigh against qualified-lead signals.

    NEXT STEP

    BigQuery to Snap Leads CAPI, in production this week.

    Talk to our team All BigQuery use cases