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

    CONNECTIONS / Couchbase / Couchbase to Google OCI

    Your Couchbase buckets, wired to Google Ads offline conversion import.

    Connect Couchbase and point Signals at your Couchbase buckets; 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

    couchbase -> google-oci :: live

    1. ● couchbase → google.oci :: live
    2. > read closed_deals rows=42,796
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 37,660 matched

    WHAT THIS ENABLES

    Couchbase to Google Offline Conversions

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

    • Offline and in-store sales from your Couchbase buckets 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 Couchbase buckets by engineering teams on Couchbase.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google Scheduled read sync recorded in Couchbase 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 Couchbase buckets, scopes, and collections.

    Engineering teams on Couchbase activating Google Ads offline conversion import straight from Couchbase buckets.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

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

    What OCI actually receives.

    signals :: couchbase.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=couchbase.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-16T17:57:26"
    5. conversion_value 45668 · currency_code GBP
    6. ✓ accepted · batch=hourly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Couchbase

    Couchbase to Google Store Sales

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

    Learn more

    from Couchbase

    Couchbase to Meta Offline CAPI

    Meta Offline CAPI for Couchbase: 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 Couchbase Google OCI sync run?

    You set the cadence, from near-real-time to a nightly Couchbase sync of your Couchbase buckets 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 engineering teams on Couchbase watch GCLID coverage. One scoped connection sets it up, cadence adjustable later.

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

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

    NEXT STEP

    Couchbase to Google OCI, in production this week.

    Talk to our team All Couchbase use cases