Study guide
9.1 Reconciliation Rules: Most Frequent, Source Priority & Last Updated
Salesforce Certified Data 360 Consultant formerly Data Cloud Consultant
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Solution Overview & Enterprise Value
1.1 Enterprise Customer 360 & Data Cloud Business Value 1.2 Architectural Foundation: Zero-Copy, Hyperforce, Lakehouse & Data Pipeline 1.3 Platform Terminology, Core Entities & Data Lifecycle Stages 1.4 Data 360's Foundational Role in Predictive & Generative AI
2 Chapter 2: Ethics, Privacy & Governance Fundamentals
2.1 Regulatory Compliance, Data Privacy & Ethics in Customer Data 2.2 Consent Management & Preference Enforcement in Data Cloud 2.3 Data Retention, Deletion, and Privacy Right-to-be-Forgotten (RTBF)
3 Chapter 3: Security, Permissions & Tenant Architecture
3.1 Standard Permission Sets, User Roles & Functional Access 3.2 Data Spaces Architecture, Resource Allocation & Tenant Isolation
4 Chapter 4: Administration, Monitoring & Lifecycle Management
4.1 Data Kits & Package Automation for Cross-Org Deployment 4.2 Auditing, Status Monitoring, Error Logs & Data Explorer 4.3 Sandboxes, Change Management & Metadata Deployment
5 Chapter 5: Ingestion Connectors & Source Integration
5.1 Standard Bundles & Salesforce CRM Connectors (Sales/Service/Marketing) 5.2 Cloud Storage (S3, GCS, Azure Blob) & Streaming Ingestion (Web/Mobile SDK, Ingestion API) 5.3 Zero-Copy Data Federation & Snowflake/BigQuery/Databricks Sharing
6 Chapter 6: Data Lake Objects (DLO) & Data Transformations
6.1 DLO Configuration, Primary Keys, Event Time & Data Stream Categories (Profile, Engagement, Other) 6.2 Streaming & Batch Data Transforms: Formula Fields, SQL Transforms & Data Prep Recipes
7 Chapter 7: Data Model Objects (DMO) & Canonical Harmonization
7.1 Customer 360 Canonical Data Model & Subject Areas 7.2 DLO-to-DMO Mapping Patterns, Cardinality & Custom DMO Design 7.3 Data Validation, Schema Maintenance & Field Mapping Best Practices
8 Chapter 8: Identity Resolution Architecture & Match Rules
8.1 Identity Resolution Concepts, Consolidation Rate & Graph Modeling 8.2 Match Rules & Match Criteria: Exact Match vs. Fuzzy Matching (Deterministic & Probabilistic) 8.3 Multi-Party Identification, Anonymous-to-Known Transitions & Contact Point Matching
9 Chapter 9: Reconciliation Rules & Unified Profile Governance
9.1 Reconciliation Rules: Most Frequent, Source Priority & Last Updated 9.2 Unified Profile Schema (Individual & Contact Points) & Resolution Troubleshooting
10 Chapter 10: Segment Architecture & Audience Design
10.1 Segmentation Canvas, Segment Types (Standard UI & Flow) & Query Processing 10.2 Direct vs. Related Attributes, Cardinality & 1:N Filtering Traps 10.3 Segment Schedule, Refresh Frequencies & Exclusion Logic 10.4 Segment Membership Analysis, Population Drift & Sizing Validation
11 Chapter 11: Calculated & Streaming Insights
11.1 Calculated Insights (CI) Architecture, SQL/Builder Syntax & Dimensions vs. Metrics 11.2 Streaming Insights (SI) Architecture, Windowing (Tumbling/Sliding) & Real-Time Signals 11.3 CI vs. SI Architectural Decision Matrix & Performance Optimization
12 Chapter 12: Data Enhancements, Sharing & Analysis
12.1 Referencing Data 360 Data from Other Systems: Enrichments, Related Lists, Data Graphs & APIs 12.2 Reports, Dashboards & Tableau Analysis on Data 360 Data 12.3 Applying Predictive & Generative AI Tooling to Customer Scenarios
13 Chapter 13: Activation Targets & Outbound Activation
13.1 Activation Targets: Marketing Cloud, External Platforms, Cloud Storage & Data Spaces 13.2 Activation Configuration: Audience Mapping, Related Attributes & Payload Optimization 13.3 Activation Schedules, Publishing Cadence & Incremental vs. Full Refresh 13.4 Activation Troubleshooting: Error Logs, Rejection Reasons & Delivery Failures
14 Chapter 14: Real-Time Data Actions & Flow Automation
14.1 Data Action Targets & Webhook/Platform Event Architecture 14.2 Data Cloud-Triggered Flows & Real-Time Business Orchestration 14.3 End-to-End Enterprise Scenario Walkthrough: Ingestion to Closed-Loop Action
9.1 Reconciliation Rules: Most Frequent, Source Priority & Last Updated
Key Takeaways Explain This Topic AI
Reconciliation rules govern attribute survivorship—deciding which specific attribute value wins (survives) on the Unified Individual profile when multiple source records merge into an identity cluster.
Match Rules and Reconciliation Rules perform distinct, decoupled functions: Match Rules govern clustering (which records link together to form the graph), while Reconciliation Rules govern attribute selection; modifying reconciliation rules never alters cluster membership, record counts, or the consolidation rate.
The three standard reconciliation methods in Salesforce Data Cloud are Last Updated (most recent timestamp wins; standard system default), Source Priority (hierarchical ranking of trusted systems), and Most Frequent (statistical mode across records).
Tie-breaking behavior is strictly deterministic across all methods: ties in Most Frequent rules and ties within the same priority tier in Source Priority rules are both resolved by the Last Updated timestamp.
In Source Priority reconciliation, Data Cloud automatically skips null or empty values in higher-ranked sources, falling back down the hierarchy to the next highest-priority source that contains a populated value rather than overwriting valid data with nulls.
Last updated: September 2026
Reconciliation Rules: Most Frequent, Source Priority & Last Updated
In Salesforce Data Cloud, the creation of a unified Customer 360 profile is executed through a two-stage Identity Resolution engine. First, Match Rules analyze disparate customer records across enterprise touchpoints, identify deterministic and probabilistic linkages, and cluster related records into an identity graph. Second, once a cluster of source records is established, the platform must construct a single, authoritative master record—the Unified Individual ( UnifiedIndividual__dlm ).
Because contributing source records frequently contain contradictory or divergent data—such as different spellings of a name, conflicting postal addresses, or competing mobile numbers—Data Cloud requires deterministic logic to decide which attribute value survives on the unified profile. This decision engine is governed by Reconciliation Rules (also known as survivorship rules).
The Dual Engines: Match Rules vs. Reconciliation Rules
A frequent source of confusion on the Salesforce Certified Data Cloud Consultant exam is conflating Match Rules with Reconciliation Rules. While they operate within the same Identity Resolution ruleset, their architectural responsibilities are completely separate and decoupled. ┌─────────────────────────────────────────────────────────────────────────┐
- │ STAGE 1: MATCH RULES ENGINE │
- │ Evaluates incoming source records and forms identity clusters. │
- │ Determines: "Do Record A (CRM), Record B (POS), and Record C (Web) │
- │ belong to the same living individual?" │
- │ Output: Identity Cluster Graph / Consolidation Rate │
- └────────────────────────────────────┬────────────────────────────────────┘
- │ Forms Cluster: [A + B + C]
- ▼
- ┌─────────────────────────────────────────────────────────────────────────┐
- │ STAGE 2: RECONCILIATION RULES ENGINE │
- │ Evaluates attribute values within each established cluster. │
- │ Determines: "Now that Records A, B, and C are clustered together, │
- │ which First Name, Mobile Phone, and Home Store should win?" │
- │ Output: Unified Individual Profile (Reconciled Field Values) │
- └─────────────────────────────────────────────────────────────────────────┘
- Architectural Comparison Matrix
- Architectural Dimension Match Rules Reconciliation Rules
- Primary Objective Identity clustering & record linkage Attribute survivorship & conflict resolution
Core Question Answered Who is this customer across systems? Which field value is most authoritative?
- Granularity Record-level & contact-point level Individual field-level on Unified DMOs
- Impact on Cluster Size Direct : Merges or splits clusters None : Has zero effect on cluster size
- Impact on Consolidation Rate Direct : Controls consolidation % Zero : Never alters consolidation %
Configuration Artifact Match Criteria (Exact, Fuzzy, Normalized) Rule Type (Last Updated, Source Priority, Most Frequent)
Evaluation Sequence Evaluated first (builds the graph) Evaluated second (populates cluster fields)
Important
The Cardinal Exam Rule Changing a Reconciliation Rule NEVER alters the number of unified records in Data Cloud, and it NEVER changes the consolidation rate. If an exam question asks how to increase the consolidation rate or link more customer profiles together, modifying reconciliation rules is always an incorrect distractor. Only Match Rules control profile consolidation.
The Three Standard Reconciliation Methods
Data Cloud provides three standard reconciliation methods for resolving field conflicts on the Unified Individual object. Each method is tailored to specific business requirements, data volatility profiles, and organizational systems of record.
1. Last Updated (Recency / Most Recent)
Operational Mechanics : Inspects the timestamp associated with each contributing source record within the cluster. The record possessing the most recent timestamp contributes its attribute value to the Unified Individual.
Timestamp Evaluation : Data Cloud evaluates the date/time field mapped during data ingestion (typically the source system's LastModifiedDate or an explicit business timestamp mapped to the DLO). If no custom date field is mapped, the ingestion system timestamp ( CreatedDate__c or LastModifiedDate__c ) is utilized.
Default System Status : Last Updated is the default reconciliation rule in Data Cloud. If an administrator maps a field to the Unified Individual and does not explicitly configure a custom reconciliation rule, Data Cloud automatically applies Last Updated.
Ideal Business Use Cases :
Highly volatile contact information that changes frequently over time (e.g., Mobile Phone Number, Mailing Address, Opt-In Consent Status).
Behavioral or situational attributes where current state supersedes historical records (e.g., Current Employer, Job Title, Preferred Channel).
Limitations : Susceptible to data corruption from batch ETL bulk-updates. For example, if a legacy database runs an automated script touching all records, their LastModifiedDate may be updated today, causing outdated legacy values to overwrite newer, accurate data.
2. Source Priority (Hierarchical System-of-Record)
Operational Mechanics : Allows the consultant to establish an explicit, ordered ranking of data sources. When reconciling an attribute, Data Cloud evaluates the contributing records against this priority hierarchy and selects the value from the highest-ranked source.
Hierarchy Configuration : Configured in the Identity Resolution UI by ordering the data streams or source objects associated with the Individual DMO (e.g., Tier 1: Service Cloud Contact; Tier 2: Sales Cloud Lead; Tier 3: B2C Commerce Account; Tier 4: Marketing Cloud Subscriber).
Handling of Null / Blank Values (Crucial Fallback Behavior) :
If the highest-priority source record contains a NULL or empty string for the attribute, Data Cloud does NOT overwrite populated data with null .
Instead, the reconciliation engine automatically traverses down the hierarchy to the next highest-priority source that contains a non-null, populated value.
Valid data from a lower-priority source is always preserved over a blank from a higher-priority source.
Tie-Breaker Mechanics :
What occurs if a cluster contains multiple records originating from the same priority source tier (e.g., two distinct Service Cloud Contact records clustered together)?
The Tie-Breaker is Last Updated : When multiple records share the highest available priority rank, Data Cloud selects the value from the record with the most recent LastModifiedDate among that tied tier.
Ideal Business Use Cases :
Verified, authoritative legal identifiers where human validation occurred (e.g., Legal First Name, Legal Last Name, Social Security Number / Tax ID, Date of Birth from a core CRM or KYC platform).
Enterprise master data management (MDM) integrations where a single system is legally designated as the system of record.
3. Most Frequent (Statistical Mode / Consensus)
Operational Mechanics : Evaluates all contributing source records in the cluster and counts the frequency of each unique attribute value. The value that appears with the highest occurrence count (the statistical mode) wins and populates the unified field.
Consensus-Driven Logic : Treats data sources as voting members. Even if a low-priority system contains an erroneous value, consensus among other systems overrides it.
Tie-Breaker Mechanics :
What occurs if two or more distinct values have identical frequency counts (e.g., Store #101 appears twice and Store #205 appears twice in a four-record cluster)?
The Tie-Breaker is Last Updated : When a frequency tie occurs, Data Cloud evaluates the tied candidates and selects the value from the record with the most recent LastModifiedDate .
Ideal Business Use Cases :
Categorical attributes, preferences, and demographic values that are captured across multiple touchpoints but rarely change (e.g., Preferred Retail Store, Preferred Language, Gender, Country of Residence, T-Shirt / Apparel Size).
Limitations : In small clusters containing only two records with differing values (a 1-to-1 split), Most Frequent immediately defaults to Last Updated, rendering the frequency calculation moot.
Comprehensive Reconciliation Methods Comparison
Reconciliation Method Decision Logic Tie-Breaker Mechanism Primary Enterprise Use Case Null Handling Behavior
Last Updated (Default) Most recent timestamp wins System-assigned internal record identifier Volatile contact details (Phone, Address, Opt-In status) Nulls are ignored if another record has a timestamped populated value
Source Priority Hierarchical ranking of source systems Last Updated (among records in the tied source tier) Authoritative master data (Legal Name, DOB, Tax ID, CRM status) Bypasses nulls ; falls back to the next ranked source with data
Most Frequent Highest occurrence count (statistical mode) Last Updated (among the values with tied frequency) Preferences & categorical consensus (Preferred Store, Language, Gender) Nulls are excluded from frequency counts
Field-Level Reconciliation Customization
In Salesforce Data Cloud, reconciliation rules are not applied uniformly across an entire object. Instead, rules are configured field-by-field on the UnifiedIndividual__dlm object. This granular flexibility enables enterprise architects to align each specific customer attribute with its natural business lifecycle. ┌─────────────────────────────────────────────────────────────────────────┐
- │ UNIFIED INDIVIDUAL FIELD MAPPING │
- ├───────────────────┬─────────────────────────┬───────────────────────────┤
- │ Field Name │ Reconciliation Rule │ Architectural Rationale │
- ├───────────────────┼─────────────────────────┼───────────────────────────┤
- │ FirstName │ Source Priority │ CRM Contact > Web Lead │
- │ LastName │ Source Priority │ Core CRM is Master │
- │ BirthDate │ Source Priority │ KYC Verified Source │
- │ MobilePhone │ Last Updated │ Captures recent changes │
- │ MailingAddress │ Last Updated │ Captures recent moves │
- │ PreferredStore │ Most Frequent │ Long-term shopping habit │
- │ PreferredLanguage │ Most Frequent │ Consensus across apps │
- │ OptInStatus │ Last Updated │ Compliance recency │
- └───────────────────┴─────────────────────────┴───────────────────────────┘
- Enterprise Design Scenario: The Multi-Source Dilemma
Consider a global retailer operating three primary systems:
Service Cloud : Contact records maintained by call center agents during customer service interactions.
B2C Commerce : E-Commerce customer profiles created during online checkouts.
Marketing Cloud : Subscriber profiles populated via newsletter signup forms.
If the customer's identity cluster contains records from all three systems, applying a single global rule would compromise data integrity:
Applying Last Updated globally : A customer enters a typo in a web newsletter form yesterday ( Fname: Jhn ), which immediately overwrites their verified legal name in Service Cloud ( Jonathan ).
Applying Source Priority globally (Service Cloud > Commerce > Marketing) : An old phone number entered in Service Cloud five years ago permanently supersedes a new, verified mobile number entered during an online checkout yesterday.
The Solution : Field-level customization. The architect assigns Source Priority to FirstName and LastName (Service Cloud > Commerce > Marketing) to protect legal identity integrity, while assigning Last Updated to MobilePhone and MailingAddress to capture fresh contact data.
Default Behavior and System Fallbacks
When deploying and maintaining Identity Resolution rulesets, consultants must understand how the engine behaves when configuration options are omitted or edge cases occur:
Unconfigured Attributes
When a standard or custom field on the Individual DMO is mapped to the UnifiedIndividual DMO, Data Cloud automatically assigns Last Updated as the default reconciliation rule. If the consultant does not navigate to the reconciliation canvas to customize the field, Last Updated will govern survivorship in production.
All-Null Attributes
If all contributing source records in an identity cluster contain a NULL or blank value for a specific attribute, the resulting field on UnifiedIndividual__dlm will be NULL . Data Cloud never synthesizes placeholder data.
Single-Record Clusters
For source records that do not match any other records (un-clustered individuals), the Unified Individual record directly mirrors the single source record's attributes. Reconciliation rules are only actively computed when two or more source records participate in the cluster.
Critical Exam Traps & Consultant Pitfalls
Warning
Exam Trap 1: The "Consolidation Rate" Distractor Scenario: "The marketing team wants to increase the Identity Resolution consolidation rate from 20% to 35%. Which configuration change should the consultant make?"
Distractor : "Change the reconciliation rule on First Name and Last Name from Last Updated to Most Frequent."
Why it's wrong : Reconciliation rules NEVER alter consolidation rates or cluster membership. To increase consolidation, the consultant must modify Match Rules (e.g., adding fuzzy match criteria, incorporating Party Identification matching, or matching on normalized phone numbers).
Caution
Exam Trap 2: The "Null Overwrite" Myth Scenario: "Source Priority is configured as Service Cloud (1) > POS (2). A Service Cloud record has a blank Email field, while a POS record has ' sarah@example.com '. Which value survives?"
Distractor : "NULL survives because Service Cloud is the top priority source and its null value overrides lower sources."
Why it's wrong : Source Priority skips nulls . Data Cloud will traverse to POS and populate 'sarah@example.com' .
Note
Exam Trap 3: The Universal Tie-Breaker Every tie-breaker scenario in Data Cloud Identity Resolution is resolved by Last Updated . Whether two records share the same source priority tier or two values share the identical occurrence count in Most Frequent, the record with the most recent timestamp wins.