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

    CONNECTIONS / Microsoft Dynamics / Dynamics 365 to LinkedIn Offline CAPI

    Dynamics 365 opportunities and process flows into LinkedIn, built for LinkedIn account-revenue reporting.

    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 closed B2B deals so LinkedIn optimizes on account revenue so LinkedIn sees offline conversions without an export.

    Talk to our team Explore the setup

    dynamics -> linkedin-offline-capi :: live

    1. ● dynamics 365 → linkedin.capi :: live
    2. > read closed_deals rows=9,602
    3. hash sha256(email,phone) consent=filtered
    4. route linkedin deliver
    5. ✓ delivered · 8,258 matched

    WHAT THIS ENABLES

    Dynamics 365 to LinkedIn Offline CAPI

    LinkedIn Offline CAPI for Dynamics 365: Signals reports closed B2B deals so LinkedIn optimizes on account revenue straight from your Dynamics 365 opportunities and process flows, hashed and consent-screened as records change.

    • Signals reports closed B2B deals so LinkedIn optimizes on account revenue, reading your Dynamics 365 opportunities and process flows as records change.
    • Account revenue attached to the sourcing campaign, 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 LinkedIn, away from any pixel. Here is how Microsoft Dynamics closes the loop.

    LinkedIn credits the campaign that sourced the conversion conversion happens off-platform Ad click on LinkedIn 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.

    B2B teams whose deals close long after the impression, working out of Dynamics 365 opportunities and business process flows.

    Enterprise RevOps teams on Dynamics 365 who need pipeline revenue tied to the LinkedIn campaigns that sourced it 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 LinkedIn's Conversions API and tuned for long B2B attribution windows.

    2. Map

      Columns from your Dynamics 365 opportunities and process flows align to LinkedIn's Conversions API in the visual mapper, hashed as the sync runs and checked for long B2B attribution windows.

    3. Deliver

      As records change, Signals reads your Dynamics 365 opportunities and process flows and reports closed B2B deals so LinkedIn optimizes on account revenue, sends only the records that changed, with long B2B attribution windows 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.linkedin-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /conversionEvents source=dynamics.closed_deals
    3. conversion "urn:lla:llaPartnerConversion:89212"
    4. conversionHappenedAt 1784083212000
    5. user.userIds [{ idType: "SHA256_EMAIL", idValue: "9c41af…" }]
    6. ✓ accepted · conversionValue 35401 USD
    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 LinkedIn Offline CAPI

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

    Learn more

    generic

    LinkedIn Offline CAPI

    Datahash routes offline outcomes, like closed deals from your CRM, to LinkedIn with hashed…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Dynamics 365 LinkedIn 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 LinkedIn. Since Signals sends only the records that changed, pipeline revenue tied to the LinkedIn campaigns that sourced it keeps pace and enterprise RevOps teams on Dynamics 365 watch long B2B attribution windows. One scoped connection sets it up, cadence adjustable later.

    What match rate should a Dynamics 365-sourced LinkedIn 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 LinkedIn; one missing both cannot. First-run feedback from Conversions API pinpoints long B2B attribution windows, the number enterprise RevOps teams on Dynamics 365 tune against.

    NEXT STEP

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

    Talk to our team All Microsoft Dynamics use cases