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

    CONNECTIONS / Datahash API / Datahash API to Google Customer Match

    Post customer segments to the Datahash API, wired to Google Customer Match.

    Send customer segments to one documented REST endpoint from any backend, in any language; Signals projects your segments into Google Ads as Customer Match lists, hashed and consent-checked, with no pixel and no warehouse read.

    Talk to our team Explore the setup

    datahash-api -> google-customer-match :: live

    1. ● datahash-api → google.match :: live
    2. > POST /v1/events source=api.audience_members count=43,009
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ 202 accepted · 34,407 forwarded

    WHAT THIS ENABLES

    Datahash API to Google Customer Match

    Datahash API to Google Customer Match: post your customer segments to one REST endpoint and Signals projects your segments into Google Ads as Customer Match lists, hashed and consent-checked server-side before Google Ads sees it.

    • Signals projects your segments into Google Ads as Customer Match lists, from events your backend posts server-side.
    • Customer Match lists that add joiners and drop lapsed members each sync, without a pixel, a connector, or a nightly export.

    WHAT FLOWS WHERE

    Datahash API to Customer Match, mapped.

    Your backend posts each event to the Datahash API, which hashes and consent-screens it server-side, then Google Ads' Customer Match API records the match-ready audiences for the serving-size threshold.

    Your backend posts each event to the Datahash API, which hashes and consent-screens it server-side, then Google Ads' Customer Match API records 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, whose engineers would rather POST an event than maintain a connector.

    Backend and platform teams driving Google Customer Match by sending customer segments straight from their own stack.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Create an API key in the Signals console and point your backend at the endpoint that feeds Google Ads' Customer Match API.

    2. Map

      Map your event payload to Google Ads' Customer Match API fields once; per-request validation flags bad events instead of dropping the batch.

    3. Deliver

      Post events as they happen and Signals projects your segments into Google Ads as Customer Match lists, hashing server-side, with the serving-size threshold shown 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 a single server-side call.

    Lists that self-maintain across syncs, with identifiers hashed at ingestion or sent pre-hashed.

    Per-event status and match feedback on the serving-size threshold from Google Ads' Customer Match API, returned inline in the live debugger.

    ON THE WIRE

    What Customer Match actually receives.

    signals :: datahash-api.google-customer-match :: wire

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=api.audience_members
    3. operation ADD · user_list "segment_42733"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 43,009 · members_matched 34,407
    6. ✓ accepted match=80%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Datahash API

    Datahash API to Meta Custom Audience

    Datahash API to Meta Custom Audience: post your customer segments to one REST endpoint and…

    Learn more

    from Datahash API

    Datahash API to TikTok Custom Audience

    Datahash API to TikTok Custom Audience: post your customer segments to one REST endpoint…

    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.

    Which backends can send to Google Customer Match through the Datahash API?

    Any backend that can make an HTTPS request. You POST customer segments as JSON to one documented endpoint and Signals forwards the match-ready audiences to Google Ads' Customer Match API; identifiers are hashed at ingestion or sent pre-hashed, and growth teams feeding Google audiences from governed first-party data track the serving-size threshold in the debugger.

    How fresh are Google Customer Match events sent over the API?

    As fresh as you post them. The API accepts events in near real time, so Customer Match lists that add joiners and drop lapsed members each sync reaches Google Ads moments after your backend fires the call, with per-event status returned inline. There is no batch window and no scheduled read, which keeps the serving-size threshold current for the teams driving Google Customer Match.

    NEXT STEP

    Datahash API to Google Customer Match, in production this week.

    Talk to our team All Datahash API use cases