Jump to a popular page, or start typing.

    CONNECTIONS / BigQuery / BigQuery to TikTok CRM

    From BigQuery datasets to TikTok CRM lead optimization.

    Point Signals at the dataset behind a read-only service account, and it reports pipeline-stage changes to TikTok as distinct optimizable events on the cadence your scheduled query already keeps.

    bigquery -> tiktok-crm-integration :: live

    1. ● bigquery → tiktok.crm :: live
    2. > read crm.lead_stage_history rows=10,791
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 9,172 matched

    WHAT THIS ENABLES

    BigQuery to TikTok CRM Integration

    BigQuery to TikTok CRM Integration: A scheduled query reads the qualified-lead and pipeline signals in your BigQuery tables, and Signals reports pipeline-stage changes to TikTok as distinct optimizable events, hashed and consent-checked whenever the scheduled query reruns.

    • Signals reports pipeline-stage changes to TikTok as distinct optimizable events, reading your BigQuery tables whenever the scheduled query reruns.
    • TikTok bidding on the funnel depth your revenue reporting reads, fed by analytics engineers running BigQuery scheduled queries.

    WHAT FLOWS WHERE

    BigQuery to CRM Integration, mapped.

    A scheduled query hands the qualified-lead and pipeline signals to Signals, which hashes and consent-filters each row before TikTok's CRM Events API logs the lead conversions for stage-to-event mapping.

    A scheduled query hands the qualified-lead and pipeline signals to Signals, which hashes and consent-filters each row before TikTok's CRM Events API logs the lead conversions for stage-to-event mapping.

    WHO THIS IS FOR

    Built for the teams that own the number.

    TikTok lead-gen advertisers tracking qualification, not form counts, with the numbers already modeled in BigQuery tables and GA4 exports.

    Analytics engineers running BigQuery scheduled queries who need TikTok bidding on the funnel depth your revenue reporting reads.

    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 TikTok's CRM Events API, sized for stage-to-event mapping.

    2. Map

      A scheduled query reads your BigQuery tables, and its columns map to TikTok's CRM Events API in the visual mapper, hashed and checked for stage-to-event mapping.

    3. Deliver

      Whenever the scheduled query reruns, Signals reports pipeline-stage changes to TikTok as distinct optimizable events, scans only the rows the query changed, with stage-to-event mapping watched in the debugger.

    WHAT YOU GET

    What ships with this use case.

    TikTok bidding on the funnel depth your revenue reporting reads on every run, since Signals scans only the rows the query changed.

    Funnel-depth events TikTok can optimize on, delivered whenever the scheduled query reruns without BigQuery slot cost climbing.

    Each run returns a match report on stage-to-event mapping from TikTok's CRM Events API, read from your BigQuery tables whenever the scheduled query reruns, at flat BigQuery slot cost.

    ON THE WIRE

    What CRM Integration actually receives.

    signals :: bigquery.tiktok-crm-integration :: wire

    1. ● signals :: event payload
    2. > POST /event/track source=bigquery.crm.lead_stage_history
    3. event "Contact" · event_time 1784352496
    4. user.email sha256 "8f21ce…" · user.phone sha256 "019d7a…"
    5. properties.lead_status "Qualified"
    6. ✓ accepted · dedupe=event_id
    FAQ

    Asked on almost every call.

    How often does the BigQuery TikTok CRM sync run?

    The scheduled query sets the pace: rebuild the qualified-lead and pipeline signals nightly and delivery to TikTok is nightly, or refresh hourly for an hourly feed. Each run only reads the rows the query changed, so TikTok bidding on the funnel depth your revenue reporting reads stays current for stage-to-event mapping while BigQuery slot cost barely moves.

    What match rate should a BigQuery-sourced TikTok CRM 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 TikTok's CRM Events API sets a baseline, the number TikTok lead-gen advertisers tracking qualification, not form counts weigh against stage-to-event mapping.

    NEXT STEP

    BigQuery to TikTok CRM, in production this week.