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

    CONNECTIONS / Microsoft Dynamics / Dynamics 365 to Google OCI

    Dynamics 365 opportunities and process flows into Google Ads, built for Google Ads offline conversion import.

    Signals reads your Dynamics 365 opportunities and process flows through scoped OAuth access to Dynamics 365, reading only your Dynamics 365 opportunities and process flows, 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

    dynamics -> google-oci :: live

    1. ● dynamics 365 → google.oci :: live
    2. > read closed_deals rows=30,136
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 25,616 matched

    WHAT THIS ENABLES

    Dynamics 365 to Google Offline Conversions

    Google Offline Conversions for Dynamics 365: Signals reconciles closed-won revenue to the Google Ads click through GCLID straight from your Dynamics 365 opportunities and process flows, hashed and consent-screened as records change.

    • Signals reconciles closed-won revenue to the Google Ads click through GCLID, reading your Dynamics 365 opportunities and process flows as records change.
    • A clean line from click to closed revenue, with no export step out of your Dynamics 365 opportunities and process flows.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google M CRM record sync recorded in Microsoft Dyn… 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 Dynamics 365 opportunities and business process flows.

    Enterprise RevOps teams on Dynamics 365 who need Smart Bidding trained on booked revenue instead of a mid-funnel proxy out of Dynamics 365 opportunities and process flows.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Dynamics 365, reading only your Dynamics 365 opportunities and process flows, mapped to Google Ads' Offline Conversion Import (Google Ads API) and tuned for GCLID coverage.

    2. Map

      Columns from your Dynamics 365 opportunities and process flows align to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed as the sync runs and checked for GCLID coverage.

    3. Deliver

      As records change, Signals reads your Dynamics 365 opportunities and process flows and reconciles closed-won revenue to the Google Ads click through GCLID, sends only the records that changed, 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 Microsoft Dynamics records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: dynamics.google-oci :: wire

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

    Adjacent moves on the same stack.

    from Microsoft Dynamics

    Dynamics 365 to Google Store Sales

    Google Store Sales for Dynamics 365: Signals matches in-person transactions to Google…

    Learn more

    from Microsoft Dynamics

    Dynamics 365 to Meta Offline CAPI

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

    You set the cadence, from near-real-time to a nightly Dynamics 365 sync of your Dynamics 365 opportunities and process flows into Google Ads. Since Signals sends only the records that changed, Smart Bidding trained on booked revenue instead of a mid-funnel proxy keeps pace and enterprise RevOps teams on Dynamics 365 watch GCLID coverage. One scoped connection sets it up, cadence adjustable later.

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

    Match rate follows identifier coverage in your Dynamics 365 opportunities and process flows, which enterprise RevOps teams on Dynamics 365 control, not Dynamics 365 itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Offline Conversion Import (Google Ads API) pinpoints GCLID coverage, the number enterprise RevOps teams on Dynamics 365 tune against.

    NEXT STEP

    Dynamics 365 to Google OCI, in production this week.

    Talk to our team All Microsoft Dynamics use cases