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

    CONNECTIONS / IBM DB2 / IBM DB2 to Google Customer Match

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

    Connect IBM DB2 and point Signals at your Db2 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

    ibm-db2 -> google-customer-match :: live

    1. ● ibm db2 → google.match :: live
    2. > read segments rows=56,267
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 47,264 matched

    WHAT THIS ENABLES

    IBM DB2 to Google Customer Match

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

    • Customer segments from your Db2 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 Db2 tables by enterprise data teams on IBM DB2.

    WHAT FLOWS WHERE

    IBM DB2 to Customer Match, mapped.

    Signals reads the customer segments from your Db2 tables each time the read runs, hashes and screens each record, and posts the match-ready audiences to Google Ads' Customer Match API, keeping the serving-size threshold in view.

    Signals reads the customer segments from your Db2 tables each time the read runs, hashes and screens each record, and posts the match-ready audiences to Google Ads' Customer Match API, keeping the serving-size threshold in view.

    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 Db2 tables and views.

    Enterprise data teams on IBM DB2 activating Google Customer Match straight from Db2 tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

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

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

    ON THE WIRE

    What Customer Match actually receives.

    signals :: ibm-db2.google-customer-match :: wire

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=ibm-db2.segments
    3. operation ADD · user_list "segment_77025"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 56,267 · members_matched 47,264
    6. ✓ accepted match=84%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from IBM DB2

    IBM DB2 to Meta Custom Audience

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

    Learn more

    from IBM DB2

    IBM DB2 to TikTok Custom Audience

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

    The pace follows your Db2 tables: Signals sends changes from IBM DB2 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 enterprise data teams on IBM DB2 keep the serving-size threshold in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    IBM DB2 to Google Customer Match, in production this week.

    Talk to our team All IBM DB2 use cases