Jump to a popular page, or start typing.

    CONNECTIONS / Couchbase / Couchbase to Google Store Sales

    Your Couchbase buckets, wired to Google Store Sales matching.

    Connect Couchbase and point Signals at your Couchbase buckets; it matches in-person transactions to Google accounts as store-sales conversions each time the read runs, hashed and consent-checked for Google Ads.

    couchbase -> google-store-sales :: live

    1. ● couchbase → google.sales :: live
    2. > read closed_deals rows=31,280
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 27,839 matched

    WHAT THIS ENABLES

    Couchbase to Google Store Sales

    Google Store Sales for Couchbase: Signals matches in-person transactions to Google accounts as store-sales conversions straight from your Couchbase buckets, hashed and consent-screened each time the read runs.

    • Offline and in-store sales from your Couchbase buckets activated for Google Ads, as Signals matches in-person transactions to Google accounts as store-sales conversions.
    • Counter and showroom revenue inside the same ROAS view as online orders, drawn from your Couchbase buckets by engineering teams on Couchbase.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off Google, away from any pixel. Here is how Couchbase closes the loop.

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google Scheduled read sync recorded in Couchbase S Signals hash · dedupe Store Sales Direct API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Omnichannel retailers reconciling point-of-sale against Google spend, with the records already in Couchbase buckets, scopes, and collections.

    Engineering teams on Couchbase activating Google Store Sales matching 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' Store Sales Direct API, sized for the store-sales match rate.

    2. Map

      A scheduled read pulls your Couchbase buckets, and its columns map to Google Ads' Store Sales Direct API in the visual mapper, hashed and checked for the store-sales match rate.

    3. Deliver

      On each run, Signals pulls your Couchbase buckets, matches in-person transactions to Google accounts as store-sales conversions, and reads only the records changed since the last run, with the store-sales match rate in the debugger.

    WHAT YOU GET

    What changes when the CSV goes away.

    Capability Manual CSV upload Datahash
    Reporting Offline sales sit in a separate export, reconciled by hand. Revenue counted in the same Store Sales reporting as web conversions.
    Deduplication A re-uploaded file risks counting the same conversion twice. Deduped delivery, so a resent record never counts as a second conversion.
    Match visibility Match quality is a guess until the numbers look off. Match rate reported per upload, tied to the source event set that produced it.
    Effort and latency An analyst exports and uploads on a manual cadence. Server-side and automatic the moment Couchbase records the event.
    ON THE WIRE

    What Store Sales actually receives.

    signals :: couchbase.google-store-sales :: wire

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=couchbase.closed_deals
    3. transaction_time 2026-07-15T15:57:27 · transaction_amount_micros 27768000000
    4. currency_code SAR
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=89%
    FAQ

    Asked on almost every call.

    How often does the Couchbase Google Store Sales 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, counter and showroom revenue inside the same ROAS view as online orders keeps pace and engineering teams on Couchbase watch the store-sales match rate. One scoped connection sets it up, cadence adjustable later.

    What match rate should a Couchbase-sourced Google Store Sales 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 Store Sales Direct API report shows engineering teams on Couchbase where the store-sales match rate needs work, a data-quality task handled in Couchbase.

    NEXT STEP

    Couchbase to Google Store Sales, in production this week.