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

    CONNECTIONS / GCS / GCS to OpenAI Offline CAPI

    Your GCS objects, wired to OpenAI's Offline Conversions API.

    Connect GCS and point Signals at your GCS objects; it reports downstream revenue as OpenAI's conversion measurement comes online each time a new file lands, hashed and consent-checked for OpenAI.

    Talk to our team Explore the setup

    google-cloud-storage -> openai-offline-capi :: live

    1. ● gcs → openai.capi :: live
    2. > read closed_deals rows=57,191
    3. hash sha256(email,phone) consent=filtered
    4. route openai deliver
    5. ✓ delivered · 47,469 matched

    WHAT THIS ENABLES

    GCS to OpenAI Offline CAPI

    GCS to OpenAI Offline CAPI: your GCS objects, hashed and consent-checked, feed OpenAI as Signals reports downstream revenue as OpenAI's conversion measurement comes online each time a new file lands.

    • Offline and in-store sales from your GCS objects activated for OpenAI, as Signals reports downstream revenue as OpenAI's conversion measurement comes online.
    • A revenue feed ready the moment OpenAI's offline measurement expands, drawn from your GCS objects by data teams landing exports in GCS.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    OpenAI credits the campaign that sourced the conversion conversion happens off-platform Ad click on OpenAI G File drop sync recorded in GCS 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 records already in Google Cloud Storage buckets and objects.

    Data teams landing exports in GCS activating OpenAI's Offline Conversions API straight from GCS objects.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only service account scoped to the one GCS bucket you name to feed OpenAI's Offline Conversions API, sized for the emerging OpenAI ad surface.

    2. Map

      Signals picks up your GCS objects, 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

      On each run, Signals pulls your GCS objects, reports downstream revenue as OpenAI's conversion measurement comes online, and processes only the newly dropped file, with the emerging OpenAI ad surface 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 GCS records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: google-cloud-storage.openai-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=google-cloud-storage.closed_deals
    3. event_name "Purchase" · event_time 1784211585
    4. em sha256 "2b9d64…" · value 30536 · currency USD
    5. ✓ accepted · row_status delivered
    RELATED USE CASES

    Adjacent moves on the same stack.

    from GCS

    GCS to Google OCI

    GCS to Google Offline Conversions: your GCS objects, hashed and consent-checked, feed…

    Learn more

    from GCS

    GCS to Google Store Sales

    GCS to Google Store Sales: your GCS objects, hashed and consent-checked, feed Google Ads as…

    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 GCS OpenAI Offline CAPI sync run?

    The pace follows your GCS objects: Signals sends changes from GCS to OpenAI each time a new file lands. Because it processes only the newly dropped file, a revenue feed ready the moment OpenAI's offline measurement expands stays current while data teams landing exports in GCS keep the emerging OpenAI ad surface in view. Delivery needs no export and no manual upload.

    What match rate should a GCS-sourced OpenAI Offline CAPI batch expect?

    Coverage of hashed identifiers across your GCS objects decides it, and data teams landing exports in GCS own that inside GCS. A live email or phone matches into OpenAI; neither, and it will not. First-run feedback flags the emerging OpenAI ad surface, which data teams landing exports in GCS then raise inside your GCS objects.

    NEXT STEP

    GCS to OpenAI Offline CAPI, in production this week.

    Talk to our team All GCS use cases