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

    CONNECTIONS / GCS / GCS to Google OCI

    Your GCS objects, wired to Google Ads offline conversion import.

    Connect GCS and point Signals at your GCS objects; it reconciles closed-won revenue to the Google Ads click through GCLID each time a new file lands, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    google-cloud-storage -> google-oci :: live

    1. ● gcs → google.oci :: live
    2. > read closed_deals rows=59,313
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 46,264 matched

    WHAT THIS ENABLES

    GCS to Google Offline Conversions

    GCS to Google Offline Conversions: your GCS objects, hashed and consent-checked, feed Google Ads as Signals reconciles closed-won revenue to the Google Ads click through GCLID each time a new file lands.

    • Offline and in-store sales from your GCS objects activated for Google Ads, as Signals reconciles closed-won revenue to the Google Ads click through GCLID.
    • Smart Bidding trained on booked revenue instead of a mid-funnel proxy, 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 Google, away from any pixel. Here is how GCS closes the loop.

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google G File drop sync recorded in GCS S Signals hash · dedupe Offline Conversion Impo… delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Advertisers whose Google-sourced deals close days after the click, with the records already in Google Cloud Storage buckets and objects.

    Data teams landing exports in GCS activating Google Ads offline conversion import 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 Google Ads' Offline Conversion Import (Google Ads API), sized for GCLID coverage.

    2. Map

      Signals picks up your GCS objects, and its columns map to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed and checked for GCLID coverage.

    3. Deliver

      On each run, Signals pulls your GCS objects, reconciles closed-won revenue to the Google Ads click through GCLID, and processes only the newly dropped file, with GCLID coverage 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 OCI 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 OCI actually receives.

    signals :: google-cloud-storage.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=google-cloud-storage.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-16T21:50:52"
    5. conversion_value 18919 · currency_code AED
    6. ✓ accepted · batch=nightly
    RELATED USE CASES

    Adjacent moves on the same stack.

    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

    from GCS

    GCS to Meta Offline CAPI

    GCS to Meta Offline CAPI: your GCS objects, hashed and consent-checked, feed Meta as…

    Learn more

    same use case

    ActiveCampaign to Google OCI

    ActiveCampaign to Google Offline Conversions: Signals reads your ActiveCampaign contacts…

    Learn more

    generic

    Google Offline Conversion Import

    Datahash automates GCLID-based OCI uploads to Google Ads so click-based offline conversions…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the GCS Google OCI sync run?

    The pace follows your GCS objects: Signals sends changes from GCS to Google Ads each time a new file lands. Because it processes only the newly dropped file, Smart Bidding trained on booked revenue instead of a mid-funnel proxy stays current while data teams landing exports in GCS keep GCLID coverage in view. Delivery needs no export and no manual upload.

    What match rate should a GCS-sourced Google OCI 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 Google Ads; neither, and it will not. First-run feedback flags GCLID coverage, which data teams landing exports in GCS then raise inside your GCS objects.

    NEXT STEP

    GCS to Google OCI, in production this week.

    Talk to our team All GCS use cases