Imagine a customer signs up on your website as "Hers Suri" from "New Delhi." Meanwhile, your CRM already lists them as "Harshit S" from "Delhi." They share the exact same email address, meaning they are the same person. However, because the data is split and slightly conflicting, your system sees two different people.

This is where Identity Resolution comes in. It is a powerful feature within Salesforce Data 360 that merges duplicate records mapped to the Individual Data Model Object into a single, cohesive Unified Individual ID.

To achieve this perfect data harmony, Identity Resolution relies on two critical pillars: Matching Rules and Reconciliation Rules.

Matching rules act as a detective, scanning your data streams to identify which records belong to the same human being. You can leverage two types of matching:

• Exact Match: Looks for identical data, such as the exact same email address or first name ("Hers").

• Fuzzy Match: Catches slight variations or partial data, recognizing that "Suri" and "S", or "New Delhi" and "Delhi", are likely matches.

By combining these (e.g., exact email + fuzzy last name), the system confidently flags the records as duplicates.

2. Reconciliation Rules: Resolving the Conflicts

Once the system groups the duplicate profiles, a new question arises: Which data wins? Should the unified profile say "Delhi" or "New Delhi"? Reconciliation rules resolve these conflicts by defining your preferred values based on three main criteria:

• Most Trusted Source: You can prioritize a specific platform. If your CRM is highly accurate, the system will select the CRM's value ("Delhi").

• Newest Value: The system chooses the most recent data. If the website signup happened today, it will pull the website's value ("New Delhi").

• Most Frequent Value: If the value "Delhi" appears across both a lead and a contact record, but "New Delhi" only appears once on the website, the system picks the most frequent value ("Delhi").

The Audit Trail: Unified Individual Link

Once the heavy lifting is done, how do you track the changes? Salesforce Data 360 provides the Unified Individual Link object. Accessible via the Data Explorer, this object links your new Unified Individual ID back to the original source individual IDs, offering total transparency.

The Bottom Line: Matching rules identify your duplicates, while reconciliation rules solve your data conflicts—giving you a flawless, single source of truth.

In Data Cloud, your data flows from Data Lake Objects (DLOs) into Data Model Objects (DMOs). When dealing with profile data—like Leads from one Salesforce Org and Contacts from another—they all represent the same human being.

To achieve true data unification, Data Cloud uses a core profile DMO called the Individual Object.

• Profile Category Data: Leads, Contacts, and Accounts are mapped here.

• The Goal: Tie different IDs from different systems to a single Individual ID to build a single source of truth.

Syncing Engagement Data from Marketing Cloud

Beyond profile data, you also need to track how customers interact with your brand. This is EngagementData.

By connecting Salesforce Marketing Cloud in Data Cloud Setup, you can deploy Starter Bundles (Email, Mobile Connect, and Mobile Push). This automatically ingests standard data views like clicks, opens, bounces, and subscribers, mapping them instantly into the Data Cloud ecosystem.

Step-by-Step: Mapping Custom Data Extensions

What if you have custom subscriber data inside a Marketing Cloud Data Extension (DE) that isn't part of a standard bundle? You have to map it manually. Here is how:

1. Create a New Data Stream: Select Salesforce Marketing Cloud as the source and locate your specific Business Unit and DE folder.

2. Select the Category & Primary Key: For custom profile data, set the category to Profile and choose your unique identifier (e.g., Subscriber Key) as the Primary Key.

3. Map to Data Model Entities: * Create a Custom DMO to mirror your Data Extension fields.

   • Link and map your Subscriber Key to the Individual DMO (Individual ID) to ensure unification.

   • Map contact details to standard helper DMOs like Contact Point Email, Contact Point Phone, and Contact Point Address.

Once deployed, Data Cloud runs the stream, seamlessly feeding your custom marketing insights into a unified, actionable customer profile!

To start merging your data, you must tell the system which base objects to evaluate.

• Navigate to Identity Resolution and click Create New Rule Set.

• Select the Individual Object as the primary Data Model Object (DMO) you want to unify.

• Define your Rule Set Name (e.g., People) and a unique Rule Set ID.

Once created, the system automatically prepares the target architecture. For every standard object (like contact point email or phone), Data Cloud creates a corresponding unified object, such as Unified Individual and Unified Individual Email.

Step 2: Configure Matching Rules

Next, you define the logic Salesforce uses to catch duplicate records. Because customers rarely provide identical information everywhere, leveraging built-in AI precision rules is essential:

• Fuzzy First Name: Accounts for variations or typos (e.g., matching "Harsh" with "Harshit"). You can adjust the AI precision level to low, medium, or high.

• Exact Last Name: While people play with their first names, surnames usually stay consistent. Setting this to "Exact" keeps your matching accurate.

• Exact Normalized Email: This looks at the core email address, ignoring minor formatting differences.

Data Quality Tip: For normalized matching to work effectively, ensure good data hygiene upfront. Validate customer emails using OTPs or double opt-ins before importing them into Data Cloud.

Step 3: Run and Wait for Reconciliation

After saving your rules, click Update Status. The backend AI will begin processing, running reconciliation rules to link matching IDs across your Salesforce CRM, Marketing Cloud subscriptions, and external data lakes.

Keep in mind that this reconciliation process typically takes 2 to 3 hours to complete. Once finished, you can view the clean, single-source-of-truth profiles in the Data Explorer, fully primed for advanced segmentation and targeted marketing campaigns.

If you’ve ever dug into Salesforce Data Cloud (formerly known as Salesforce CDP / Data 360), you’ve probably run into the Individual object. It sits under the "Profile" category, and honestly, it is the secret sauce to making sense of all your customer data.

But what exactly is it, and why is it so important? Let's break it down in plain English.

The Big Problem: One Person, Many Identities

Imagine a customer named Sarah. Sarah interacts with your business in three different ways:

1. As a Lead: She fills out a form on your website. Salesforce creates a Lead record with a specific Lead ID.

2. As a Contact: Your sales team closes a deal with her. That lead gets converted into a Contact record with a completely new Contact ID.

3. As a Subscriber: She gets synced to Salesforce Marketing Cloud Engagement to receive your newsletters. Now she has a Subscriber ID.

Technically, Sarah has three different identities across your systems.

If you look at your engagement data—like who is opening emails, clicking links, or opening support cases—it’s scattered. To your systems, Sarah looks like three entirely different people.

Enter the "Individual" Object

This is where the Individual Data ModelObject (DMO) comes to the rescue.

In Data Cloud, your data is divided into different categories, like Engagement Data (clicks, opens, visits) and Profile Data (who the person actually is). The Individual object belongs to the Profile category.

Think of the Individual object as a universal bucket. When you bring your leads, contacts, and subscribers into Data Cloud, you don't just leave them in their separate corners. You map all of them to the Individual object.

By pointing all these different profile records to the Individual object, you are telling Data Cloud: "Hey, all of these records represent actual human beings. Keep them here."

How Data Cloud Unifies Your Data

Mapping everything to the Individual object is just step one. The real magic happens with Identity Resolution Rules.

Because you mapped your Leads, Contacts, and Subscribers to the Individual object, you can now write rules to link them together. For example, you can tell the system:

"If a Lead, a Contact, and a Subscriber all share the exact same email address, they are actually the same person."

Data Cloud runs these rules against the Individual object. It matches the duplicates and merges those three separate identities into a single, master profile called the Unified Individual.

Why This Matters

Without the Individual object and identity resolution, your data is siloed. You might send a marketing email to Sarah the "Subscriber" about a product that Sarah the "Contact" already bought.

By unifying everything into a single Unified Individual:

• You get a true 360-degree view of your customer.

• Your marketing becomes smarter because you know exactly who you are talking to.

• You stop wasting effort on duplicate records.

In short, the Individual object is the foundation that allows Salesforce Data Cloud to bridge the gap between fragmented data and a perfect, unified customer experience.

Segmentation and Activation: How It Works

Data Cloud shines by pulling diverse data into a single location. Marketing teams can then use the Segmentation feature to slice this unified data into targeted groups.

Once a segment is ready, it is Activated and sent to an external platform—such as Salesforce Marketing Cloud or Commerce Cloud. While an Activation Specialist can happily build these daily segments, an Activation Manager or Architect must first step in to establish the bridge (the Activation Target) to those external systems.

After the automated backend process finishes, head over to the AppLauncher (the nine-dot icon). Search for DataCloud and open it.

Thanks to your new permission set, the entire dashboard is now unlocked. You will see all configuration and menu items fully enabled, meaning you are officially ready to start connecting data streams and building out your Data 360 strategy!

Mastering CAN-SPAM in SFMC

Navigating email compliance can feel like a chore, but mastering the US CAN-SPAM Act is non-negotiable for digital marketers. In Salesforce Marketing Cloud (SFMC) Engagement, staying compliant boils down to understanding the distinct rules governing two types of emails: Commercial and Transactional.

• Commercial Emails: These promote products or services (e.g., "20% off your next Salesforce training").

• Transactional Emails: These are automated, triggered responses to a user's action (e.g., a purchase receipt or a bank transaction alert).

Because CAN-SPAM heavily targets commercial, promotional activities, SFMC provides built-in tools to keep your business fully compliant.

The law states your sender identity must be completely transparent. In SFMC, you configure this using a SenderProfile, where you define your From Name (e.g., People Who Skills) and From Email (e.g., info@peoplewhoskills.com). SFMC requires a one-time verification code to authenticate your email address, ensuring you never send from an unverified domain.

2. Honest Subject Lines & Compliant Footers

Your subject lines must accurately reflect the email content—promotional for commercial messages and straightforward for transactional ones (e.g., "Your Invoice is Ready").

Furthermore, commercial emails must include a physical mailing address and an unsubscribe link. SFMC manages these footer requirements via DeliveryProfiles. To prevent losing subscribers entirely, you can use PublicationLists. This allows a user to granularly opt out of specific streams (like Course Alerts) while remaining subscribed to others (like Webinar Invitations).

3. The Power of Send Classifications

SFMC combines your Sender Profile and Delivery Profile into a SendClassification within the setup menu. This classification tells the system whether an email is commercial or transactional.

Crucially, CAN-SPAM does not require unsubscribe links for transactional emails. If a customer buys a course or swipes their bank card, they are legally entitled to receive their transactional data. Forcing an unsubscribe option on these operational emails would actually violate a customer's right to receive critical financial or purchase summaries.

This is the green light. An Active subscriber is healthy, verified, and completely fit to receive your communications. Your primary goal is to keep as many subscribers in this state as possible.

2. Bounced

A bounce occurs when an email is sent from your SFMC account but fails to land inside the recipient's inbox. Bounces are split into two categories:

• Soft Bounce: A temporary delivery issue. The most common cause is a full recipient inbox. Once the subscriber clears out some space and a future email successfully delivers, their status automatically reverts to Active.

• Hard Bounce: A permanent delivery failure. This usually happens due to a critical typo in the email address (such as xyz.gmail.com instead of using the @ symbol), making the domain completely unavailable.

3. Held (Undeliverable)

Also referred to as Undeliverable, the Held status acts as a safety net to protect your sender reputation by stopping you from emailing dead accounts. A subscriber is moved here under two conditions:

• They experience an immediate hard bounce due to an invalid email address.

• They accumulate threesoftbounceswithina15-daywindow.

4. Unsubscribed

This status is driven purely by subscriber behavior. If a recipient decides they no longer want to see your content, they will utilize your opt-out link. SFMC automatically shifts them to Unsubscribed to honor their choice and keep your organization compliant.