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

    CONNECTIONS / BigQuery / BigQuery to Meta Conversion Leads

    From BigQuery datasets to Meta Conversion Leads bidding.

    Point Signals at the dataset behind a read-only service account, and it reports lead-stage progress so Meta bids toward qualified pipeline on the cadence your scheduled query already keeps.

    Talk to our team Explore the setup

    bigquery -> meta-capi-crm :: live

    1. ● bigquery → meta.leads :: live
    2. > read crm.lead_stage_history rows=31,317
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 24,740 matched

    WHAT THIS ENABLES

    BigQuery to Meta CAPI for CRM

    BigQuery to Meta CAPI for CRM: A scheduled query reads the qualified-lead and pipeline signals in your BigQuery tables, and Signals reports lead-stage progress so Meta bids toward qualified pipeline, hashed and consent-checked whenever the scheduled query reruns.

    • Signals reports lead-stage progress so Meta bids toward qualified pipeline, reading your BigQuery tables whenever the scheduled query reruns.
    • Meta bidding tuned to the lead stages that become revenue, fed by analytics engineers running BigQuery scheduled queries.

    WHAT FLOWS WHERE

    BigQuery to CAPI for CRM, mapped.

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

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

    WHO THIS IS FOR

    Built for the teams that own the number.

    Meta lead-gen advertisers whose lead quality swings more than volume, with the numbers already modeled in BigQuery tables and GA4 exports.

    Analytics engineers running BigQuery scheduled queries who need Meta bidding tuned to the lead stages that become revenue.

    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 Meta's Conversion Leads API, sized for lead-stage selection.

    2. Map

      A scheduled query reads your BigQuery tables, and its columns map to Meta's Conversion Leads API in the visual mapper, hashed and checked for lead-stage selection.

    3. Deliver

      Whenever the scheduled query reruns, Signals reports lead-stage progress so Meta bids toward qualified pipeline, scans only the rows the query changed, with lead-stage selection watched in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Meta bidding tuned to the lead stages that become revenue on every run, since Signals scans only the rows the query changed.

    Bids weighted to revenue-grade lead stages, delivered whenever the scheduled query reruns without BigQuery slot cost climbing.

    Each run returns a match report on lead-stage selection from Meta's Conversion Leads API, read from your BigQuery tables whenever the scheduled query reruns, at flat BigQuery slot cost.

    ON THE WIRE

    What CAPI for CRM actually receives.

    signals :: bigquery.meta-capi-crm :: wire

    1. ● signals :: event payload
    2. > POST /conversion_leads source=bigquery.crm.lead_stage_history
    3. event_name "Purchase" · value 3297 AED
    4. em sha256 "6f2a91…" · ph sha256 "d40c7e…"
    5. lead_id "lsh_59312" · action_source "system_generated"
    6. ✓ accepted pii=hashed-at-ingestion
    RELATED USE CASES

    Adjacent moves on the same stack.

    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

    from BigQuery

    BigQuery to TikTok CRM

    BigQuery to TikTok CRM Integration: A scheduled query reads the qualified-lead and pipeline…

    Learn more

    same use case

    ActiveCampaign to Meta Conversion Leads

    ActiveCampaign to Meta CAPI for CRM: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta CAPI for CRM

    Datahash ingests lead status from your CRM and sends Meta the qualified events it needs to…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the BigQuery Meta Conversion Leads sync run?

    The scheduled query sets the pace: rebuild the qualified-lead and pipeline signals nightly and delivery to Meta is nightly, or refresh hourly for an hourly feed. Each run only reads the rows the query changed, so Meta bidding tuned to the lead stages that become revenue stays current for lead-stage selection while BigQuery slot cost barely moves.

    What match rate should a BigQuery-sourced Meta Conversion Leads 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 Meta's Conversion Leads API sets a baseline, the number Meta lead-gen advertisers whose lead quality swings more than volume weigh against lead-stage selection.

    NEXT STEP

    BigQuery to Meta Conversion Leads, in production this week.

    Talk to our team All BigQuery use cases