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

    CONNECTIONS / Clickhouse / ClickHouse to Google Store Sales

    From ClickHouse tables to Google Store Sales matching.

    Signals reads your ClickHouse tables through a read-only database user scoped to the ClickHouse tables you name, then matches in-person transactions to Google accounts as store-sales conversions so Google Ads sees offline conversions without an export.

    Talk to our team Explore the setup

    clickhouse -> google-store-sales :: live

    1. ● clickhouse → google.sales :: live
    2. > read closed_deals rows=49,402
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 40,510 matched

    WHAT THIS ENABLES

    ClickHouse to Google Store Sales

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

    • Signals matches in-person transactions to Google accounts as store-sales conversions, reading your ClickHouse tables each time the read runs.
    • Store visits reconciled to campaign spend, with no export step out of your ClickHouse tables.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google Scheduled read sync recorded in Clickhouse 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, working out of ClickHouse tables and materialized views.

    Analytics engineers on ClickHouse who need counter and showroom revenue inside the same ROAS view as online orders out of ClickHouse tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the ClickHouse tables you name, mapped to Google Ads' Store Sales Direct API and tuned for the store-sales match rate.

    2. Map

      Columns from your ClickHouse tables align to Google Ads' Store Sales Direct API in the visual mapper, hashed as the read runs and checked for the store-sales match rate.

    3. Deliver

      Each time the read runs, Signals reads your ClickHouse tables and matches in-person transactions to Google accounts as store-sales conversions, reads only the records changed since the last run, with the store-sales match rate watched 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 Clickhouse records the event.
    ON THE WIRE

    What Store Sales actually receives.

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

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=clickhouse.closed_deals
    3. transaction_time 2026-07-16T02:59:20 · transaction_amount_micros 13633000000
    4. currency_code AED
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=82%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Clickhouse

    ClickHouse to Google OCI

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

    Learn more

    from Clickhouse

    ClickHouse to Meta Offline CAPI

    Meta Offline CAPI for ClickHouse: 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 ClickHouse Google Store Sales sync run?

    The pace follows your ClickHouse tables: Signals sends changes from ClickHouse 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 analytics engineers on ClickHouse keep the store-sales match rate in view. Delivery needs no export and no manual upload.

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

    In ClickHouse, match rate tracks the email and phone quality your ClickHouse tables carry. Clean identifiers land for Google Ads; blank ones never will. The first Store Sales Direct API report shows analytics engineers on ClickHouse where the store-sales match rate needs work, a data-quality task handled in ClickHouse.

    NEXT STEP

    ClickHouse to Google Store Sales, in production this week.

    Talk to our team All Clickhouse use cases