Customer Insights – Journeys explained

Customer Insights – Journeys is Microsoft's marketing automation application — the successor to Dynamics 365 Marketing. It orchestrates multi-channel customer journeys, runs email campaigns and events, scores and qualifies leads, and hands them to Dynamics 365 Sales. It runs on Dataverse and shares the same Account, Contact, and Lead tables as the other Dynamics 365 CRM apps — which is the whole point. Marketing doesn't sync to the CRM; marketing is in the CRM.

Two names cause endless confusion, so let's settle them first. Customer Insights – Journeys is the marketing automation app (journeys, email, events). Customer Insights – Data is a separate customer data platform (profile unification, measures, predictions) covered in its own guide. Microsoft sells them together under the single "Dynamics 365 Customer Insights" licence, but they are distinct products that install and work independently. The renaming history from Dynamics 365 Marketing to today's naming is untangled in the marketing history and transition guide.

Journeys: the core concept

A customer journey is a multi-step path a contact or lead travels through over time. Each step is a trigger, a wait, a branch, or an action — send an email, send an SMS or push notification, create a task, fire a Power Automate flow, update a record. Journeys come in two starting shapes:

Segment-based journeys start a defined audience down the path together — the classic campaign send, a monthly newsletter, a product launch sequence.

Trigger-based journeys start one person at a time, the moment something happens: a form submission, an event registration, an abandoned cart signal, a custom event your own systems raise through the API. This is where marketing automation earns its name — a welcome sequence that starts the second someone signs up, a renewal journey that fires ninety days before a contract date.

Branching is where journeys get interesting: split by attribute (send enterprise customers a different track), by behaviour (opened the last email or didn't), or by A/B test results with automatic winner selection.

Real-time replaced outbound

The product carries scar tissue worth understanding. The original Dynamics 365 Marketing shipped an outbound model — batch-oriented, list-based, slower. Microsoft rebuilt the engine as real-time marketing, ran the two side by side for years, and has since retired outbound; new environments are real-time only. If you find older blog posts describing customer journeys with tiles on a horizontal canvas, that's the dead outbound designer. The differences, and what a migration involves, are covered in real-time vs outbound journeys.

Practical consequence: ignore any consultant proposal or tutorial that doesn't say which model it's describing. If it's outbound, it's history.

Segments

A segment is a dynamic, query-defined audience — "customers in Sweden with at least one purchase in the last 90 days and an open opportunity". Segments are built on Dataverse attributes and behavioural signals, refresh as data changes, and journeys targeting a segment automatically pick up new entrants. The query builder is genuinely capable and genuinely fiddly; the segment builder guide covers the mechanics, and segmentation deep dive covers the design thinking.

Email, forms, and personalisation

The email designer is block-based with reusable content blocks, conditional content per recipient attribute, and A/B testing. Personalisation goes well beyond "Hi {first name}" — dynamic text can traverse Dataverse relationships, so an email can reference the recipient's account owner's name or the products on their latest order. The token syntax has real depth and real sharp edges; see personalization tokens.

Hosted forms capture inbound leads and registrations, mapping fields to Lead or Contact records with duplicate handling. Getting mail delivered at volume is its own discipline — DKIM, SPF, DMARC, dedicated sending domains, warm-up, and list hygiene — covered in email deliverability for Customer Insights – Journeys.

Consent is first-class

Real-time journeys enforce consent centrally: consent records per email address or phone number, per purpose (commercial, transactional), with topics for granular subscription management. A send simply will not go out to a contact without the right consent — the platform checks at send time, not at segment time. For European organisations living under GDPR this is one of the strongest arguments for the product, and it's also the part most often mis-designed on day one. Decide your purposes and topics before the first campaign, not after.

Events and lead scoring

Built-in event management covers in-person and webinar events: sessions, speakers, registration pages, capacity, waitlists, and Teams integration for virtual delivery. Registration and attendance flow back as journey triggers — attend the webinar, get the follow-up track; register and no-show, get the recording. Details in event management and event orchestration.

Lead scoring models combine demographic fit and behavioural engagement, and qualified leads route to sales queues automatically. Because Sales and Journeys share the same Lead table, the marketing-to-sales handoff is a stage change, not an integration project — the single strongest architectural argument for the product. Lead scoring with AI Builder covers building a custom scoring model rather than relying on the built-in one. Post-event and post-purchase feedback typically flows in through Customer Voice surveys, with Customer Voice integration covering how survey triggers and responses tie back to journeys and Customer Service.

Copilot

Generative AI shows up in three useful places: content generation (subject lines, email body drafts, image suggestions), query assist (describe a segment in natural language, get the query), and journey suggestions. Treat it like a competent junior — good first drafts, always reviewed. The broader AI story across the family is in Copilot across Dynamics 365.

Licensing

Microsoft licenses Customer Insights per tenant, not per user: a base licence covers both Journeys and Data, with capacity measured in interacted people for Journeys (roughly: the people you actually engaged in the period) and unified profiles for Data. Additional capacity packs stack on top. The model rewards clean data — a bloated contact list of people you never contact costs storage, but the metered dimension is who you engage. Check current tiers on Microsoft's pricing page before budgeting; the numbers move.

Where it stops

Honest limits. High-volume B2C at the scale of tens of millions of daily sends is the territory of dedicated platforms like Braze or Salesforce Marketing Cloud. Deep content operations (DAM, brand portals, editorial workflow) need a separate system. Programmatic advertising isn't in the product. And organisations without any other Dynamics 365 or Power Platform footprint lose the product's main advantage — the shared data platform — and should weigh HubSpot-class alternatives seriously. This is exactly the gap Dynamics 365 for media and entertainment runs into: audience engagement fits Journeys well, but rights management and programmatic ad sales still need specialised systems alongside it.

Where it wins: any organisation already running Dynamics 365 Sales or Customer Service, where "marketing sees what sales sees" stops being an integration roadmap and starts being the default.

Where to go next

Orientation: real-time vs outbound, then the segment builder. Building: journey orchestration tips collects the field lessons. Architecture: real-time marketing data integration covers feeding external signals in. And if your problem is fragmented customer data rather than campaign execution, start with Customer Insights – Data instead.