Drag and Drop Question You manage the Dynamics 365 Customer Insights applications at a cosmetics retail firm. Your marketing team wants to be able to branch contacts in a journey to receive a…

Question

Exhibit

Answer Area

Explanation

Explanation: D365 Customer Insights – Journey Branch on Spend Data

The Core Problem

The spend data lives in Customer Insights - Data (not Dataverse). To use it in a journey branch without touching standard tables, you must: wire Customer Insights customers to Dataverse Contacts → calculate a per-customer spend total → expose it in a way the journey engine can consume.

Step 1 - Create a relationship between the CustomerInsights.CustomerId table and the Contact table

Why first: This is the prerequisite that bridges the two systems. The unified Customer Insights profile (identified by CustomerInsights.CustomerId) must be explicitly linked to the Dataverse Contact entity before any measure output can be surfaced to a journey. Without this relationship, the journey engine has no way to match a calculated value back to an individual contact.

Why not "CustomerSpendTrailing12 → Customer table" instead? That distractor links an ingested source table to the unified profile, which is handled during the data unification/mapping phase - not a manual relationship step here. The journey needs a path from the unified profile all the way to the Dataverse Contact, which is what this step establishes.

Step 2 - Create a measure with the dimension CustomerInsights.CustomerId that sums CustomerSpendTrailing12.Amount

Why second: With the relationship in place, you can now define the calculation. The measure:

• Dimension = CustomerInsights.CustomerId - groups the result per customer (one row per person)
• Aggregation = SUM(CustomerSpendTrailing12.Amount) - adds up all transactions for that customer

Common mistake - the wrong measure option: The distractor says "sums CustomerInsights.CustomerId" - this would sum the ID field (meaningless numeric/GUID aggregation) rather than the Amount field. The dimension and the aggregation target are different things; confusing them is the classic trap here.

Step 3 - Set the Measure type to Customer and Table, and run the measure

Why last: The measure type controls how the output is stored and exposed:

"Customer and Table" is required because the journey branching engine needs to query the output table to evaluate the condition per contact. Running the measure executes the aggregation and populates that table.

Why not "Business level"? A Business-level measure produces one value for the entire organization (e.g., total company revenue). There is no per-customer breakdown - you cannot branch individual contacts on a value that applies to everyone equally.

Summary of Eliminated Distractors

No community discussion yet for this question.