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

    CONNECTIONS / AWS S3 / AWS S3 to Google Customer Match

    S3 exports into Google Ads, built for Google Customer Match.

    Signals reads your S3 exports through a read-only IAM key scoped to the one S3 bucket you name, then projects your segments into Google Ads as Customer Match lists so Google Ads sees match-ready audiences without an export.

    Talk to our team Explore the setup

    aws-s3 -> google-customer-match :: live

    1. ● aws s3 → google.match :: live
    2. > read segments rows=40,634
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 30,476 matched

    WHAT THIS ENABLES

    AWS S3 to Google Customer Match

    Google Customer Match for AWS S3: Signals projects your segments into Google Ads as Customer Match lists straight from your S3 exports, hashed and consent-screened each time a new file lands.

    • Signals projects your segments into Google Ads as Customer Match lists, reading your S3 exports each time a new file lands.
    • Lists that self-maintain across syncs, with no export step out of your S3 exports.

    WHAT FLOWS WHERE

    AWS S3 to Customer Match, mapped.

    Signals picks up the customer segments from your S3 exports; Signals hashes and consent-screens each record before Google Ads' Customer Match API accepts the match-ready audiences for the serving-size threshold.

    Signals picks up the customer segments from your S3 exports; Signals hashes and consent-screens each record before Google Ads' Customer Match API accepts the match-ready audiences for the serving-size threshold.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Growth teams feeding Google audiences from governed first-party data, working out of S3 objects, prefixes, and export drops.

    Data teams landing exports in S3 who need Customer Match lists that add joiners and drop lapsed members each sync 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' Customer Match API and tuned for the serving-size threshold.

    2. Map

      Columns from your S3 exports align to Google Ads' Customer Match API in the visual mapper, hashed as the file lands and checked for the serving-size threshold.

    3. Deliver

      Each time a new file lands, Signals reads your S3 exports and projects your segments into Google Ads as Customer Match lists, processes only the newly dropped file, with the serving-size threshold watched in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Customer Match lists that add joiners and drop lapsed members each sync from your S3 exports, delivered each time a new file lands.

    Lists that self-maintain across syncs out of your S3 exports, delivered each time a new file lands without transfer overhead climbing.

    Match feedback on the serving-size threshold from Google Ads' Customer Match API each run, tied back to your S3 exports.

    ON THE WIRE

    What Customer Match actually receives.

    signals :: aws-s3.google-customer-match :: wire

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=aws-s3.segments
    3. operation ADD · user_list "segment_83778"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 40,634 · members_matched 30,476
    6. ✓ accepted match=75%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from AWS S3

    AWS S3 to Meta Custom Audience

    Meta Custom Audience for AWS S3: Signals keeps Meta audiences synced as adds and removals…

    Learn more

    from AWS S3

    AWS S3 to TikTok Custom Audience

    TikTok Custom Audience for AWS S3: Signals delivers first-party segments to TikTok as…

    Learn more

    same use case

    ActiveCampaign to Google Customer Match

    ActiveCampaign to Google Customer Match: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    Google Customer Match

    Datahash builds and refreshes Google Customer Match audiences from your CRM, warehouse, or…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the AWS S3 Google Customer Match 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, Customer Match lists that add joiners and drop lapsed members each sync keeps pace and data teams landing exports in S3 watch the serving-size threshold. One scoped connection sets it up, cadence adjustable later.

    What match rate should a AWS S3-sourced Google Customer Match 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 Customer Match API pinpoints the serving-size threshold, the number data teams landing exports in S3 tune against.

    NEXT STEP

    AWS S3 to Google Customer Match, in production this week.

    Talk to our team All AWS S3 use cases