There is a common learning curve for teams adopting Salesforce Data 36O. You spend time configuring a highly targeted segment, initiate your activation to Marketing Cloud, and inspect the resulting payload. But you might notice something unexpected: by default, the system outputs the user’s newly reconciled Gmail address, even though their older Yahoo address was the specific source record that met your segment criteria.
Predictably, the immediate reaction for those used to legacy marketing platforms is to ask: Is the segmentation engine working correctly?
The answer is a resounding yes. While legacy systems might leave you stuck with the “wrong” email, Data 36O provides sophisticated tools to handle exactly this scenario. What feels like a discrepancy is actually the gateway to a powerful paradigm shift in how we handle customer data. This behavior stems from the sophisticated way Data 36O’s Identity Resolution (IR) handles the Unified Individual Data Model Object (DMO) versus the standard Individual DMO.
Rather than being a limitation, this architecture opens doors marketers simply didn’t have before. Let’s look under the hood of Data 36O’s data architecture, define exactly when to query each object, and explore how to leverage activation filters to achieve unprecedented precision in your campaigns.
The Unified Link: Decoupling Qualification from Reconciliation
To understand why Data 36O behaves this way—and why it is such a massive advantage—we have to look at the Identity Resolution data model.
Traditional Master Data Management (MDM) platforms and legacy ESPs typically execute destructive merges to yield a single, surviving “golden record.” If a customer changed their email, the old history was often lost or overwritten. Data36O utilizes a non-destructive relational model. If five disparate source profiles exist across your CRM, data lakes, and marketing applications, all five persist natively in the Individual DMO.
Instead of overwriting data, Data36O generates a “key ring” via the Unified Link table. It maps these multiple Individual IDs to a single Unified Individual ID, establishing a many-to-one relationship.
Here is how the query logic works: When you build a segment against the Unified Individual DMO, the engine evaluates the entire key ring. For example, imagine your segment criteria is looking for users who engaged with a specific win-back campaign (e.g., Email Engagement = 'Opened' AND Campaign = 'Win-Back 2025'). The engine asks: Does any associated Individual record meet this criteria? If the old Yahoo profile is the one that registered the email open, the parent Unified Individual is successfully flagged for inclusion.
Strategic Application: Segmenting on theIndividual DMO
Because the Unified Individual is so powerful, many practitioners make the mistake of defaulting to it for every single segment. However, Data 36O gives you the flexibility to query the raw source data directly by segmenting on the Individual DMO, bypassing Identity Resolution entirely when the use case demands it.
When to leverage the Individual DMO:
- Precise B2B Lifecycle Targeting (Account & Contact): Imagine you are targeting users for an upcoming B2B contract renewal. A customer might exist in your system as a business Contact tied to a specific Salesforce CRM Account, but they also have a separate e-commerce profile tied to their personal email on the Unified profile. If you segment on the Unified Individual, you risk blending their B2B and B2C contexts. By segmenting directly on the Individual DMO (specifically querying the CRM Contact) and activating on that same Individual, you explicitly maintain the relationship to their Account data. This ensures the renewal payload pulls their precise business email and Account ID, ignoring their unified cross-platform history entirely.
Strategic Application: Segmenting on theUnified Individual DMO
The Unified Individual DMO is critical for aggregate analysis and cross-channel orchestration. You should leverage it when cross-platform data synthesis is your primary objective and deduplication is a strict requirement.
When to leverage the Unified Individual DMO:
- VIP Lifetime Value (LTV) & Cost-Heavy Campaigns: A retail brand wants to send a premium physical catalog to “VIPs” who have spent over $1,000 in the last year. A customer might have spent $400 via their loyalty app (Email A), $400 in-store (Phone B), and $300 on the e-commerce site (Email C). In a legacy system, these look like three separate people who do not meet the threshold. By leveraging a Calculated Insight (CI) tied to the Unified Individual DMO, Data36O calculates the total transactional history across the entire key ring. You can then build a segment targeting that unified CI metric (e.g.,
Unified Annual Spend > $1,000) to accurately qualify the user. The activation will then use your reconciliation rules to deduplicate the record, ensuring you only spend your budget mailing one catalog to their best unified address.
Deep Dive: Mastering Precision with Activation Filters
What happens when you want the best of both worlds? You need the aggregate behavioral data of the Unified Individual to qualify the segment, but your campaign requires you to activate the specific source ID that qualified (e.g., you need to send the email to the old Yahoo address that submitted a specific form, not the reconciled new Gmail).
In legacy systems, you were often stuck with whatever the platform deemed the “primary” email. In Data 360, you have the agency to surgically select your payload using Activation Filters.
Here is the technical mechanism to achieve this precision routing:
- The Default State: During activation setup, you map the contact point (e.g., Email). Without intervention, Data 360 sorts all
Contact Point Emailrecords tied to the Unified Individual based on your IR reconciliation rules and selects the “winner.” - Applying the Activation Filter: In the activation configuration screen, you have the ability to add filters directly to the Contact Point. You can explicitly re-apply your segmentation criteria here as an Activation Filter (e.g., setting the filter on the
Contact Point EmailDMO to match the specific form submission or source system of the old Yahoo address). - The Precision Override: By filtering the
Contact Point EmailDMO at the point of activation, you constrain the pool of eligible contact points. Data 360 seamlessly bypasses its default reconciliation logic because only the old Yahoo address satisfies this new, hyper-specific filter criteria. - The Output: The activation engine extracts the exact
Contact Point Email(Yahoo) and its correspondingPartyId(which becomes the Subscriber Key in Marketing Cloud), ensuring your Data Extension receives the precise identity you intended.
Applying criteria at the activation layer might feel like a new muscle to flex for those used to flat-file querying. But this is the exact architecture that empowers marketers to do things they never could before. You are no longer constrained by rigid, merged data files. You have a deeply relational, multi-source data model at your fingertips, giving you the power to pull any version of any person you could ever want—you just have to tell the system exactly how to find them.
Written by
