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

    CONNECTIONS / Cockroach / Cockroach to Google Store Sales

    From Cockroach tables to Google Store Sales matching.

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

    Talk to our team Explore the setup

    cockroach -> google-store-sales :: live

    1. ● cockroach → google.sales :: live
    2. > read closed_deals rows=69,669
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 60,612 matched

    WHAT THIS ENABLES

    Cockroach to Google Store Sales

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

    • Offline and in-store sales from your Cockroach tables 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 Cockroach tables by platform teams running CockroachDB.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google Scheduled read sync recorded in Cockroach 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 Cockroach tables and secondary indexes.

    Platform teams running CockroachDB activating Google Store Sales matching straight from Cockroach tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the Cockroach tables you name to feed Google Ads' Store Sales Direct API, sized for the store-sales match rate.

    2. Map

      A scheduled read pulls your Cockroach tables, 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 Cockroach tables, 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 Cockroach records the event.
    ON THE WIRE

    What Store Sales actually receives.

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

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=cockroach.closed_deals
    3. transaction_time 2026-07-22T01:09:37 · transaction_amount_micros 13822000000
    4. currency_code USD
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=87%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Cockroach

    Cockroach to Google OCI

    Google Offline Conversions for Cockroach: Signals reconciles closed-won revenue to the…

    Learn more

    from Cockroach

    Cockroach to Meta Offline CAPI

    Meta Offline CAPI for Cockroach: Signals credits dealer, branch, and phone sales to the…

    Learn more

    same use case

    ActiveCampaign to Google Store Sales

    ActiveCampaign to Google Store Sales: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Google Store Sales

    Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Cockroach Google Store Sales sync run?

    The pace follows your Cockroach tables: Signals sends changes from Cockroach to Google Ads each time the read runs. Because it reads only the records changed since the last run, counter and showroom revenue inside the same ROAS view as online orders stays current while platform teams running CockroachDB keep the store-sales match rate in view. Delivery needs no export and no manual upload.

    What match rate should a Cockroach-sourced Google Store Sales batch expect?

    Coverage of hashed identifiers across your Cockroach tables decides it, and platform teams running CockroachDB own that inside Cockroach. A live email or phone matches into Google Ads; neither, and it will not. First-run feedback flags the store-sales match rate, which platform teams running CockroachDB then raise inside your Cockroach tables.

    NEXT STEP

    Cockroach to Google Store Sales, in production this week.

    Talk to our team All Cockroach use cases