Dynamics 365 integration

Dynamics 365 lead source, set at submission.

Dynamics 365 has a Lead Source option set on every lead. It holds a single picked value. Capture the real source, landing page and full page journey instead, and let Zapier create the lead with the source already attached.

Track your Dynamics leads free → See the setup
Connects via the Dynamics 365 Zapier connector Creates or updates leads and contacts One line of code
What Dynamics captures, and what it misses

Dynamics has a Lead Source option set. It holds one option.

Microsoft Dynamics 365 gives the lead and opportunity tables a Lead Source option set. It is a single value chosen from a configured list, which fits a Microsoft-stack sales org that wants a clean dropdown for reporting. It is also why the field tells you the channel and nothing about the campaign, the entry page, or the path the buyer took to reach you.

What the option set holds

One configured option

  • A single option: Web, Trade show, Partner, Other
  • Set on creation, by a form map or a rep
  • Tidy for a dashboard, blunt for a spend review
What it leaves out

The detail behind the option

  • The campaign or search behind the click
  • The landing page they arrived on
  • The pages they read before submitting, ending on the page that converted them

Short version: Lead Source records the source, landing page and journey at submission, then hands the lead to Zapier so the Dynamics record carries the real story.

How the connection works

Captured on your site. Written into Dynamics through Zapier.

Dynamics 365 has a live Zapier connector covering Dynamics v9 and Dynamics 365. It is a Zapier Premium app, which suits the enterprise context it usually lives in.

  1. 01
    Lead Source logs the real source, campaign, landing page and full page journey from the first visit.
  2. 02
    When the form is submitted, Lead Source logs the lead in your dashboard and routes it to Zapier.
  3. 03
    Your Zap runs the Dynamics Create Lead or Update Lead action (or Create Contact for a contact-led model). You map the captured source into the fields the action exposes.
  4. 04
    The lead lands in Dynamics with the source set at submission, before it routes to a seller.
The captured record

What lands in Dynamics 365.

Sample data, not a real customer. The shape of the lead created when a form is submitted and the Zap fires.

SAMPLE · captured lead → Dynamics lead at submission
Dynamics lead created
Sarah Donnelly
Procurement · Meridian Manufacturing
Lead SourceOrganic Bing
searchindustrial coatings
landed/industrial-coatings
journey/industrial-coatings → /case-studies → /quote
tableLead
Real source on the lead before it routes.
Safe setup pattern

From snippet to record, in three steps.

Only the verified Dynamics Zapier actions, mapped into the lead they create.

01

Place the snippet on your site

Add the Lead Source script before the closing </head> on any page with a form. It logs the source, landing page and journey for every visitor.

02

Connect Lead Source to Dynamics in Zapier

Create a Zap with Lead Source as the trigger and the Dynamics Create Lead action as the step. The Dynamics connector is a Zapier Premium app, so a paid Zapier plan is needed.

03

Map the source onto the lead

Map the captured source into the Lead Source option set or a text field, with the campaign and landing page alongside. Send a test submission with a UTM and confirm the lead arrives with the real source.

Integration details verified against the Microsoft Dynamics 365 Zapier connector on 30 June 2026. We confirmed the Create Lead, Update Lead, Create Contact and Update Contact actions exist and that the connector is a Zapier Premium app for Dynamics v9 and Dynamics 365. We did not verify writes to arbitrary custom fields on standard records.

When this isn’t the right fit

When Dynamics isn’t the right fit yet.

A few cases where this setup is the wrong choice, no spin.

  • You are on a free Zapier plan. The Dynamics connector is a Premium app, so this needs a paid Zapier tier.
  • Your org runs lead capture through native Dynamics Marketing or Power Automate flows you would rather not duplicate. Map the path that owns the record.
  • You need the source written to a specific bespoke custom field. We map into the fields the connector exposes; arbitrary custom-field writes are not verified.
Related

Where to go next.

CRM lead source tracking
The pillar guide. How lead source works in every CRM
CRM source, compared
How each CRM captures source, side by side
Salesforce
Lead source in Salesforce, a direct integration
Lead source examples
What a captured record looks like, channel by channel
Common questions

Questions, answered.

Does Dynamics 365 already track lead source?

Yes. Dynamics 365 gives the lead and opportunity tables a Lead Source option set. It is a single value chosen from a configured list, so it records the channel only. Lead Source fills it through Zapier with the real source captured at form submission, along with the campaign and landing page.

Do I need a paid Zapier plan to connect Dynamics 365?

Yes. The Microsoft Dynamics 365 connector is a Zapier Premium app, so a paid Zapier plan is required to use it in a Zap.

Which Dynamics versions does the connector cover?

The Zapier connector covers Dynamics v9 and Dynamics 365. Its Create Lead, Update Lead, Create Contact, and Update Contact actions are the ones we map the captured source into.

See your real Dynamics 365 lead sources.

Free to start. Connect Dynamics 365 through Zapier in minutes.

Track your Dynamics leads free &rarr;

Free to start &middot; no card