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

    CONNECTIONS / Couchbase / Couchbase to Google Customer Match

    Your Couchbase buckets, wired to Google Customer Match.

    Connect Couchbase and point Signals at your Couchbase buckets; 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

    couchbase -> google-customer-match :: live

    1. ● couchbase → google.match :: live
    2. > read segments rows=62,920
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 54,111 matched

    WHAT THIS ENABLES

    Couchbase to Google Customer Match

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

    • Customer segments from your Couchbase buckets 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 Couchbase buckets by engineering teams on Couchbase.

    WHAT FLOWS WHERE

    Couchbase to Customer Match, mapped.

    Signals reads the customer segments from your Couchbase buckets 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 Couchbase buckets 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 Couchbase buckets, scopes, and collections.

    Engineering teams on Couchbase activating Google Customer Match straight from Couchbase buckets.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

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

    Lists that self-maintain across syncs from your Couchbase buckets, 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 Couchbase buckets.

    ON THE WIRE

    What Customer Match actually receives.

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

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=couchbase.segments
    3. operation ADD · user_list "segment_86881"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 62,920 · members_matched 54,111
    6. ✓ accepted match=86%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Couchbase

    Couchbase to Meta Custom Audience

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

    Learn more

    from Couchbase

    Couchbase to TikTok Custom Audience

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

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

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

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

    NEXT STEP

    Couchbase to Google Customer Match, in production this week.

    Talk to our team All Couchbase use cases