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

    CONNECTIONS / AWS S3 / AWS S3 to Google OCI

    S3 exports into Google Ads, built for Google Ads offline conversion import.

    Signals reads your S3 exports through a read-only IAM key scoped to the one S3 bucket you name, then reconciles closed-won revenue to the Google Ads click through GCLID so Google Ads sees offline conversions without an export.

    Talk to our team Explore the setup

    aws-s3 -> google-oci :: live

    1. ● aws s3 → google.oci :: live
    2. > read closed_deals rows=59,069
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 52,571 matched

    WHAT THIS ENABLES

    AWS S3 to Google Offline Conversions

    Google Offline Conversions for AWS S3: Signals reconciles closed-won revenue to the Google Ads click through GCLID straight from your S3 exports, hashed and consent-screened each time a new file lands.

    • Signals reconciles closed-won revenue to the Google Ads click through GCLID, reading your S3 exports each time a new file lands.
    • A clean line from click to closed revenue, with no export step out of your S3 exports.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off Google, away from any pixel. Here is how AWS S3 closes the loop.

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google A File drop sync recorded in AWS S3 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, working out of S3 objects, prefixes, and export drops.

    Data teams landing exports in S3 who need Smart Bidding trained on booked revenue instead of a mid-funnel proxy out of S3 exports.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only IAM key scoped to the one S3 bucket you name, mapped to Google Ads' Offline Conversion Import (Google Ads API) and tuned for GCLID coverage.

    2. Map

      Columns from your S3 exports align to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed as the file lands and checked for GCLID coverage.

    3. Deliver

      Each time a new file lands, Signals reads your S3 exports and reconciles closed-won revenue to the Google Ads click through GCLID, processes only the newly dropped file, with GCLID coverage 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 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 AWS S3 records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: aws-s3.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=aws-s3.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-19T19:47:15"
    5. conversion_value 32692 · currency_code SAR
    6. ✓ accepted · batch=daily
    RELATED USE CASES

    Adjacent moves on the same stack.

    from AWS S3

    AWS S3 to Google Store Sales

    Google Store Sales for AWS S3: Signals matches in-person transactions to Google accounts as…

    Learn more

    from AWS S3

    AWS S3 to Meta Offline CAPI

    Meta Offline CAPI for AWS S3: Signals credits dealer, branch, and phone sales to the Meta…

    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 AWS S3 Google OCI sync run?

    You set the cadence, from near-real-time to a nightly AWS S3 sync of your S3 exports into Google Ads. Since Signals processes only the newly dropped file, Smart Bidding trained on booked revenue instead of a mid-funnel proxy keeps pace and data teams landing exports in S3 watch GCLID coverage. One scoped connection sets it up, cadence adjustable later.

    What match rate should a AWS S3-sourced Google OCI batch expect?

    Match rate follows identifier coverage in your S3 exports, which data teams landing exports in S3 control, not AWS S3 itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Offline Conversion Import (Google Ads API) pinpoints GCLID coverage, the number data teams landing exports in S3 tune against.

    NEXT STEP

    AWS S3 to Google OCI, in production this week.

    Talk to our team All AWS S3 use cases