Jump to a popular page, or start typing.

    Google Customer Match

    Customer Match, refreshed from your source of truth.

    Datahash builds and refreshes Google Customer Match audiences from your CRM, warehouse, or SingleView, with hashed identifiers.

    google.customer-match :: live

    1. ● google.customer_match :: live
    2. > list high_value_buyers size=61,405
    3. hash sha256(em,ph) job=customer_match
    4. sync add 2,110 · remove 540 match 69%
    5. ✓ uploaded · list serving

    WHAT THIS ENABLES

    Google Customer Match

    Google Customer Match is the automated sync that builds and refreshes Google Ads audiences from your CRM, warehouse, or SingleView, uploading hashed identifiers so lists stay current across Search, YouTube, Gmail, and Display.

    • One segment reaches buyers across every Google surface, with campaigns running on current data instead of last cycle's export.
    • Existing buyers suppressed from acquisition so prospecting budget reaches new people.
    • Similar-audience seeds and retention lists that follow your source of truth as it changes.
    WHO THIS IS FOR

    Built for the teams that own the number.

    Advertisers running suppression, retention, and similar-audience plays on Google.

    Teams re-uploading customer lists to Google Ads by hand.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Source connect to CRM, warehouse, or SingleView.

    2. Segment

      Audience rules applied to your customer base.

    3. Upload

      Hash and upload via the Google Ads API.

    4. Refresh

      Scheduled refresh cadence so lists stay current.

    WHAT FLOWS WHERE

    One use case, every source.

    Your segment updates in the source system, Signals hashes the member identifiers and computes the incremental adds and removes, then syncs them to Google Ads through a Customer Match user-data job.

    Your segment updates in the source system, Signals hashes the member identifiers and computes the incremental adds and removes, then syncs them to Google Ads through a Customer Match user-data job.

    WHAT YOU GET

    What ships with this offering.

    Customer lists live across Search, YouTube, Gmail, and Display.

    Suppression of existing customers from acquisition campaigns.

    Hashed identifier handling per Google policy.

    ON THE WIRE

    What the platform actually receives.

    Identifiers are hashed with SHA-256 at source. The payload the destination sees never contains raw PII.

    signals :: google-customer-match :: wire

    1. ● signals :: audience payload
    2. > POST customers/{id}/offlineUserDataJobs (CUSTOMER_MATCH_USER_LIST)
    3. op create · add 2110 · remove 540
    4. user_identifiers hashed_email "3b8f…" · hashed_phone_number "c07d…"
    5. consent ad_user_data=GRANTED
    6. ✓ received · list_size 61405
    FAQ

    Questions your team will ask.

    Is there a minimum audience size?

    Google requires a minimum number of matched, active users before a Customer Match list can serve, generally in the region of 1,000 for most surfaces. Because match rates vary by identifier quality, a raw list of a few hundred contacts can still fall short after hashing and matching. We monitor matched size per list and flag segments that fall under the threshold, so you can consolidate similar segments or wait for the base to grow before launch.

    What match rate should we expect?

    It depends on identifier quality. Lists keyed on email and phone together typically match a meaningful majority of records once Datahash hashes them to SHA-256 and Google matches against signed-in Google accounts. Single-identifier lists, such as phone only, tend to match less. We report the matched count after every sync so you always know effective reach before you size a campaign around it.

    How often do audiences refresh?

    On the cadence you choose, from hourly to weekly. Datahash sends incremental adds and removes through the Google Ads offline user-data job rather than full re-uploads, so refreshes are fast and lists never go stale. For suppression and retention audiences that depend on knowing who bought recently, we default new builds to a daily cadence and tighten it if the account needs faster reaction.

    NEXT STEP

    Live in fifteen minutes. Measurable in a week.

    Talk to our team of solutions engineers. We map your source data, propose an integration plan, and give you a live setup in the same call where possible.