Dynamics 365 Campaign Management: What Campaigns Actually Track

What follows is each entity in turn, the numbers they carry, the maintenance each one asks for, and the two honest ways to get real spend and real revenue onto the same row.

Dynamics ships two things with campaign in the name, and choosing wrongly is the most common early mistake. The difference is how many activity types you need and whether the sends are spread over time.

In practice: a quick campaign is a one-off send to a list you just built, and its results are a log rather than a funnel. A campaign is the record you keep for a quarter, and it is the only one of the two that can carry responses into the pipeline.

Four money and forecast columns do most of the reporting work, and knowing which is calculated and which is typed tells you exactly how much to trust the campaign dashboard.

• Budget Allocatedbudgetedcost. What you planned to spend. Typed in by the campaign owner and never reconciled against anything.
• Total Cost of Campaigntotalactualcost. The one people read as actual spend. It is built from the costs entered on the campaign and its activities, not from an ad account, so it is only as current as the last person who updated it.
• Total Cost of Campaign Activitiestotalcampaignactivityactualcost. The rolled-up cost of the activities underneath, which is why an activity with no cost on it silently understates the campaign.
• Expected Revenue and Expected Response Percentageexpectedrevenue and expectedresponse. A forecast, typed at planning time. Useful for a plan, and not to be confused with what the campaign produced.

A campaign activity is how a campaign reaches people. Each one distributes exactly one type of activity to the marketing lists attached to it, and the documented list of types tells you what era the entity was designed in: phone call, appointment, letter, letter via mail merge, fax, fax via mail merge, email and email via mail merge.

There is no ad platform in that list, and there never was. A campaign activity cannot represent a Google search campaign, a Meta ad set or a LinkedIn sponsored post, which is why the paid half of a modern marketing budget has no natural home in the entity. Teams work around it by creating a campaign per channel and typing the spend in monthly, which works exactly as long as somebody keeps doing it.

• Static marketing lists

  A fixed set of accounts, contacts or leads, one record type per list. Distribute to accounts and leads and you need two lists.

• Dynamic marketing lists

  A saved query, evaluated when it is used. Better for anything ongoing, and the usual answer to lists going stale between sends.

• Distribution

  A campaign activity is distributed with DistributeCampaignActivityRequest; a quick campaign uses PropagateByExpressionRequest or CreateActivitiesListRequest. Worth knowing when you automate any of this.

The campaign response is the single entity that carries a campaign into the pipeline. It records a reply, and from it you can create a lead, an opportunity, a quote or an order, which is what puts a campaign name next to money.

It is also the piece that breaks first, because a campaign response is created by hand or converted from an existing activity. Nothing writes one when somebody clicks a Meta ad, reads two pages and comes back a week later on a brand search. At ad volume, the manual work is not merely tedious, it is not attempted, and the campaign ends the quarter with a cost, a forecast and no responses at all.

• A response needs somebody to create it, or an integration that creates it for you. Decide which on day one.
• Converting the response is what links the money, because the lead or opportunity it creates carries the campaign with it.
• An opportunity created any other way has no campaign, and no report can invent one later.
• Responses are per campaign, not per touch. Even a well kept campaign credits one campaign per record, so a journey across three channels is recorded as one.

None of this is a criticism of the entity. It does what a campaign container should do. The honest list of what it does not do is what decides whether you need anything else.

1. It does not connect to an ad account. Spend is typed, so cost per lead and ROAS are as accurate as your last manual update.
2. It does not see a web session. Dynamics 365 Sales records no visits, referrers or campaign parameters, so a click never becomes a response on its own.
3. It credits one campaign per record. There is no multi-touch model in Sales, so the campaign that closed takes everything and the one that opened the journey takes nothing.
4. It does not send anything back. A won opportunity does not become a conversion in Microsoft Advertising, Google Ads, Meta or LinkedIn, so the platforms never learn which clicks produced revenue.
5. The marketing app is a separate licence. Customer Insights - Journeys runs the journeys, forms and lead scoring, and its outbound module was removed from every environment in May 2026, so reporting built on the old data model had to be rebuilt in Microsoft Fabric.

Two patterns work, and they can be combined. The first costs discipline, the second costs a subscription.

Whichever you choose, keep the campaign record. It is still the right place to hold a plan, a budget and a list. What it should stop being is the place you look for the answer to which marketing produced the revenue, because that answer has to be measured somewhere the ad clicks are visible.

LeadJourney is one script on your site or in your GTM container, live in about 21 minutes without a developer. It records every visit server-side on your own domain at 95%+ accuracy, captures msclkid, gclid, fbclid and li_fat_id at click time, and joins the anonymous first click to the person when they submit a form, book a meeting or call.

The Microsoft Dynamics integration then writes the observed channel, campaign, ad and landing page onto the Lead, the Account and the Opportunity in Dataverse, and reads stages and revenue back over a webhook. Spend comes straight from Microsoft, Google, Meta and LinkedIn Ads, so cost per won opportunity is calculated from the two numbers rather than typed into Total Cost of Campaign. When an opportunity is closed as won, the amount goes back to the platform that produced the click, matched on the click ID captured at the first visit.

What it does not do is run your campaigns. Sends, journeys, forms and lead scoring stay where they are, in Customer Insights - Journeys or whichever tool you use, and a lead that never touched your website still needs a source typed in by a human.

Keep going with Dynamics 365 lead source tracking, what Customer Insights attribution measures and the attribution tools built for Dynamics. On the product side, the Microsoft Dynamics integration, the ad campaign report and offline conversion tracking.