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

    CONNECTIONS / AWS S3 / AWS S3 to Google Store Sales

    S3 exports into Google Ads, built for Google Store Sales matching.

    Signals reads your S3 exports through a read-only IAM key scoped to the one S3 bucket you name, then matches in-person transactions to Google accounts as store-sales conversions so Google Ads sees offline conversions without an export.

    Talk to our team Explore the setup

    aws-s3 -> google-store-sales :: live

    1. ● aws s3 → google.sales :: live
    2. > read closed_deals rows=20,929
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 18,418 matched

    WHAT THIS ENABLES

    AWS S3 to Google Store Sales

    Google Store Sales for AWS S3: Signals matches in-person transactions to Google accounts as store-sales conversions straight from your S3 exports, hashed and consent-screened each time a new file lands.

    • Signals matches in-person transactions to Google accounts as store-sales conversions, reading your S3 exports each time a new file lands.
    • Store visits reconciled to campaign spend, 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 Store Sales Direct API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Omnichannel retailers reconciling point-of-sale against Google spend, working out of S3 objects, prefixes, and export drops.

    Data teams landing exports in S3 who need counter and showroom revenue inside the same ROAS view as online orders 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' Store Sales Direct API and tuned for the store-sales match rate.

    2. Map

      Columns from your S3 exports align to Google Ads' Store Sales Direct API in the visual mapper, hashed as the file lands and checked for the store-sales match rate.

    3. Deliver

      Each time a new file lands, Signals reads your S3 exports and matches in-person transactions to Google accounts as store-sales conversions, processes only the newly dropped file, with the store-sales match rate 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 Store Sales 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 Store Sales actually receives.

    signals :: aws-s3.google-store-sales :: wire

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=aws-s3.closed_deals
    3. transaction_time 2026-07-16T12:34:02 · transaction_amount_micros 29843000000
    4. currency_code GBP
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=88%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from AWS S3

    AWS S3 to Google OCI

    Google Offline Conversions for AWS S3: Signals reconciles closed-won revenue to the Google…

    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 Store Sales

    ActiveCampaign to Google Store Sales: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Google Store Sales

    Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the AWS S3 Google Store Sales 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, counter and showroom revenue inside the same ROAS view as online orders keeps pace and data teams landing exports in S3 watch the store-sales match rate. One scoped connection sets it up, cadence adjustable later.

    What match rate should a AWS S3-sourced Google Store Sales 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 Store Sales Direct API pinpoints the store-sales match rate, the number data teams landing exports in S3 tune against.

    NEXT STEP

    AWS S3 to Google Store Sales, in production this week.

    Talk to our team All AWS S3 use cases