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

    CONNECTIONS / Cockroach / Cockroach to Google OCI

    From Cockroach tables to Google Ads offline conversion import.

    Connect Cockroach and point Signals at your Cockroach tables; it reconciles closed-won revenue to the Google Ads click through GCLID each time the read runs, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    cockroach -> google-oci :: live

    1. ● cockroach → google.oci :: live
    2. > read closed_deals rows=25,666
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 21,046 matched

    WHAT THIS ENABLES

    Cockroach to Google Offline Conversions

    Google Offline Conversions for Cockroach: Signals reconciles closed-won revenue to the Google Ads click through GCLID 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 reconciles closed-won revenue to the Google Ads click through GCLID.
    • Smart Bidding trained on booked revenue instead of a mid-funnel proxy, 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 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, with the records already in Cockroach tables and secondary indexes.

    Platform teams running CockroachDB activating Google Ads offline conversion import 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' Offline Conversion Import (Google Ads API), sized for GCLID coverage.

    2. Map

      A scheduled read pulls your Cockroach tables, and its columns map to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed and checked for GCLID coverage.

    3. Deliver

      On each run, Signals pulls your Cockroach tables, reconciles closed-won revenue to the Google Ads click through GCLID, and reads only the records changed since the last run, with GCLID coverage 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 Cockroach records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: cockroach.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=cockroach.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-21T03:58:44"
    5. conversion_value 37590 · currency_code AED
    6. ✓ accepted · batch=hourly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Cockroach

    Cockroach to Google Store Sales

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

    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 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 Cockroach Google OCI 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, Smart Bidding trained on booked revenue instead of a mid-funnel proxy stays current while platform teams running CockroachDB keep GCLID coverage in view. Delivery needs no export and no manual upload.

    What match rate should a Cockroach-sourced Google OCI 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 GCLID coverage, which platform teams running CockroachDB then raise inside your Cockroach tables.

    NEXT STEP

    Cockroach to Google OCI, in production this week.

    Talk to our team All Cockroach use cases