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

    CONNECTIONS / Apache Cassandra / Apache Cassandra to Google Customer Match

    From Cassandra tables to Google Customer Match.

    Connect Apache Cassandra and point Signals at your Cassandra 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

    apache-cassandra -> google-customer-match :: live

    1. ● apache cassandra → google.match :: live
    2. > read segments rows=63,581
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 49,593 matched

    WHAT THIS ENABLES

    Apache Cassandra to Google Customer Match

    Apache Cassandra to Google Customer Match: Signals reads your Cassandra tables and projects your segments into Google Ads as Customer Match lists, hashed and consent-checked each time the read runs.

    • Customer segments from your Cassandra 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 Cassandra tables by platform teams running Cassandra.

    WHAT FLOWS WHERE

    Apache Cassandra to Customer Match, mapped.

    A scheduled read pulls the customer segments from your Cassandra 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 Cassandra 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 Cassandra tables and materialized views.

    Platform teams running Cassandra activating Google Customer Match straight from Cassandra tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

      A scheduled read pulls your Cassandra 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 Cassandra 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 Cassandra tables and reads only the records changed since the last run.

    Lists that self-maintain across syncs from your Cassandra 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 Cassandra tables.

    ON THE WIRE

    What Customer Match actually receives.

    signals :: apache-cassandra.google-customer-match :: wire

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=apache-cassandra.segments
    3. operation ADD · user_list "segment_46741"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 63,581 · members_matched 49,593
    6. ✓ accepted match=78%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Apache Cassandra

    Apache Cassandra to Meta Custom Audience

    Apache Cassandra to Meta Custom Audience: Signals reads your Cassandra tables and keeps…

    Learn more

    from Apache Cassandra

    Apache Cassandra to TikTok Custom Audience

    Apache Cassandra to TikTok Custom Audience: Signals reads your Cassandra tables and…

    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 Apache Cassandra Google Customer Match sync run?

    You set the cadence, from near-real-time to a nightly Apache Cassandra sync of your Cassandra tables into Google Ads. Since Signals reads only the records changed since the last run, Customer Match lists that add joiners and drop lapsed members each sync keeps pace and platform teams running Cassandra watch the serving-size threshold. One scoped connection sets it up, cadence adjustable later.

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

    In Apache Cassandra, match rate tracks the email and phone quality your Cassandra tables carry. Clean identifiers land for Google Ads; blank ones never will. The first Customer Match API report shows platform teams running Cassandra where the serving-size threshold needs work, a data-quality task handled in Apache Cassandra.

    NEXT STEP

    Apache Cassandra to Google Customer Match, in production this week.

    Talk to our team All Apache Cassandra use cases