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

    CONNECTIONS / Clickhouse / ClickHouse to Google Customer Match

    From ClickHouse tables to Google Customer Match.

    Signals reads your ClickHouse tables through a read-only database user scoped to the ClickHouse tables 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

    clickhouse -> google-customer-match :: live

    1. ● clickhouse → google.match :: live
    2. > read segments rows=23,570
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 19,092 matched

    WHAT THIS ENABLES

    ClickHouse to Google Customer Match

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

    • Signals projects your segments into Google Ads as Customer Match lists, reading your ClickHouse tables each time the read runs.
    • Lists that self-maintain across syncs, with no export step out of your ClickHouse tables.

    WHAT FLOWS WHERE

    Clickhouse to Customer Match, mapped.

    Each sync hands the customer segments from your ClickHouse tables to Signals, which hashes and filters every record, then Google Ads' Customer Match API logs the match-ready audiences for the serving-size threshold.

    Each sync hands the customer segments from your ClickHouse tables to Signals, which hashes and filters every record, then Google Ads' Customer Match API logs 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 ClickHouse tables and materialized views.

    Analytics engineers on ClickHouse who need Customer Match lists that add joiners and drop lapsed members each sync out of ClickHouse tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the ClickHouse tables you name, mapped to Google Ads' Customer Match API and tuned for the serving-size threshold.

    2. Map

      Columns from your ClickHouse tables align to Google Ads' Customer Match API in the visual mapper, hashed as the read runs and checked for the serving-size threshold.

    3. Deliver

      Each time the read runs, Signals reads your ClickHouse tables and projects your segments into Google Ads as Customer Match lists, reads only the records changed since the last run, 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 ClickHouse tables, delivered each time the read runs.

    Lists that self-maintain across syncs out of your ClickHouse tables, delivered each time the read runs without read load on the database climbing.

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

    ON THE WIRE

    What Customer Match actually receives.

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

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=clickhouse.segments
    3. operation ADD · user_list "segment_44012"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 23,570 · members_matched 19,092
    6. ✓ accepted match=81%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Clickhouse

    ClickHouse to Meta Custom Audience

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

    Learn more

    from Clickhouse

    ClickHouse to TikTok Custom Audience

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

    The pace follows your ClickHouse tables: Signals sends changes from ClickHouse 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 analytics engineers on ClickHouse keep the serving-size threshold in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    ClickHouse to Google Customer Match, in production this week.

    Talk to our team All Clickhouse use cases