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

    CONNECTIONS / MongoDB / MongoDB to Google OCI

    From MongoDB collections to Google Ads offline conversion import.

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

    mongodb -> google-oci :: live

    1. ● mongodb → google.oci :: live
    2. > read closed_deals rows=43,922
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 36,455 matched

    WHAT THIS ENABLES

    MongoDB to Google Offline Conversions

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

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

    The click, the conversion, and the credit.

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

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

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

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

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

    What OCI actually receives.

    signals :: mongodb.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=mongodb.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-13T12:48:45"
    5. conversion_value 42065 · currency_code USD
    6. ✓ accepted · batch=daily
    RELATED USE CASES

    Adjacent moves on the same stack.

    from MongoDB

    MongoDB to Google Store Sales

    MongoDB to Google Store Sales: Signals reads your MongoDB collections and matches in-person…

    Learn more

    from MongoDB

    MongoDB to Meta Offline CAPI

    MongoDB to Meta Offline CAPI: Signals reads your MongoDB collections and credits dealer,…

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

    The pace follows your MongoDB collections: Signals sends changes from MongoDB 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 application teams running MongoDB keep GCLID coverage in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    MongoDB to Google OCI, in production this week.

    Talk to our team All MongoDB use cases