Customer Data and Journeys at a Regional Retailer
Lakeshore Outfitters is a regional outdoor retailer with 74 stores, an e-commerce site, and a loyalty program with 1.2 million members. Customer data sits in the point-of-sale system, the e-commerce platform, a legacy email tool, and a loyalty database. The same person can appear as three different records with different email addresses and consent flags. Marketing sends batch campaigns to one 600,000-person list; average open rate is 11% and unsubscribe rate is 0.9%. The company wants to segment by purchase history and store proximity, trigger journeys such as a post-purchase care series and a win-back series, and honor consent by channel. It has no data warehouse and two marketing operations staff. Leaders ask whether Dynamics 365 Customer Insights can replace the email tool and loyalty database, and how the two Customer Insights offerings differ.
1. Distinguish the two Customer Insights offerings and explain which one addresses unification and which addresses orchestration.
Read the worked answer
Customer Insights - Data is the unification and insight layer. It ingests data from the point-of-sale system, e-commerce platform, loyalty database, and other sources; matches records to create a unified customer profile; and supports segments, measures, and predictions. In this scenario it is the answer to three records with different emails and consent flags, because identity resolution and unification are its core purpose.
Customer Insights - Journeys is the orchestration layer. It builds segments, journeys, emails, and consent-aware triggers, and it executes the post-purchase and win-back sequences. It is the successor to the marketing application, so the retailer should treat it as the campaign and journey tool rather than as a second database.
The two are designed to work together: Data produces the unified profile and segments, and Journeys uses them to target and trigger. The retailer does not have to choose one forever, but the sequencing matters. Starting with Journeys before unification would automate the same fragmented records and worsen the consent problem. Starting with Data establishes a trustworthy profile, then Journeys can act on it.
A critical distinction: neither offering is a replacement for the point-of-sale or loyalty transaction system. They consume that data; they do not run the store.
2. Which capabilities address the low open rate, the consent problem, and the two-person operations team?
Read the worked answer
Segmentation and purchase history address the 11% open rate. Instead of one 600,000-person batch, the retailer can build segments from unified profiles - recent buyers of a product category, customers near a store, lapsed customers with a previous purchase - and send relevant content. Relevance is the mechanism, not a better subject line.
Consent and preference management address the 0.9% unsubscribe rate and the conflicting consent flags. Journeys should respect channel-level consent and suppression lists, and the unified profile should carry the authoritative consent state. The retailer must decide which source wins when flags conflict; that is a business rule, not a technical default.
Triggered journeys address the post-purchase and win-back use cases. A purchase event can start a care series; a period without purchase can start a win-back series. Triggers replace calendar-based batch sends and reduce irrelevant contact.
For a two-person team, the priority is to limit scope. Use standard templates, a small number of high-value journeys, and built-in analytics rather than custom development. The team should not attempt a full data warehouse or a dozen personas in the first release. A focused first wave - one post-purchase journey and one win-back journey - is more likely to succeed and produces evidence for the next wave.
3. What should the retailer not expect Customer Insights to replace, and what business value is realistic?
Read the worked answer
Customer Insights should not replace the point-of-sale system, the e-commerce transaction engine, or the loyalty ledger. Those systems authorize transactions, calculate points, and hold the financial record. Customer Insights consumes their data to build profiles and segments; it is not the system of record for sales or loyalty balances. It is also not a full data warehouse or a general-purpose BI platform, although it can expose measures and segments for analysis.
Realistic value includes higher engagement from relevant segments, lower unsubscribe rates from consent-aware contact, and more repeat purchases from triggered journeys. The retailer should also expect better customer understanding: unified profiles reveal overlap between store and online behavior that the current reports cannot show.
The value depends on data quality and operating discipline. If the two-person team cannot maintain the data connections and consent rules, the unified profile decays. If journeys are launched without a measurement plan, the retailer will see activity but not impact. Measures should include open and click rates by segment, unsubscribe rate, conversion after journey, repeat purchase rate, and profile match rate. The match rate is an early indicator of whether unification is working.