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

    CONNECTIONS / Apache Cassandra / Apache Cassandra to Google OCI

    From Cassandra tables to Google Ads offline conversion import.

    Connect Apache Cassandra and point Signals at your Cassandra 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

    apache-cassandra -> google-oci :: live

    1. ● apache cassandra → google.oci :: live
    2. > read closed_deals rows=55,673
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 44,538 matched

    WHAT THIS ENABLES

    Apache Cassandra to Google Offline Conversions

    Apache Cassandra to Google Offline Conversions: Signals reads your Cassandra tables and reconciles closed-won revenue to the Google Ads click through GCLID, hashed and consent-checked each time the read runs.

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

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google Scheduled read sync recorded in Apache Cassan… 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 Cassandra tables and materialized views.

    Platform teams running Cassandra activating Google Ads offline conversion import straight from Cassandra tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the Cassandra tables you name to feed Google Ads' Offline Conversion Import (Google Ads API), sized for GCLID coverage.

    2. Map

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

    What OCI actually receives.

    signals :: apache-cassandra.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=apache-cassandra.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-18T11:55:30"
    5. conversion_value 38266 · currency_code GBP
    6. ✓ accepted · batch=daily
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Apache Cassandra

    Apache Cassandra to Google Store Sales

    Apache Cassandra to Google Store Sales: Signals reads your Cassandra tables and matches…

    Learn more

    from Apache Cassandra

    Apache Cassandra to Meta Offline CAPI

    Apache Cassandra to Meta Offline CAPI: Signals reads your Cassandra tables and credits…

    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 Apache Cassandra Google OCI sync run?

    You set the cadence, from near-real-time to a nightly Apache Cassandra sync of your Cassandra tables into Google Ads. Since Signals reads only the records changed since the last run, Smart Bidding trained on booked revenue instead of a mid-funnel proxy keeps pace and platform teams running Cassandra watch GCLID coverage. One scoped connection sets it up, cadence adjustable later.

    What match rate should a Apache Cassandra-sourced Google OCI batch expect?

    In Apache Cassandra, match rate tracks the email and phone quality your Cassandra tables carry. Clean identifiers land for Google Ads; blank ones never will. The first Offline Conversion Import (Google Ads API) report shows platform teams running Cassandra where GCLID coverage needs work, a data-quality task handled in Apache Cassandra.

    NEXT STEP

    Apache Cassandra to Google OCI, in production this week.

    Talk to our team All Apache Cassandra use cases