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

    CONNECTIONS / CouchDB / CouchDB to Google Customer Match

    CouchDB documents into Google Ads, built for Google Customer Match.

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

    couchdb -> google-customer-match :: live

    1. ● couchdb → google.match :: live
    2. > read segments rows=71,419
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 63,563 matched

    WHAT THIS ENABLES

    CouchDB to Google Customer Match

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

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

    WHAT FLOWS WHERE

    CouchDB to Customer Match, mapped.

    Each sync hands the customer segments from your CouchDB documents 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 CouchDB documents 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 CouchDB documents and map/reduce views.

    Application teams running CouchDB who need Customer Match lists that add joiners and drop lapsed members each sync out of CouchDB documents.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

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

    Lists that self-maintain across syncs out of your CouchDB documents, 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 CouchDB documents.

    ON THE WIRE

    What Customer Match actually receives.

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

    1. ● signals :: audience upload
    2. > POST /user_list_operations source=couchdb.segments
    3. operation ADD · user_list "segment_92902"
    4. hashed_email sha256 "b02cf1…" · hashed_phone sha256 "3ad990…"
    5. members_uploaded 71,419 · members_matched 63,563
    6. ✓ accepted match=89%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from CouchDB

    CouchDB to Meta Custom Audience

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

    Learn more

    from CouchDB

    CouchDB to TikTok Custom Audience

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

    Delivery tracks CouchDB, run by application teams running CouchDB: a near-real-time or scheduled sync of your CouchDB documents feeds Google Ads on that cadence. Each run reads only the records changed since the last run, so lists that self-maintain across syncs holds up on the serving-size threshold. The live debugger confirms every delivery inline.

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

    Coverage of hashed identifiers across your CouchDB documents decides it, and application teams running CouchDB own that inside CouchDB. A live email or phone matches into Google Ads; neither, and it will not. First-run feedback flags the serving-size threshold, which application teams running CouchDB then raise inside your CouchDB documents.

    NEXT STEP

    CouchDB to Google Customer Match, in production this week.

    Talk to our team All CouchDB use cases