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

    CONNECTIONS / CouchDB / CouchDB to Google OCI

    CouchDB documents into Google Ads, built for Google Ads offline conversion import.

    Signals reads your CouchDB documents through a read-only database user scoped to the CouchDB documents 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

    couchdb -> google-oci :: live

    1. ● couchdb → google.oci :: live
    2. > read closed_deals rows=31,429
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 26,715 matched

    WHAT THIS ENABLES

    CouchDB to Google Offline Conversions

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

    • Signals reconciles closed-won revenue to the Google Ads click through GCLID, reading your CouchDB documents each time the read runs.
    • A clean line from click to closed revenue, with no export step out of your CouchDB documents.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google Scheduled read sync recorded in CouchDB 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 CouchDB documents and map/reduce views.

    Application teams running CouchDB who need Smart Bidding trained on booked revenue instead of a mid-funnel proxy out of CouchDB documents.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the CouchDB documents you name, mapped to Google Ads' Offline Conversion Import (Google Ads API) and tuned for GCLID coverage.

    2. Map

      Columns from your CouchDB documents 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 CouchDB documents 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 CouchDB records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: couchdb.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=couchdb.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-20T08:07:35"
    5. conversion_value 36956 · currency_code SAR
    6. ✓ accepted · batch=hourly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from CouchDB

    CouchDB to Google Store Sales

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

    Learn more

    from CouchDB

    CouchDB to Meta Offline CAPI

    Meta Offline CAPI for CouchDB: Signals credits dealer, branch, and phone sales to the Meta…

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

    Delivery tracks CouchDB, run by application teams running CouchDB: a near-real-time or scheduled sync of your CouchDB documents feeds Google Ads on that cadence. Each run reads only the records changed since the last run, so a clean line from click to closed revenue holds up on GCLID coverage. The live debugger confirms every delivery inline.

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

    Coverage of hashed identifiers across your CouchDB documents decides it, and application teams running CouchDB own that inside CouchDB. A live email or phone matches into Google Ads; neither, and it will not. First-run feedback flags GCLID coverage, which application teams running CouchDB then raise inside your CouchDB documents.

    NEXT STEP

    CouchDB to Google OCI, in production this week.

    Talk to our team All CouchDB use cases