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

    CONNECTIONS / Microsoft Dynamics / Dynamics 365 to Snap Offline CAPI

    Dynamics 365 opportunities and process flows into Snapchat, built for Snapchat in-store conversions.

    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 reports in-store purchases against the Snapchat campaigns that reached the buyer so Snapchat sees offline conversions without an export.

    Talk to our team Explore the setup

    dynamics -> snap-offline-capi :: live

    1. ● dynamics 365 → snap.capi :: live
    2. > read closed_deals rows=47,265
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 39,703 matched

    WHAT THIS ENABLES

    Dynamics 365 to Snapchat Offline CAPI

    Snapchat Offline CAPI for Dynamics 365: Signals reports in-store purchases against the Snapchat campaigns that reached the buyer straight from your Dynamics 365 opportunities and process flows, hashed and consent-screened as records change.

    • Signals reports in-store purchases against the Snapchat campaigns that reached the buyer, reading your Dynamics 365 opportunities and process flows as records change.
    • In-person conversions Snapchat can bid on, 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 Snap, away from any pixel. Here is how Microsoft Dynamics closes the loop.

    Snap credits the campaign that sourced the conversion conversion happens off-platform Ad click on Snap M CRM record sync recorded in Microsoft Dyn… S Signals hash · dedupe Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Retail and QSR advertisers whose Snapchat audience buys in person, working out of Dynamics 365 opportunities and business process flows.

    Enterprise RevOps teams on Dynamics 365 who need physical-world sales counted inside Snapchat performance 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 Snapchat's Conversions API and tuned for offline event timing.

    2. Map

      Columns from your Dynamics 365 opportunities and process flows align to Snapchat's Conversions API in the visual mapper, hashed as the sync runs and checked for offline event timing.

    3. Deliver

      As records change, Signals reads your Dynamics 365 opportunities and process flows and reports in-store purchases against the Snapchat campaigns that reached the buyer, sends only the records that changed, with offline event timing 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 Offline CAPI 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 Offline CAPI actually receives.

    signals :: dynamics.snap-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /v2/conversion source=dynamics.closed_deals
    3. event_type "PURCHASE" · event_conversion_type "OFFLINE"
    4. hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
    5. timestamp 1784139814 · price 36676 · currency GBP
    6. ✓ accepted · match=true
    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 Google Store Sales

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

    Learn more

    same use case

    ActiveCampaign to Snap Offline CAPI

    ActiveCampaign to Snapchat Offline CAPI: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    Snap Offline CAPI

    Deliver offline conversions to Snap on a schedule that fits your operations.

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Dynamics 365 Snap Offline CAPI 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 Snapchat. Since Signals sends only the records that changed, physical-world sales counted inside Snapchat performance keeps pace and enterprise RevOps teams on Dynamics 365 watch offline event timing. One scoped connection sets it up, cadence adjustable later.

    What match rate should a Dynamics 365-sourced Snap Offline CAPI 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 Snapchat; one missing both cannot. First-run feedback from Conversions API pinpoints offline event timing, the number enterprise RevOps teams on Dynamics 365 tune against.

    NEXT STEP

    Dynamics 365 to Snap Offline CAPI, in production this week.

    Talk to our team All Microsoft Dynamics use cases