Dynamics 365 Customer Insights Implementation
Real-time journeys, unified customer profiles, segmentation and consent management for marketing teams on Dynamics 365, by senior consultants with 8+ years of delivery.
Solzet implements Microsoft Dynamics 365 Customer Insights for marketing teams that want automation in the same data model as sales and service. Our senior consultants configure Customer Insights - Journeys for real-time journeys, emails, forms, segments and consent, and Customer Insights - Data for unified customer profiles built from several sources. We connect marketing to Dynamics 365 Sales so qualified leads reach sellers with their full history, migrate teams from the retired outbound marketing features, and fix journeys where contacts get stuck. Licensed but unused? We get a minimum viable setup live in about three weeks. When Microsoft licensing is the wrong match, we build custom CRM; we connect marketing to Business Central or Finance and Operations order data.
What is Dynamics 365 Customer Insights?
Customer Insights is the Dynamics 365 marketing and customer data application, which replaced the product previously sold as Dynamics 365 Marketing. It has two parts that can be licensed and implemented together or separately.
- Customer Insights - Journeys: real-time, event-triggered customer journeys, email and SMS messages, marketing forms, segments, lead scoring and consent management.
- Customer Insights - Data: a customer data platform that unifies profiles from Dataverse and external sources, resolves identities and calculates measures and segments you can act on.
Journeys or Data: which do you need?
Many mid-market teams start with Journeys, because their customer data already lives in Dynamics 365 Sales and Customer Service. Data becomes worth adding when customer information is spread across several systems that need to be unified before marketing can act on it.
| Your situation | Start with | Why |
|---|---|---|
| Customer data mostly in Dynamics 365 already | Journeys | Segments and journeys can run directly on Dataverse contacts, leads and accounts. |
| Customer data spread across e-commerce, support and other systems | Data, then Journeys | Profiles need unifying and identities resolving before journeys target the right person. |
| Moving from the retired outbound marketing features | Journeys | Real-time journeys are the supported path forward, and the migration needs planning for emails, segments and forms. |
| Marketing must hand qualified leads to sellers | Journeys with Dynamics 365 Sales | Lead scoring and hand-off rules route leads to sellers with their full engagement history. |
Bought Customer Insights and nobody uses it: how do you get it live in about three weeks?
Customer Insights usually ends up as shelfware for the same reason: the project was scoped as a full marketing transformation, with every data source, every journey and a lead scoring model, and stalled before anything was sent. The licence renews while sales keeps asking marketing for the same three lists. The fix is to cut the scope to something that produces a result sales can see within weeks, and add the rest once the first journey is running.
The minimum viable scope is deliberately small. One profile source: for most teams already on Dynamics 365 Sales that is the Dataverse contacts and accounts sales already maintains, so Customer Insights - Data and external sources can wait. The top three to five segments sales actually asks for, built in the real-time segment builder. One journey that matters, such as a follow-up for new leads or a re-engagement email to dormant accounts. One compliance profile with the consent and subscription settings that journey needs. If the contact data is too messy to segment, start with the cleanup described in our guide to segmentation and data quality on a 40,000-contact list.
Who should do the fast start?
| Option | Works when | Watch out for |
|---|---|---|
| Internal sprint | Someone in-house already knows Customer Insights - Journeys, consent configuration and the Dataverse data model, and has the time. | The sprint competing with day jobs, and consent settings learned by trial and error on live contacts. |
| Marketplace freelancer | The scope is one clearly defined task, such as building a form or a single email template. | Nobody owning domain authentication, consent design and data quality together, and no cover once the contract ends. |
| Short expert engagement | You need the whole minimum viable setup working in weeks, with the configuration documented so marketing can run it afterwards. | Scope creep: keep it to the agreed segments and one journey, and add the rest as a second phase. |
- Week 1: confirm the environment, sending domain authentication and compliance profile; agree the segments with sales in writing; check the contact data behind them and fix the fields the segments depend on.
- Week 2: build and test the segments, compare member counts against what sales expects, build the first journey and its emails, and test it end to end with internal contacts.
- Week 3: go live with the first journey, watch journey analytics daily for entrants that stop progressing, hand marketing a short runbook, and agree the next two journeys.
- Manual stopgap while it is built: give sales the agreed segments as saved views in Dynamics 365 Sales from week 1, and if a send cannot wait, send a single email to a static segment under the correct compliance profile so the licence earns something immediately.
What a short Solzet engagement covers
Our senior consultants run the three weeks above: environment and sending domain checks, consent and compliance profile, the agreed segments, the first journey, testing, go live and a runbook for your marketing team. When journeys later stop progressing, our guide to contacts stuck in Customer Insights journeys explains the usual causes and the fix order.
How do we handle consent and compliance?
Consent is designed before the first email is sent. We configure compliance profiles, subscription centres and purpose-based consent so contact preferences are recorded once and respected by every journey. For organizations trading into the EU we align the setup with GDPR requirements, including double opt-in where appropriate and clear records of when and how consent was given.
What if years of legacy contacts have no reliable consent record?
Treat every contact whose consent you cannot prove as suppressed by default, then rebuild a defensible list rather than emailing it and hoping. In Customer Insights - Journeys consent is not a single yes or no on the contact: it is held in contact point consent records, one per contact point (a specific email address or phone number) and channel, each with a purpose such as commercial or transactional communication and, optionally, a topic within that purpose, governed by a compliance profile. A legacy list with no provenance cannot populate those records honestly, so it cannot be treated as opted in. This is technical guidance, not legal advice: involve your DPO and legal adviser before any decision about the list.
Terminology, default behaviours and enforcement options in the consent model change between releases, so confirm the current behaviour of purposes, topics and compliance profiles against Microsoft documentation for your version before designing around it. What matters for a legacy list is the consequence: consent is recorded against the email address or phone number, not against a vaguely remembered person, so a contact with three addresses needs three answers, and a commercial opt-in says nothing about a topic the person never chose.
How the consent model maps onto a legacy list you cannot prove
| Consent element | What it records | What it means for unproven legacy contacts |
|---|---|---|
| Contact point | The specific email address or phone number the consent applies to, per channel. | Consent inferred for one address cannot be copied to another address for the same person. |
| Purpose | Why you contact the person, for example commercial marketing as opposed to transactional messages about something they bought or booked. | Being a customer may support transactional messages; it does not prove commercial marketing consent. |
| Topic | A narrower subject within a purpose, such as one newsletter or product line. | Only set topic consent where you can show the person chose that topic. |
| Compliance profile | Which purposes and topics apply, how they are enforced and which preference centre people use. | Choose enforcement that requires a recorded opt-in for commercial messages to EU contacts, as your DPO advises. |
- Suppress by default: mark every contact point without provable consent as not opted in for commercial purposes, so no journey or segment can reach it by accident, while keeping the record for service and legal obligations your DPO confirms.
- Run a documented re-permission campaign only through a channel your legal adviser confirms is lawful. In several jurisdictions an email asking for marketing consent is itself marketing, so options may be limited to logged-in account preferences, the next service or transactional interaction, or existing-customer rules where they genuinely apply.
- Record consent provenance as data, not as a note: source, timestamp, the exact consent wording and its version, and the capture point (form, preference centre, import, call) stored in fields on or alongside the consent record, so any single opt-in can be evidenced.
- Keep an auditable trail of every suppression decision: which contacts were suppressed, by which rule, on what date, approved by whom, and which were later re-permissioned. Our Dynamics 365 audit trail guide covers keeping change history you can export.
- Separate erasure and retention from consent: a suppressed contact still has to be deleted when retention expires or an erasure request arrives, which is covered in our guide to GDPR retention, erasure and DSAR in Dynamics 365.
Can identity resolution in Customer Insights - Data merge different people into one profile?
Yes, when match rules are too loose. Customer Insights - Data unifies source records into one customer profile using the deduplication and match rules you configure. Rules that match on name alone, on a shared household or company address, or on generic email addresses such as info@ or a shared family inbox will combine different people. The unified profile then carries one person's purchases, consent and preferences onto another, which is a privacy exposure in its own right: marketing can reach someone on the strength of another person's opt-in, and a subject access request or erasure can return or delete the wrong person's data.
Tighten the rules before trusting consent on unified profiles. Match on stable identifiers first (customer numbers, verified email addresses), add fuzzy name matching only in combination with another strong attribute, normalise data before matching, and exclude known generic and shared addresses from matching. Then review the result rather than the rule: sample merged profiles, look at the unification output for records combined from many sources, and check high-risk merges by hand before journeys use them. Re-run unification after rule changes and compare profile counts with the previous run. Cleaning duplicates at source in Dataverse is covered in our duplicate data cleanup guide.
Why do contacts get stuck in journeys, and how do we fix it?
Journeys that stop progressing are the most common issue we are asked to investigate: contacts waiting on a condition that can never be met, triggers that never fire, or consent and segment settings that silently exclude people. Our guide to contacts stuck in Customer Insights journeys walks through the causes. We audit the journey design, correct it in a test environment and put monitoring in place so the problem is noticed in hours rather than weeks.
What if our migration from outbound marketing to real-time journeys already broke our segments?
Start with triage, because a campaign is usually days away. Inventory every segment the migration touched, rank each one by the revenue or obligation that depends on it (the renewal campaign, the event invitation, the regulated notice), and stabilise only the top few before rebuilding anything: freeze a known-good audience as a static list or a list-based segment, built from records you have checked by hand or exported from wherever membership was last right, and point the urgent journey at that. It is not elegant, and the list will not update itself, but it lets the campaign go out to the right people while the real cause is found. Everything below the top few can wait for a proper rebuild.
Microsoft has been retiring outbound marketing in favour of real-time journeys, and the migration tooling, what can be carried over and the timelines have changed several times, so check current Microsoft documentation for your version before relying on any specific behaviour described here. In the migrations we are asked to repair, broken segments almost always come from three causes, set out below. If contacts do enter the journey but then stall, that is a different problem, covered in our guide to contacts stuck in Customer Insights journeys.
The three usual causes of segments that broke in the migration, and who can fix them:
| Cause | What you see | Fix a marketer can usually run | When it genuinely needs a developer |
|---|---|---|---|
| Segment definitions do not mean the same thing in both models | A rebuilt segment returns far more, far fewer or different people than the old one, or a segment that used email opens, clicks or website visits returns nobody. | Rebuild in the real-time segment builder and compare counts and a sample of members against the old segment. Check whether the segment targets contacts or leads, re-check relationship paths, date conditions and and-or grouping, and replace conditions on old outbound interaction history with real-time interactions or a static list of those people. | The logic depends on data that is not in Dataverse, needs a calculated or rollup value that does not exist yet, or history from outbound interactions has to be brought across into fields the new segments can query. |
| Contact and lead identity and consent handling changed | Members appear in the segment but emails are skipped as not consented, duplicates receive messages twice, or leads that used to be reached are ignored. | Check which compliance profile the message uses and how it enforces consent, inspect contact point consent records for a sample of skipped people, confirm the purpose and topic the message is sent under, and choose deliberately whether a journey targets contacts or leads. | Consent held in the old subscription lists and contact fields has to be converted into contact point consent at volume, or duplicate contacts and leads have to be merged with rules and history preserved. |
| Website interaction and form triggers stopped firing | Journeys that started on a form submission or a website visit have no new entrants since the cutover, while the site still shows the old form. | Recreate the form as a real-time form, publish it, and use the out-of-the-box form submitted trigger in the journey. Where the site editor allows embedding snippets, replace the old outbound form embed with the new one and submit a test entry end to end. | The trigger is a custom website or application event, the form is embedded in a site you cannot edit without a code release, or an integration, plugin or flow still writes to or reads from the outbound marketing tables. |
- Segment inventory: for each segment record its name, which journeys and emails use it, the audience type, the date it last produced a trustworthy count, and the campaign or obligation that depends on it. The ranking comes from that last column, not from how complex the segment is.
- Stabilise the top few: build the static audience, get the owner of the campaign to sign off a sample of members, and write down the date it was frozen so nobody mistakes it for a live segment later.
- Compare before trusting: for every rebuilt segment, check the member count and a hand-picked sample, including people who should be excluded, against the last known-good result before switching a journey over.
- Test consent end to end: send a test message under the real compliance profile to internal contact points you have opted in and out, and confirm the skipped and delivered results match what you expect.
- Test triggers end to end: submit every migrated form and fire every trigger once from outside the organisation, then confirm a new journey entrant appears. Do the same after each website release.
- Retire deliberately: switch journeys off the static lists one at a time as rebuilt segments pass comparison, and only then remove leftover outbound assets.
How does Customer Insights connect to sales and service?
Because Customer Insights runs on Dataverse, marketing, Dynamics 365 Sales and Customer Service can share one customer record. We configure lead scoring and hand-off rules so sellers receive qualified leads with the full engagement history, and service interactions can trigger journeys such as follow-ups after a case is resolved. If Microsoft licensing is beyond your marketing budget, we can build campaign and segmentation features into a custom CRM instead. Where purchase history sits in Business Central or Finance and Operations, our CRM and ERP integration work brings it into the same customer record. If marketing runs on HubSpot today, our guide to Customer Insights vs HubSpot Marketing alongside Dynamics 365 Sales covers when to keep it, when to consolidate, and how to stop the sync creating duplicates.
Where can you go deeper?
Contacts stuck in Customer Insights journeys
The causes behind journeys that stop progressing and how to fix them without losing campaign history.
Customer Insights vs HubSpot Marketing, and fixing the sync
When to keep HubSpot alongside Dynamics 365 Sales and when to consolidate on Customer Insights - Journeys, and how to gate a HubSpot sync that creates duplicates.
What do buyers ask us?
What is the difference between Customer Insights - Journeys and Customer Insights - Data?
Journeys is the marketing automation part: real-time journeys, emails, forms, segments, lead scoring and consent. Data is the customer data platform: it unifies customer profiles from several sources, resolves identities and calculates measures and segments. Teams whose customer data already lives in Dynamics 365 often start with Journeys; teams with data spread across many systems usually need Data as well.
Is Dynamics 365 Marketing the same as Customer Insights?
Customer Insights is the current name for Microsoft's marketing and customer data offering, which replaced the product previously sold as Dynamics 365 Marketing. Real-time journeys in Customer Insights - Journeys are the supported path for marketing automation going forward.
Can you migrate us from outbound marketing to real-time journeys?
Yes. We inventory your existing emails, segments, forms and journeys, rebuild what is still needed as real-time journeys, plan the consent and subscription changes, and run both in parallel for a controlled period so no campaign is interrupted. If the migration has already happened and segments broke on the way over, we start with triage: inventory the segments, rank them by revenue impact and stabilise the top few with static lists, then trace the cause, usually segment definitions that behave differently in real-time journeys, consent and identity handling, or form and website triggers that stopped firing. Microsoft has been retiring outbound marketing, so check current Microsoft documentation for the tooling and timelines that apply to you.
Why do our segments return different people after migrating to Customer Insights - Journeys?
Because segments in real-time journeys are built differently from outbound marketing segments. The usual differences are whether the segment targets contacts or leads, relationship paths and and-or grouping that were rebuilt slightly differently, date conditions, and conditions on old outbound email or website interaction history that real-time segments cannot see. Compare member counts and a sample of members against the last known-good result before switching any journey over, and use a static list for urgent campaigns meanwhile.
Which migration fixes can a marketer make without a developer?
Most of them: rebuilding segments in the real-time segment builder and comparing counts, freezing an urgent audience as a static list, checking the compliance profile, purpose and topic a message is sent under, recreating forms as real-time forms with the form submitted trigger, and testing every form and journey end to end. A developer is genuinely needed for custom website or application triggers, bulk conversion of old consent data, duplicate merges at volume, forms on sites that need a code release, and integrations still using outbound marketing tables.
Why did our form and website triggers stop starting journeys after the migration?
Usually because the website still embeds the old outbound marketing form or tracking, which real-time journeys do not listen to. Recreate the form as a real-time form, publish it, replace the embed on the site and use the form submitted trigger, then submit a test entry and confirm a new journey entrant appears. Triggers based on custom website or application events need a developer. Check current Microsoft documentation for the exact trigger options in your version.
Where can we find help implementing Dynamics 365 Customer Insights we already pay for?
Look for a Dynamics 365 consultancy that will scope a minimum viable setup rather than a full transformation: one profile source, the few segments sales asks for, one journey and the consent settings it needs, live in about three weeks and documented for your marketing team. Solzet runs exactly that kind of short engagement, then adds journeys and data sources as a second phase.
What is the minimum viable setup for Customer Insights - Journeys?
An authenticated sending domain, one compliance profile with the consent and subscription settings you need, the Dataverse contacts sales already maintains as the profile source, three to five segments agreed with sales, and one journey tested end to end. Customer Insights - Data, external sources and lead scoring can follow once that first journey runs.
Why are contacts stuck in our Customer Insights journey?
The usual causes are conditions a contact can never satisfy, triggers that do not fire because the underlying event is not being raised, and consent or segment settings that exclude people without an obvious error. We audit the journey, reproduce the problem in a test environment, fix the design and add monitoring so it does not recur silently.
How is consent modelled in Dynamics 365 Customer Insights - Journeys?
Consent is stored as contact point consent records rather than a single field on the contact: one per email address or phone number and channel, with a purpose such as commercial or transactional messaging, an optional topic, and a compliance profile that decides how consent is enforced and which preference centre applies. Names and default behaviours change between releases, so check current Microsoft documentation for your version.
Can we email legacy contacts in Customer Insights when we have no record of their consent?
Not safely for commercial marketing. Treat contact points without provable consent as suppressed by default, keep a dated record of that decision, and rebuild permission only through a channel your DPO or legal adviser confirms is lawful, because in some jurisdictions a re-permission email is itself marketing. Record each new opt-in with its source, timestamp, wording version and capture point. This is technical guidance, not legal advice.
What happens if Customer Insights - Data merges two different people into one profile?
The unified profile mixes their data, so one person's consent, purchases and preferences can be applied to the other, and a subject access or erasure request can return or remove the wrong person's data. It usually comes from loose match rules on names, shared addresses or generic emails. Tighten rules around stable identifiers, exclude shared addresses, review merged profiles and involve your DPO if wrongly merged data was used.
Does Customer Insights work with Dynamics 365 Sales?
Yes. Both run on Dataverse, so marketing and sales share the same contacts, leads and accounts. We configure lead scoring and hand-off rules so qualified leads reach sellers with their engagement history, and sales activity can feed back into segments and journeys.
What if Microsoft marketing licensing does not fit our budget?
Then Microsoft licensing may not be the right answer for your marketing. For teams that need segmentation, campaigns and consent tracking without Microsoft licensing, we can build those capabilities into a custom CRM that you own.
Which related services fit alongside this?
Custom CRM Development
Custom CRM development on React, Node.js, PostgreSQL and .NET for companies that need CRM without Microsoft licensing. Full ownership, no per-user fees.
Dynamics 365 Sales Implementation & Consulting
Dynamics 365 Sales implementation: lead-to-opportunity process, pipeline and forecasting, quotes, Outlook and Teams integration, and migration from other CRMs.
Dynamics 365 Customer Service Implementation
Dynamics 365 Customer Service implementation: case management, routing, SLAs and entitlements, knowledge base, omnichannel chat and Copilot for support teams.
Ready to start?
Contact Solzet for a free consultation. A senior consultant replies within one business day with a recommendation: Dynamics 365 Customer Engagement, Business Central, Finance and Operations, Power Platform, or a custom-built CRM.