⚡ Key Points
- Consent is Mandatory: Under privacy regimes like GDPR, CCPA, and others, you must have a lawful basis or explicit consent to process data and send messages.
- The Master Key: Marketing Cloud relies on the
Subscriber Keyto manage consent globally. - Four Statuses: A subscriber is always categorized as Active, Held, Unsubscribed, or Bounced.
- Data Extension Failsafe: Even if a user's email exists in the exact Data Extension you are using for a send, SFMC will suppress them if their master status is "Unsubscribed".
A customer receives your monthly newsletter and clicks "Unsubscribe." SFMC immediately writes "Unsubscribed" to their profile in the All Subscribers master list. Tomorrow, a marketer tries to send a promotional blast using a custom Data Extension that still contains that customer's email address. Marketing Cloud checks the All Subscribers list, sees the opt-out, and automatically skips them during the send.
๐️ Core Concept: How SFMC Enforces Consent
Because Marketing Cloud sends communications to real people, enforcing user consent is the architectural foundation of the platform.
- GDPR Rules: You cannot message someone without their permission, and subscribers possess fundamental rights over their data (including the right to access and the right to erasure).
- All Subscribers List: This is the ultimate source of truth for email status in SFMC. Unsubscribes are honored globally at this level.
- Preference Centers: For fine-grained control, custom Preference Centers allow subscribers to opt-out of specific categories (e.g., "Stop sending me Promos, but keep sending me Account Alerts").
In practice, running a compliant Marketing Cloud org means you must master four operational rules:
- Capture explicitly: Never send an email to a purchased list without documented consent.
- Honor globally: Ensure unsubscribes update the master All Subscribers list.
- Facilitate rights: Build processes to honor Right to be Forgotten (data erasure) requests.
- Integrate broadly: When enterprise platforms like Data Cloud (formerly Data 360) are involved, leverage the Consent API to unify privacy rules across Salesforce CRM and SFMC.
Rule: Consent is enforced at the platform level, not just visually on a record. Every send checks the master status before delivery.
Gain: You maintain a single master status per person. A careless marketer importing a stale list cannot accidentally email unsubscribed users.
Price: If you use both SFMC and Salesforce CRM, you now have two separate systems that hold an opinion on user consent. They can disagree if you don't sync them properly.
Limits: Right to be Forgotten requires actual data erasure or deep suppression, which goes much further than a simple unsubscribe.
At Volume: A bad data import without status mapping can overwrite the consent preferences for millions of users instantly. You must safeguard your import activities.
Do not confuse an "Unsubscribe" with the GDPR "Right to be Forgotten" (Erasure). An unsubscribe simply changes a user's status so they stop receiving emails, but you retain their data. Erasure requires completely anonymizing or deleting the user's data from your Data Extensions and CRM.
๐ฏ Core Q&A
Q: How does Marketing Cloud ensure you don't accidentally email someone who has opted out? And how does GDPR shape this?
A: Marketing Cloud acts as a strict gatekeeper. Every recipient is tied to a Subscriber Key in the All Subscribers list, which holds their master status. If a user unsubscribes, their Subscriber Key status flips to "Unsubscribed." Because this check happens at the absolute master level, the system will suppress that user across every single List and Data Extension send.
GDPR shapes this by legally requiring a lawful basis to process data and granting users control over it. Therefore, you must capture consent properly, honor it globally, and build workflows to delete user data when they invoke their Right to be Forgotten.
๐ Scenario Follow-ups
Q1: A subscriber invokes their Right to be Forgotten. What must happen technically?
A: Their data must be entirely erased or anonymized so they can no longer be processed or messaged. Practically, you must delete their records from all custom Data Extensions. Furthermore, you must ensure their Subscriber Key is suppressed or deleted at the All Subscribers master level so no rogue future import can resurrect them. In enterprise setups, this erasure command is usually orchestrated centrally via Data Cloud's Consent API, which pushes the deletion command down into Marketing Cloud.
Q2: Marketing Cloud has an "Unsubscribed" status, but Salesforce CRM has the "Email Opt Out" checkbox. Which one wins?
A: Neither automatically wins—they are two separate truths living in two separate databases. An integrated enterprise must explicitly pick one system as the master for consent and sync the data. Usually, Marketing Cloud is declared the master for commercial email consent, and Marketing Cloud Connect is used to continually sync the CRM checkbox to match SFMC. The fastest way to fail compliance is to leave both systems unsynced.