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

    CONNECTIONS / Cockroach / Cockroach to Google Customer Match

    From Cockroach tables to Google Customer Match.

    Connect Cockroach and point Signals at your Cockroach tables; it projects your segments into Google Ads as Customer Match lists each time the read runs, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    cockroach -> google-customer-match :: live

    1. ● cockroach → google.match :: live
    2. > read segments rows=17,849
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 13,922 matched

    WHAT THIS ENABLES

    Cockroach to Google Customer Match

    Google Customer Match for Cockroach: Signals projects your segments into Google Ads as Customer Match lists straight from your Cockroach tables, hashed and consent-screened each time the read runs.

    • Customer segments from your Cockroach tables activated for Google Ads, as Signals projects your segments into Google Ads as Customer Match lists.
    • Customer Match lists that add joiners and drop lapsed members each sync, drawn from your Cockroach tables by platform teams running CockroachDB.

    WHAT FLOWS WHERE

    Cockroach to Customer Match, mapped.

    A scheduled read pulls the customer segments from your Cockroach tables; Signals hashes and consent-screens each record before Google Ads' Customer Match API accepts the match-ready audiences for the serving-size threshold.

    A scheduled read pulls the customer segments from your Cockroach tables; 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, with the records already in Cockroach tables and secondary indexes.

    Platform teams running CockroachDB activating Google Customer Match straight from Cockroach tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the Cockroach tables you name to feed Google Ads' Customer Match API, sized for the serving-size threshold.

    2. Map

      A scheduled read pulls your Cockroach tables, and its columns map to Google Ads' Customer Match API in the visual mapper, hashed and checked for the serving-size threshold.

    3. Deliver

      On each run, Signals pulls your Cockroach tables, projects your segments into Google Ads as Customer Match lists, and reads only the records changed since the last run, with the serving-size threshold in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Customer Match lists that add joiners and drop lapsed members each sync on every run, as Signals reads your Cockroach tables and reads only the records changed since the last run.

    Lists that self-maintain across syncs from your Cockroach tables, with read load on the database steady because Signals reads only the records changed since the last run.

    A per-run match report from Google Ads' Customer Match API on the serving-size threshold, straight out of your Cockroach tables.

    ON THE WIRE

    What Customer Match actually receives.

    signals :: cockroach.google-customer-match :: wire

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=cockroach.segments
    3. operation ADD · user_list "segment_59815"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 17,849 · members_matched 13,922
    6. ✓ accepted match=78%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Cockroach

    Cockroach to Meta Custom Audience

    Meta Custom Audience for Cockroach: Signals keeps Meta audiences synced as adds and…

    Learn more

    from Cockroach

    Cockroach to TikTok Custom Audience

    TikTok Custom Audience for Cockroach: 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 Cockroach Google Customer Match sync run?

    The pace follows your Cockroach tables: Signals sends changes from Cockroach to Google Ads each time the read runs. Because it reads only the records changed since the last run, Customer Match lists that add joiners and drop lapsed members each sync stays current while platform teams running CockroachDB keep the serving-size threshold in view. Delivery needs no export and no manual upload.

    What match rate should a Cockroach-sourced Google Customer Match batch expect?

    Coverage of hashed identifiers across your Cockroach tables decides it, and platform teams running CockroachDB own that inside Cockroach. A live email or phone matches into Google Ads; neither, and it will not. First-run feedback flags the serving-size threshold, which platform teams running CockroachDB then raise inside your Cockroach tables.

    NEXT STEP

    Cockroach to Google Customer Match, in production this week.

    Talk to our team All Cockroach use cases