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

    CONNECTIONS / MariaDB / MariaDB to Google Customer Match

    MariaDB tables into Google Ads, built for Google Customer Match.

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

    mariadb -> google-customer-match :: live

    1. ● mariadb → google.match :: live
    2. > read segments rows=21,130
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 18,806 matched

    WHAT THIS ENABLES

    MariaDB to Google Customer Match

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

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

    WHAT FLOWS WHERE

    MariaDB to Customer Match, mapped.

    Each sync hands the customer segments from your MariaDB 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 MariaDB 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 MariaDB tables and views.

    Engineering teams running MariaDB who need Customer Match lists that add joiners and drop lapsed members each sync out of MariaDB tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

      Columns from your MariaDB 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 MariaDB 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 MariaDB tables, delivered each time the read runs.

    Lists that self-maintain across syncs out of your MariaDB 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 MariaDB tables.

    ON THE WIRE

    What Customer Match actually receives.

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

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=mariadb.segments
    3. operation ADD · user_list "segment_88918"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 21,130 · members_matched 18,806
    6. ✓ accepted match=89%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from MariaDB

    MariaDB to Meta Custom Audience

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

    Learn more

    from MariaDB

    MariaDB to TikTok Custom Audience

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

    You set the cadence, from near-real-time to a nightly MariaDB sync of your MariaDB 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 engineering teams running MariaDB watch the serving-size threshold. One scoped connection sets it up, cadence adjustable later.

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

    Match rate follows identifier coverage in your MariaDB tables, which engineering teams running MariaDB control, not MariaDB itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Customer Match API pinpoints the serving-size threshold, the number engineering teams running MariaDB tune against.

    NEXT STEP

    MariaDB to Google Customer Match, in production this week.

    Talk to our team All MariaDB use cases