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

    CONNECTIONS / Clickhouse / ClickHouse to Google OCI

    From ClickHouse tables to Google Ads offline conversion import.

    Signals reads your ClickHouse tables through a read-only database user scoped to the ClickHouse tables you name, then reconciles closed-won revenue to the Google Ads click through GCLID so Google Ads sees offline conversions without an export.

    Talk to our team Explore the setup

    clickhouse -> google-oci :: live

    1. ● clickhouse → google.oci :: live
    2. > read closed_deals rows=65,329
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 51,610 matched

    WHAT THIS ENABLES

    ClickHouse to Google Offline Conversions

    Google Offline Conversions for ClickHouse: Signals reconciles closed-won revenue to the Google Ads click through GCLID straight from your ClickHouse tables, hashed and consent-screened each time the read runs.

    • Signals reconciles closed-won revenue to the Google Ads click through GCLID, reading your ClickHouse tables each time the read runs.
    • A clean line from click to closed revenue, 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 Offline Conversion Impo… delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Advertisers whose Google-sourced deals close days after the click, working out of ClickHouse tables and materialized views.

    Analytics engineers on ClickHouse who need Smart Bidding trained on booked revenue instead of a mid-funnel proxy 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' Offline Conversion Import (Google Ads API) and tuned for GCLID coverage.

    2. Map

      Columns from your ClickHouse tables align to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed as the read runs and checked for GCLID coverage.

    3. Deliver

      Each time the read runs, Signals reads your ClickHouse tables and reconciles closed-won revenue to the Google Ads click through GCLID, reads only the records changed since the last run, with GCLID coverage 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 OCI 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 OCI actually receives.

    signals :: clickhouse.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=clickhouse.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-20T10:32:05"
    5. conversion_value 30328 · currency_code USD
    6. ✓ accepted · batch=hourly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Clickhouse

    ClickHouse to Google Store Sales

    Google Store Sales for ClickHouse: Signals matches in-person transactions to Google…

    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 OCI

    ActiveCampaign to Google Offline Conversions: Signals reads your ActiveCampaign contacts…

    Learn more

    generic

    Google Offline Conversion Import

    Datahash automates GCLID-based OCI uploads to Google Ads so click-based offline conversions…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the ClickHouse Google OCI 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, Smart Bidding trained on booked revenue instead of a mid-funnel proxy stays current while analytics engineers on ClickHouse keep GCLID coverage in view. Delivery needs no export and no manual upload.

    What match rate should a ClickHouse-sourced Google OCI 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 Offline Conversion Import (Google Ads API) report shows analytics engineers on ClickHouse where GCLID coverage needs work, a data-quality task handled in ClickHouse.

    NEXT STEP

    ClickHouse to Google OCI, in production this week.

    Talk to our team All Clickhouse use cases