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!

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.

Decoding SFMC Data Extensions

Unlike rigid, standard Lists, Data Extensions (DEs) act as flexible, custom relational database tables within Salesforce Marketing Cloud Engagement. They can store both subscriber profile data (sendable) and behavioral data (non-sendable).

To manage your audience effectively, you need to know the right tool for the job. Here is a quick breakdown of the types of Data Extensions available and when to use them.

1. Standard Data Extensions

Built manually from scratch, Standard DEs allow you to define your own fields, data types, and primary keys. Depending on your needs, you can configure them to be either sendable (to target subscribers) or non-sendable (for storing relational data like purchase history).

2. Filtered Data Extensions

When you have a master DE and need a specific segment, you use a Filtered DE. By defining clear rules—such as "subscribers older than 30 living in New Delhi"—you generate a new subset.

• Key Benefit: It automatically copies the exact schema, data types, and send configurations of the source DE.

3. Random Data Extensions

Perfect for A/B testing, Random DEs split a master audience into smaller segments based on percentages rather than specific criteria. For example, you can randomly grab 10% of your audience to test an email subject line before launching it to the masses.

4. Synchronized Data Extensions

Connected via Marketing Cloud Connect, these DEs pull data directly from Salesforce Sales or Service Cloud standard and custom objects (like Leads or Contacts).

• The Catch: You cannot send communications directly to a Synchronized DE. Because data updates on a polling schedule (ranging from 15 minutes to 1 hour), you must first query or filter this data into a Sendable DE.

5. Salesforce Data Extensions

If you want your email engagement metrics (opens, clicks, bounces) to sync back to Salesforce Core as Individual Email Results, you must use a Salesforce Data Extension. Using a standard DE will keep that tracking data locked inside Marketing Cloud.

Pro Tip: Any of these types can be saved into a shared folder, turning them into Shared Data Extensions that can be accessed across multiple business units in your organization.

 Key Lists in Salesforce Marketing Cloud

Managing data efficiently in Salesforce Marketing Cloud (SFMC) is crucial for campaign success. If you are using a list-based data model, understanding the different types of lists helps you target the right audience, manage preferences, and protect your email metrics.

Here are the four essential types of lists in SFMC explained in simple points:

1. Subscriber Lists & The "All Subscribers" Master List

• StandardSubscriberLists: These are your go-to lists for importing data. A single standard list can hold up to 500,000 subscribers. To store more than that, you must create a new list within the platform.

• AllSubscribersList: This is the master list within Email Studio. Whenever you import subscribers into a normal list or trigger a send via sendable Data Extensions, they are automatically added here. It serves as the central source of truth for profile data and subscription statuses.

2. Publication Lists

• SubscriptionPreferenceManagement: These lists are used to manage custom subscriber preferences and opt-outs for different communication categories (such as Course Updates, Webinar Invitations, or Product Launches).

• FlexibleUnsubscribes: When a subscriber opts out from an email sent using a Publication List, they are only removed from that specific category. They remain active on the master All Subscribers list, ensuring you do not lose them entirely.

3. Suppression Lists

• The"DoNotSend"List: These act as a filter during an email send to omit specific addresses, such as test accounts or internal organization employees.

• ProtectingKPIs: Excluding internal audiences ensures your campaign Key Performance Indicators (KPIs)—like open, click, and unsubscribe rates—remain clean, realistic, and accurate.

• ManualSelection: Standard suppression lists must be manually selected each time during the send flow setup in Email Studio, Automation Studio, or Journey Builder.

4. Auto-Suppression Lists

• Error-FreeAutomation: To prevent human error—like forgetting to manually add a suppression list during a busy campaign launch—SFMC uses Auto-Suppression Lists.

• Hands-FreeFiltering: Subscribers added here are automatically excluded from all platform sends without you needing to select them manually during the send flow.

Leveraging these four lists effectively gives your subscribers flexibility while keeping your marketing metrics pristine!

A Subscriber is an individual who has actively opted in to receive communications from your company via a specific channel.

• EmailStudio: Opting into emails makes someone an Email Subscriber, adding them to the "All Subscribers" list.
• MobileStudio: Opting into SMS or push notifications makes them a Push/SMS Subscriber.

Subscribers are inherently siloed by the specific channel they use to interact with your brand.

What is a Contact?

Businesses need a single, holistic view of a customer's entire footprint. That’s where Contacts come in.

Inside ContactBuilder, the AllContacts section acts as your master database. Marketing Cloud treats an individual as a single contact, regardless of how many channels they use. Whether you receive an email, an SMS, or a push notification, SFMC ties all of these channel addresses and activities back to one unique Contact.

TheGoldenRule: A contact can exist without being an email subscriber. For instance, if someone only signs up for mobile push notifications, they will exist in All Contacts (with their App ID) but will be completely absent from Email Studio's All Subscribers list.

Key Differences at a Glance

How is Contact Data Created?

Contacts enter your "All Contacts" database through several primary methods:

• DirectImports: Loading data straight into Contact Builder.
• MarketingSends: Sending a communication to a new List or Data Extension automatically registers them.
• SalesforceDataSync: Syncing data seamlessly from Sales or Service Cloud.
• APIs: Creating contacts programmatically from external systems.

By understanding this distinction, you can better manage your cross-channel journeys and ensure your audience gets a unified experience, no matter the channel.