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

    CONNECTIONS / Microsoft Dynamics / Dynamics 365 to Google Store Sales

    Dynamics 365 opportunities and process flows into Google Ads, built for Google Store Sales matching.

    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 matches in-person transactions to Google accounts as store-sales conversions so Google Ads sees offline conversions without an export.

    Talk to our team Explore the setup

    dynamics -> google-store-sales :: live

    1. ● dynamics 365 → google.sales :: live
    2. > read closed_deals rows=33,925
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 29,854 matched

    WHAT THIS ENABLES

    Dynamics 365 to Google Store Sales

    Google Store Sales for Dynamics 365: Signals matches in-person transactions to Google accounts as store-sales conversions straight from your Dynamics 365 opportunities and process flows, hashed and consent-screened as records change.

    • Signals matches in-person transactions to Google accounts as store-sales conversions, reading your Dynamics 365 opportunities and process flows as records change.
    • Store visits reconciled to campaign spend, 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 Store Sales Direct API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Omnichannel retailers reconciling point-of-sale against Google spend, working out of Dynamics 365 opportunities and business process flows.

    Enterprise RevOps teams on Dynamics 365 who need counter and showroom revenue inside the same ROAS view as online orders 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' Store Sales Direct API and tuned for the store-sales match rate.

    2. Map

      Columns from your Dynamics 365 opportunities and process flows align to Google Ads' Store Sales Direct API in the visual mapper, hashed as the sync runs and checked for the store-sales match rate.

    3. Deliver

      As records change, Signals reads your Dynamics 365 opportunities and process flows and matches in-person transactions to Google accounts as store-sales conversions, sends only the records that changed, with the store-sales match rate 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 Store Sales 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 Store Sales actually receives.

    signals :: dynamics.google-store-sales :: wire

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=dynamics.closed_deals
    3. transaction_time 2026-07-17T08:04:02 · transaction_amount_micros 42518000000
    4. currency_code GBP
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=88%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Microsoft Dynamics

    Dynamics 365 to Google OCI

    Google Offline Conversions for Dynamics 365: Signals reconciles closed-won revenue to the…

    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 Store Sales

    ActiveCampaign to Google Store Sales: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Google Store Sales

    Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Dynamics 365 Google Store Sales 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, counter and showroom revenue inside the same ROAS view as online orders keeps pace and enterprise RevOps teams on Dynamics 365 watch the store-sales match rate. One scoped connection sets it up, cadence adjustable later.

    What match rate should a Dynamics 365-sourced Google Store Sales 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 Store Sales Direct API pinpoints the store-sales match rate, the number enterprise RevOps teams on Dynamics 365 tune against.

    NEXT STEP

    Dynamics 365 to Google Store Sales, in production this week.

    Talk to our team All Microsoft Dynamics use cases