Dynamics 365 Lead Source Tracking: UTMs, Campaigns and the Real Source

What follows is the detail: which table holds what, the five failure modes in the order they bite, how far UTM tracking gets you, and an audit that tells you in an afternoon how bad your own data is.

Dynamics ships three places to record where something came from, and most reporting arguments come from mixing them up. They answer different questions, they are filled in at different moments, and all three are filled in by hand.

• Lead Source on the LeadThe leadsourcecode choice column. Its shipped options are Advertisement, Employee Referral, External Referral, Partner, Public Relations, Seminar, Trade Show, Web, Word of Mouth and Other. One value, chosen once, and Web covers every digital channel you buy.
• The Campaign recordA container for planning tasks, campaign activities, marketing lists and responses. It carries Budget Allocated, Total Cost of Campaign, Expected Revenue and Expected Response Percentage, all typed in by the person who owns the campaign.
• The Campaign ResponseA reply to a campaign activity, created manually or converted from an activity, which can then become a Lead, an Opportunity, a Quote or an Order. It is the link between a campaign and the pipeline, and nothing creates one automatically from an ad click.

There is a chain behind every source value, and in a standard Dynamics 365 Sales environment most of it is missing. Knowing which links exist turns a vague complaint about bad data into something you can check this afternoon.

• The website

  Dynamics 365 Sales has no script on your site. It records no sessions, no referrers and no campaign parameters, because it was never a web analytics product. Whatever reaches Dataverse arrives through a form, an import or an integration.

• The form

  A Customer Insights - Journeys form, or a third-party form connected through form capture, maps each field to a Dataverse column. A hidden field carrying a UTM value is the usual way a campaign name ever reaches the Lead.

• The Journeys cookie

  Customer Insights - Journeys web tracking writes its cookie carrying the form submission id at the moment a form is submitted. The identity starts at the form, which is why the click that brought the person there a week earlier is not in it.

• The person creating the record

  A seller typing a lead in, an import from a list, an integration posting through the API. Each of those picks a Lead Source value, or leaves it empty, and that is the source your report is made of.

Put that chain next to the question the board asks, which is which campaign produced the revenue, and the mismatch is obvious. Dynamics is precise about the opportunity and silent about the marketing that produced it, because the marketing half of the chain was never collected.

In the order they bite, from the one that affects every environment to the one that only shows up when you start reporting on revenue.

1. Web is one option for every digital channel. Paid search, paid social, organic, email, referral and AI search all collapse into it. The chart is technically correct and answers nothing.
2. Nobody fills it in consistently. Two sellers, two habits. One picks Web for an inbound demo request, one picks Advertisement, one leaves it blank. The option set is not required unless somebody made it required.
3. The campaign is on the Campaign record, not on the Lead. Even a well maintained campaign with a real budget in Total Cost of Campaign is only joined to pipeline when somebody creates a Campaign Response and converts it, which is manual work nobody does at ad-click volume.
4. The first touch is lost the moment a form is involved. A hidden UTM field records the page the visitor happened to submit on. The LinkedIn ad that started the journey three weeks earlier left no trace, so the last touch is credited and the channel that opened the deal is invisible.
5. Calls, chats and imported lists have no session at all. The lead exists, the revenue is real, and there is nothing to attribute it to, so it lands in Other or in nothing.

UTM tracking in Dynamics is not one feature, it is a pattern people build. It works, within limits, and the limits are worth knowing before you spend a sprint on it.

The usual build has three parts. You tag every ad destination with utm_source, utm_medium and utm_campaign. You add hidden fields to the form for each parameter, either on a Customer Insights - Journeys form or on your own form connected through form capture, and map each one to a custom column on the Lead. Then you build a view or a Power BI report that groups by those columns instead of by Lead Source.

• What it gets rightA lead who clicks an ad and submits the form on that same visit arrives with the campaign name on the record, in columns you own, without touching leadsourcecode. For a short buying cycle with one landing page, that is most of the job.
• What it cannot seeThe visit before the visit. A returning visitor arrives with no parameters in the URL, so the hidden fields are empty or, worse, overwrite a good value with a blank. Organic, direct and AI search visits carry no UTMs at all by definition.
• What breaks itA redirect that drops the query string, a form on a second domain, a new form built without the fields, a consent banner that blocks the script before the fields are filled, and any lead that arrives by phone or import.

There is also a maintenance cost people underestimate. Every new form, every new landing page and every agency handover is another place the hidden fields have to exist. The build is never finished, and the day it silently breaks looks exactly like a slow month.

Before buying anything, measure the gap. Four numbers, all available from views you can build in Dynamics today, and each one tells you something different.

1. The Web share. Leads created in the last 90 days, grouped by Lead Source. The percentage sitting in Web is the share of your pipeline whose channel you cannot name.
2. The blank share. The same view, filtered to Lead Source empty. This is the number that decides whether you have a tooling problem or a process problem.
3. The campaign join rate. Opportunities closed as won in the last year that have a Campaign Response, or any campaign, associated at all. In most environments this is close to zero, and it is why cost per won opportunity cannot be calculated.
4. The click ID share. If you already capture msclkid or gclid in a custom column, count the won opportunities that still have a value in it. That is the ceiling on what you could send back to the ad platforms today.

Take those four numbers into the budget meeting instead of an opinion. A Web share of 70% and a campaign join rate of 2% is not a reporting preference, it is the reason nobody can say what the last quarter's spend produced.

There are three levels of ambition here and they stack: the second assumes the first works, the third assumes both. Pick the one that matches how much revenue depends on the answer.

The honest summary: the first level is free and incomplete, the second cheap and fragile, the third costs a subscription and closes most of the gap. If you spend five figures a month and cannot name the campaigns behind the won opportunities, the arithmetic decides for you.

LeadJourney is one script on your site or in your GTM container, live in about 21 minutes without a developer. It runs server-side on your own domain at 95%+ tracking accuracy, so Safari, iOS and ad blockers take far less out of the data. At the first visit it captures msclkid, gclid with gbraid and wbraid, fbclid and li_fat_id, plus the UTMs and the landing page. That anonymous first click is joined to the person at the form fill, call or booking, so the March ad is still attached in September.

The Microsoft Dynamics integration runs both ways over Dataverse. It reads your lead statuses, opportunity stages and revenue, and writes the first touch, campaign, click ID and full journey onto the Lead, the Account and the Opportunity as columns of their own, so leadsourcecode stays exactly as your routing rules expect it. You then map any stage you choose, qualified, proposal sent or closed as won, to a conversion action: Microsoft Ads as offline conversions matched on msclkid, Google Ads as an offline conversion import matched on the gclid, Meta over the Conversions API, LinkedIn over its Conversions API, with the amount and currency travelling with the event. Attribution models switch between first click, last click, linear, time decay and position based without re-tracking.

The limits are worth saying out loud. Tracking is first-party and respects consent decisions rather than working around them, so a visitor who declines is not measured, and a lead that never touched your site still needs a source typed in by a human. Call tracking closes the phone gap, but numbers are billed per number plus usage on top of the plan, which starts at €129 a month by marketing spend, hosted in Frankfurt under a GDPR data processing agreement.

Read verified reviews on Trustpilot, G2 and leadjourney.io/testimonials.

Keep going with what Dynamics 365 campaign management actually tracks, what Customer Insights attribution measures and the attribution tools built for Dynamics. On the technical side, see the GCLID guide and our UTM parameters explainer. On the product side, the Microsoft Dynamics integration, fixing the lead source in your CRM and the lead source glossary entry.