Data Cloud Unification Challenges in Marketing Cloud Next

Data reconciliation constraints in Marketing Cloud Next segmentation

Moving to Marketing Cloud Next (MC Next) gets complicated as soon as you wire core Salesforce CRM data into Journey Builder segmentation.

The first wall you hit is Segment-Triggered Flows, which require the Unified Individual Data Model Object (DMO).

The unified profile against the Lead inquiry data model

One business can generate several Lead records, each carrying its own Email Address or Mobile Number for that particular inquiry. What you want is for journey communications to use the contact point on the specific Lead that triggered the segment, even after that contact point has been harmonized into a Unified Profile.

Data Cloud unification runs reconciliation rules to pick the authoritative contact points for the Unified Individual profile, and each rule has a failure mode:

1. Last Updated can send the campaign to an outdated or wrong email or mobile, because a different Lead record was touched more recently.
2. Most Frequent breaks when an individual has several Leads and the one you care about uses a secondary contact point, so the flow may pick the wrong email address.
3. By Source is barely deterministic once several Lead records exist, so the chosen contact point is unpredictable.

Where Activation Templates and the Individual DMO fall short

Activation Templates let you define the Contact Point Email Address for the Unified Profile, but they inherit the same reconciliation constraints. Nothing in the template tells the segment to use the contact point on the source record that qualified the individual in the first place.

The Spring '26 release lets you use the Individual DMO in segment flows, but you cannot use Data Graphs at the same time. Data Graphs are what keep complex personalization logic manageable and pre-define the field sets the journey uses for decisioning.

Workaround: force a 1:1 mapping

To keep the right contact points and keep Data Graphs, the current workaround forces a 1:1 mapping between the CRM ID and the Unified Individual DMO.

It works like this:

1. Configure reconciliation rules to enforce a 1:1 match on the CRM ID.
2. That sidesteps the cross-record reconciliation logic for contact points.
3. Build the segments on that 1:1 mapping.
4. Apply Ranking and Limiting by hand where several leads still land on the same 'unified' individual by other means. It is tedious, and you maintain it per segment.

Because the mapping is explicit, the Data Graph references the right DMO and the right contact points.

You are working against what Data Cloud unification is for, which is centralized identity resolution. It does keep segmentation stable while you wait for the platform to catch up.