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

    CONNECTIONS / BigQuery / BigQuery to OpenAI Offline CAPI

    From BigQuery datasets to OpenAI's Offline Conversions API.

    Point Signals at the dataset behind a read-only service account, and it reports downstream revenue as OpenAI's conversion measurement comes online on the cadence your scheduled query already keeps.

    Talk to our team Explore the setup

    bigquery -> openai-offline-capi :: live

    1. ● bigquery → openai.capi :: live
    2. > read sales.pos_transactions rows=10,403
    3. hash sha256(email,phone) consent=filtered
    4. route openai deliver
    5. ✓ delivered · 8,947 matched

    WHAT THIS ENABLES

    BigQuery to OpenAI Offline CAPI

    BigQuery to OpenAI Offline CAPI: A scheduled query reads the offline and in-store sales in your BigQuery tables, and Signals reports downstream revenue as OpenAI's conversion measurement comes online, hashed and consent-checked whenever the scheduled query reruns.

    • Signals reports downstream revenue as OpenAI's conversion measurement comes online, reading your BigQuery tables whenever the scheduled query reruns.
    • A revenue feed ready the moment OpenAI's offline measurement expands, fed by analytics engineers running BigQuery scheduled queries.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    OpenAI credits the campaign that sourced the conversion conversion happens off-platform Ad click on OpenAI Scheduled query sync recorded in BigQuery S Signals hash · dedupe Offline Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Early advertisers on OpenAI inventory measuring revenue from day one, with the numbers already modeled in BigQuery tables and GA4 exports.

    Analytics engineers running BigQuery scheduled queries who need a revenue feed ready the moment OpenAI's offline measurement expands.

    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 OpenAI's Offline Conversions API, sized for the emerging OpenAI ad surface.

    2. Map

      A scheduled query reads your BigQuery tables, and its columns map to OpenAI's Offline Conversions API in the visual mapper, hashed and checked for the emerging OpenAI ad surface.

    3. Deliver

      Whenever the scheduled query reruns, Signals reports downstream revenue as OpenAI's conversion measurement comes online, scans only the rows the query changed, with the emerging OpenAI ad surface 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 BigQuery records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: bigquery.openai-offline-capi :: wire

    1. â—Ź signals :: event payload
    2. > POST /offline_conversions source=bigquery.sales.pos_transactions
    3. event_name "Purchase" · event_time 1784370288
    4. em sha256 "2b9d64…" · value 39174 · currency AED
    5. ✓ accepted · row_status delivered
    RELATED USE CASES

    Adjacent moves on the same stack.

    from BigQuery

    BigQuery to Google OCI

    BigQuery to Google Offline Conversions: A scheduled query reads the offline and in-store…

    Learn more

    from BigQuery

    BigQuery to Google Store Sales

    BigQuery to Google Store Sales: A scheduled query reads the offline and in-store sales in…

    Learn more

    same use case

    ActiveCampaign to OpenAI Offline CAPI

    ActiveCampaign to OpenAI Offline CAPI: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    OpenAI Offline Conversions API

    Datahash uploads offline and in-store conversions to OpenAI with hashed identifiers, so…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the BigQuery OpenAI Offline CAPI sync run?

    The scheduled query sets the pace: rebuild the offline and in-store sales nightly and delivery to OpenAI is nightly, or refresh hourly for an hourly feed. Each run only reads the rows the query changed, so a revenue feed ready the moment OpenAI's offline measurement expands stays current for the emerging OpenAI ad surface while BigQuery slot cost barely moves.

    What match rate should a BigQuery-sourced OpenAI Offline 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 OpenAI's Offline Conversions API sets a baseline, the number early advertisers on OpenAI inventory measuring revenue from day one weigh against the emerging OpenAI ad surface.

    NEXT STEP

    BigQuery to OpenAI Offline CAPI, in production this week.

    Talk to our team All BigQuery use cases