[object Object]

A marketing manager asks where to build their next campaign and gets two answers from two consultants: Journeys for the orchestration, Data for the segmentation. Both are right and the platform splits them on purpose. The rebrand looks like marketing reshuffling; underneath, it is a real architectural separation that changes how teams work.

The Rebrand

Dynamics 365 Marketing split into two: Customer Insights: Journeys (real-time marketing journeys, email, segmentation) and Customer Insights: Data (CDP — unified profile, identity resolution, segmentation on Dataverse plus external data). The split lets each side evolve independently and lets organizations license what they need rather than the bundled marketing SKU.

Journeys: outreach, journeys, email, SMS, push
Data: profile unification, segmentation, scoring, identity

Most teams need both. A few teams that already have a CDP only need Journeys; a few teams that send through other channels only need Data.

Journeys

Triggered real-time journeys: customer events trigger next action. Email, SMS, push, in-app. Lower latency than outbound marketing’s scheduled sends. The trigger model takes an event from the Customer Insights data layer or a Dataverse row change and fires the journey within seconds, not minutes.

Trigger sources:
- Customer Insights segment entry or exit
- Behavioral event (web visit, click, app event)
- Dataverse row update (lead score change, opportunity stage)
- Custom event from external source via event grid

The behavioral event source is what finally makes cart-abandonment work the way the demos always promised.

Data

The CDP side — unified profiles across D365, Azure, external sources. Segments built here activate to Journeys or other destinations. The unification step is the hard part; identity resolution across email, phone, and customer ID requires deliberate match rules and a deduplication strategy.

Match hierarchy:
1. Exact match on customer_id (highest confidence)
2. Exact match on email + last_name
3. Fuzzy match on email + last_name + zip
4. Manual review for fuzzy matches below 0.85

Skip the match rule design step and the unified profile contains duplicates that look like separate customers to every downstream system.

Sync to Sales

Marketing-qualified leads flow to Sales. Scoring handoff: set a score threshold; above it, lead converts. Simple, works. The score lives on the lead and updates as behavior accumulates; the conversion is a Power Automate flow that watches for the threshold and creates the opportunity.

async function checkLeadScore(leadId) {
  const lead = await fetch(`/api/data/v9.2/leads(${leadId})?$select=msdyn_leadscore`).then(r => r.json());
  if (lead.msdyn_leadscore >= 75) {
    await convertLeadToOpportunity(leadId);
  }
}

Tune the threshold quarterly based on the conversion rate from MQL to closed-won. A threshold that lets too many leads through buries Sales; a threshold that lets too few through wastes Marketing’s pipeline.

AI Segmentation

Natural-language segment creation: customers who bought X in the last 90 days and have not opened our last three emails. Useful for marketers without SQL fluency. The natural language interpreter generates the underlying segment definition and the marketer reviews before saving.

Prompt: customers in California who bought a premium product in the last quarter
Generated: segment with conditions on state, purchase_amount, product_tier, purchase_date

The review step is essential. The interpreter sometimes picks the wrong field when two fields have similar names; a quick review catches it.

Real-Time vs Outbound Trade-Off

Real-time journeys are the future of the platform but outbound journeys still ship in 2026. The difference matters for some scenarios: outbound supports A/B at the journey level with statistical sign-off, real-time supports A/B at the message level. For a launch campaign, outbound is still the cleaner experience. For ongoing nurture, real-time wins.

Both products honor the consent model on the contact. A contact who opts out of marketing emails will not receive a Journey send, even if they enter the segment. Document the consent fields and confirm the integration with your global privacy preferences before going live.

What to do this week

Audit your current marketing setup, decide whether you need Journeys, Data, or both, and pick one campaign to rebuild on the real-time journey pattern. Tune the MQL score threshold based on last quarter’s conversion data and document the match rules for the unified profile.

[object Object]
Share