If you cannot connect a customer's online shopping behaviour with their in-store returns history, you are flying blind on who they really are and what they want. This chapter solves that problem by introducing Dynamics 365 Customer Insights, which is a Customer Data Platform (CDP) that acts as a central brain for all your customer information, stitching together scattered data to create a single, complete view of each person.
Jump to a section
A simple way to picture Introduction to Dynamics 365 Customer Insights
A head wedding planner is the person responsible for making sure every detail of a massive wedding comes together perfectly. They don't just show up on the day; they spend months gathering information from dozens of different sources. The couple tells them the venue and the guest list. The caterer sends a menu with dietary restrictions. The florist confirms the bouquet colours. The photographer sends their schedule. The band gives their set list. The hotel manager provides the room block numbers. Each of these bits of data lives in its own separate email, text, or paper form. The planner's biggest nightmare is having one version of the guest list in an email from the couple, a different version on a napkin from the caterer, and yet another version on a clipboard at the venue. One guest is listed as 'Sarah J. Smith' on the invitation list, 'Sara Smith' on the dietary requirements form, and 'Sarah Jane Smith' on the seating chart. The planner cannot confidently tell you who is actually coming or what they need. To solve this, the planner creates one single, master spreadsheet. They take every piece of data from every source and carefully match the guest profiles, finding that 'Sara Smith' is the same person as 'Sarah J. Smith'. They fill in missing phone numbers, standardise the address format, and create one single, golden record for each guest. Now, the planner can see that Sarah has a nut allergy, prefers chicken, and needs a chair near the dance floor, all from one place. This master spreadsheet is the Customer Data Platform (CDP) for the wedding. It unifies all fragmented data into a single, trusted, and powerful source of truth, allowing the planner to deliver perfect, personalised service to every single guest. Without it, the wedding would be a chaotic mess of missed connections and duplicate gifts.
Dynamics 365 Customer Insights is a specific type of software called a Customer Data Platform, or CDP. A CDP is a tool built to collect, organise, and make sense of customer data that comes from many different places. Think of it as a specialised data warehouse designed just for customer profiles.
Before CDPs existed, companies typically stored their customer information in multiple, separate systems. A sales team might use a Customer Relationship Management (CRM) system like Dynamics 365 Sales to track leads and deals. The marketing team might use a different tool, like a marketing automation platform, to send email campaigns. The customer service team would use a helpdesk system to manage support tickets. A company's website might run on a separate e-commerce platform that stores purchase history. Critically, a physical retail store might use a completely different point-of-sale (POS) system. Each of these systems knows a different piece of the customer's story, but none of them knows the full story. This is often called data silos.
Customer Insights solves the silo problem by connecting to all these different data sources. It uses connectors, which are pre-built bridges, to pull data from systems like Dynamics 365 Sales, Marketing, and Service, as well as external systems like your own databases, data lakes, or even Excel files. Once the data is pulled in, the real magic happens: unification.
Unification is the process of identifying that records from different systems actually refer to the same real-world person. For example, you might have a record from your website for 'john.doe@email.com' and a record from your loyalty programme for 'John Doe, 123 Main St'. Customer Insights uses matching rules to determine these are the same person. It then merges the data from both sources into a single, unified customer profile. This profile is also called a 360-degree view of the customer because it gives you a complete picture.
This unified profile contains all the information: \ - Contact details (name, address, phone, email) \ - Demographics (age, gender, location) \ - Transaction history (what they bought, when, for how much) \ - Interaction history (which emails they opened, which web pages they visited, which support calls they made) \ - Loyalty status and points \ - Marketing segmentation data \ - Predictions and insights generated by the system itself
Customer Insights doesn't just store this data; it actively enriches and analyses it. It can use built-in artificial intelligence (AI) to create predictive models. For example, the system can predict which customers are most likely to churn (stop doing business with you) or who is most likely to buy a specific new product. These predictions are added directly to the customer profile.
Finally, Customer Insights is an action platform. It doesn't just sit there holding data. It triggers actions in other systems. For instance, if a customer's unified profile shows they are a high-value customer who hasn't purchased in six months, Customer Insights can automatically create a segment of 'At-Risk VIP Customers' and send that segment to Dynamics 365 Marketing to trigger a special re-engagement email. It can also be used by salespeople in Dynamics 365 Sales, who will see a full, unified profile of a lead right inside their sales interface, allowing for a much more personalised conversation.
Connect Data Sources
First, you identify all the places where customer data lives, such as Dynamics 365 Sales, a marketing database, or an external Excel file. You then use built-in connectors in Customer Insights to establish a connection to each of these sources, scheduling regular refreshes.
Ingest and Transform Data
Customer Insights pulls the raw data from each source. You may then apply transformations, like standardising date formats or mapping a field called 'FullName' in one system to a field called 'Name' in another. This step prepares the data for matching.
Define Unification Rules
You define the rules that tell Customer Insights how to identify that two records from different sources represent the same real person. For example, you might say 'match if email addresses are identical' or 'match if last name and phone number are the same'. You can also set up fuzzy matching for near-perfect matches.
Run Unification Process
Customer Insights processes the entire dataset against your rules. It identifies which records are duplicates, matches them, and merges them into a single unified customer profile. This profile now contains data from all your sources.
Create Segments and Measures
With unified profiles ready, you build segments (e.g., 'Customers who bought a laptop in the last 6 months') and measures (e.g., 'Average revenue per customer'). These are the building blocks for business analysis and targeted campaigns.
An IT professional, often called a Functional Consultant or a Solution Architect, implements Dynamics 365 Customer Insights for a client. Let's say a medium-sized retailer called 'Northwind Traders' has two main systems: an old on-premises database for their loyalty programme and a modern Dynamics 365 Sales instance for their e-commerce website. The data does not match. The loyalty database calls customers 'Patrons' and uses internal IDs. Dynamics 365 Sales calls them 'Contacts' and uses email addresses as the primary identifier. Customers who buy in-store with cash and a loyalty card are invisible to the online system.
Here is the step-by-step process the IT professional would follow:
First, they perform a data discovery. They interview business stakeholders to understand what data exists, where it lives, and how it's structured. They document that the loyalty database has 50,000 'Patron' records and the Sales system has 20,000 'Contact' records.
Second, they design the data integration. They use the Customer Insights admin centre to configure two data sources. One connection points to the loyalty database using a secure connection. The other connection pulls data from Dynamics 365 Sales using the built-in connector. They schedule these data imports to run nightly.
Third, they define the unification rules. This is a critical IT task. They decide to use email address and last name as the primary matching criteria. They also configure a rule for 'fuzzy matching' to handle minor spelling differences (e.g., 'Jon' vs 'John'). They then run the unification process. The system identifies that 15,000 'Patrons' match exactly to 'Contacts', and a further 5,000 are fuzzy matches. The remaining 30,000 'Patrons' are unmatched and become new customer profiles.
Fourth, they create measures and segments. A 'measure' is a calculation, like 'Total Lifetime Value' or 'Average Order Value'. The consultant creates a measure that calculates the total spending of each unified customer across both the loyalty programme and the online store. They then create a segment called 'High-Value Inactive Customers' which filters for customers with a lifetime value over $500 who haven't made a purchase in the last 90 days.
Fifth, they set up output and action. The consultant configures the 'High-Value Inactive Customers' segment to be exported to Dynamics 365 Marketing. When the segment updates nightly, Marketing automatically sends a personalised email with a 15% discount code to everyone in that list. They also configure a relationship to the Sales system, so when a salesperson opens a contact record, they see a special 'Customer Insights' tab showing the unified profile, including the churn prediction score. The consultant then tests the whole flow in a sandbox environment before deploying to production.
For the MB-910, this topic (Objective 5.1) is a prime candidate for 'describe' and 'identify' style questions. You will not be asked to configure Customer Insights. The exam focuses on concepts, benefits, and distinguishing it from other Dynamics 365 apps.
Here is exactly what they test:
The definition of a Customer Data Platform (CDP) and its purpose. They will give you a scenario (e.g., 'A company has data in Sales, Service, and Marketing and wants a unified view') and ask which tool does this. The correct answer is almost always Dynamics 365 Customer Insights. A common trap is 'Dynamics 365 Sales' itself, but Sales is a CRM app, not a CDP. A CDP unifies data across apps.
The goal of unification. They ask: 'What is the primary benefit of using Customer Insights?' The correct answer revolves around creating a single, 360-degree view of the customer. Traps include 'improving data security' (which is a benefit but not the primary goal of unification) or 'building customised reports in Power BI' (Power BI is a separate tool for visualisation, not unification).
The concept of data silos. You will see a question like: 'What problem does a CDP solve?' The answer is breaking down data silos between different business applications.
Predictive insights. They may ask: 'What feature of Customer Insights can predict which customers are likely to churn?' The answer is AI or predictive models built into the platform. They want you to know that Customer Insights can generate insights, not just store data.
Outputs and actions. They might ask: 'After unifying data, how can Customer Insights use the data to drive action?' The correct answer is exporting segments to other Dynamics 365 apps like Marketing or Sales. A trap is saying 'it only stores the data'.
Key terms to memorise: \ - Customer Data Platform (CDP) \ - Unification \ - 360-degree view / Unified customer profile \ - Data silos \ - Connectors (for bringing data in) \ - Segments (for grouping customers) \ - Measures (for calculations) \ - Predictive models / AI insights (churn, product recommendation)
Trap pattern: The exam loves to confuse Customer Insights with Dynamics 365 Marketing (which does audience segmentation within its own universe) or Dynamics 365 Sales (which manages leads but does not unify data from other apps). Remember: Customer Insights is the horizontal platform that cross-references data from Sales, Marketing, Service, and external sources. If a question mentions bringing together data from multiple different systems, Customer Insights is always the answer.
A Customer Data Platform (CDP) like Dynamics 365 Customer Insights is designed to unify customer data from multiple sources into a single, complete profile.
The primary business value of Customer Insights is breaking down data silos to provide a 360-degree view of each customer.
Customer Insights uses AI to generate predictive insights, such as predicting customer churn or suggesting next-best actions.
Unified customer segments created in Customer Insights can be exported to other Dynamics 365 apps to drive personalised marketing and sales actions.
Customer Insights is distinct from Dynamics 365 Sales, Marketing, and Service; it integrates with them but is not a replacement for them.
Data unification in Customer Insights involves matching records (e.g., by email or name) and merging them into a single, deduplicated profile.
These come up on the exam all the time. Here's how to tell them apart.
Customer Data Platform (CDP)
Unifies data from multiple sources (Sales, Marketing, Service, external)
Focuses on creating a single, complete profile across the entire customer journey
Owns the data; it's a system of record for unified identity
Customer Relationship Management (CRM)
Primarily manages data within its own app (e.g., Sales manages leads)
Focuses on managing relationships and sales pipelines
Is a system of engagement for specific business processes
Dynamics 365 Customer Insights
Primary purpose is data unification and analytics
Generates segments based on unified data from many sources
Does not send email campaigns; it exports segments to other systems
Dynamics 365 Marketing
Primary purpose is executing marketing campaigns and customer journeys
Can create its own segments but only from its own data or imported lists
Is the system that actually sends emails, tracks opens, and manages subscriptions
Data Silos
Customer info is scattered across different departments and systems
Leads to inconsistent views, duplicate records, and poor customer experience
Employees see only a fragment of the customer's story
Unified Data
All customer info is merged into a single, golden record
Provides a consistent, complete view to every department
Enables personalised service based on full history
Mistake
Customer Insights is just a fancy database that stores customer names and addresses.
Correct
Customer Insights is a CDP that not only stores data but also unifies records from multiple sources, enriches them with AI-driven predictions, and triggers actions in other Dynamics 365 apps.
Beginners often underestimate the 'action' part. They see 'data platform' and think it is just a storage bucket, missing the active analysis and integration capabilities.
Mistake
Customer Insights is the same as Dynamics 365 Customer Service.
Correct
Customer Service is a specific app for managing support tickets. Customer Insights is a separate platform that pulls data from Customer Service and other apps to create a unified profile.
The names are similar ('Customer Insights' and 'Customer Service'), leading beginners to confuse their functions. Understanding that one is a data platform and the other is a service desk app is crucial.
Mistake
To use Customer Insights, you must have all your data already cleaned and perfectly matched.
Correct
Customer Insights is designed to handle messy, inconsistent data. It provides tools for matching and merging records (unification) to clean data as part of the process.
Beginners think a platform requires perfect input, not realising the platform's core value is solving the messiness. They assume data has to be perfect to be useful.
Mistake
Customer Insights can only work with data from other Microsoft Dynamics 365 apps.
Correct
Customer Insights can connect to a wide variety of external data sources, including custom databases (SQL), data lakes (Azure Data Lake), and flat files like Excel or CSV.
Exam questions often test the breadth of connectors. Beginners might mistakenly think it is a Microsoft-only tool, but its power is in connecting non-Microsoft systems.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Customer Insights is a CDP that brings together data from many sources to create unified profiles and segments. Marketing is a specific application that uses those segments (or its own) to run email campaigns and manage customer journeys.
No. Customer Insights provides a low-code interface where you configure data connections, set matching rules, and build segments using a visual interface, not code.
Yes. You can create a segment that filters customers by total spending, purchase frequency, or loyalty tier, giving you a clear view of your most valuable customers.
This is a common problem. You configure multiple matching rules, such as combining name with email address or phone number, to distinguish between different people with the same name.
Not always. Data refresh is typically scheduled (e.g., nightly) depending on your data sources and configuration. Real-time updates are possible but require specific setups.
It means having a single customer profile that contains all the information you have about them from every department (sales, marketing, service, web) in one place, so you have a complete picture of their relationship with your company.
You've finished Introduction to Dynamics 365 Customer Insights. Continue through the MB-910 study guide to build a complete picture of the exam.
Done with this chapter?