Study guide
2.2 Consent Management & Preference Enforcement in Data Cloud
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
2.2 Consent Management & Preference Enforcement in Data Cloud
Key Takeaways Explain This Topic AI
The Data Cloud Consent Data Model relies on canonical DMOs: Individual (root entity), Contact Point Consent (channel endpoint opt-in/opt-out), Communication Subscription Consent (topic/brand level), and Data Use Purpose.
Contact Point Consent governs physical/electronic endpoints via PrivacyConsentStatus (OptIn, OptOut, Seen, NotSeen), while Communication Subscription Consent links consent to specific topics or business purposes.
Marketing segments must enforce consent using conservative exclusion logic: checking active consent statuses (PrivacyConsentStatus EQUALS 'OptIn') and filtering out opt-outs (PrivacyConsentStatus EQUALS 'OptOut' or DoNotTrack EQUALS True).
In multi-source identity resolution, reconciling conflicting consent flags across merged profiles requires a most-restrictive (conservative) governance rule: an opt-out on any merged contact point must suppress communication to protect consumer trust and legal compliance.
Consent synchronization must bridge external preference centers, Salesforce CRM Individual records, and Data Cloud via bi-directional connectors and real-time Ingestion APIs.
Last updated: September 2026
Consent Management & Preference Enforcement in Data Cloud
In an enterprise Customer Data Platform, possessing a unified customer identity does not confer an unrestricted license to communicate. Knowing a customer's email address, mobile number, and purchase history is legally inert without verifiable, active consent. A core responsibility of a certified Data Cloud consultant is configuring the Consent Data Model , harmonizing preferences across disparate touchpoints, and enforcing automated suppression within the segmentation engine before audience payloads leave the platform.
The Data Cloud Consent Data Model
Salesforce Data Cloud models privacy and preferences through the Customer 360 Canonical Data Model , specifically within the Consent subject area. This framework mirrors the Salesforce Core CRM Individual and Consent data architecture, establishing a standardized relational schema across brands and channels. Individual DMO (Master Identity & Global Privacy Flags)
- │
- ├── Contact Point Consent DMO (Channel Endpoint Level: Email, Phone, Address)
- │ └── PrivacyConsentStatus: OptIn | OptOut | Seen | NotSeen
- │ └── EffectiveFromDate / EffectiveToDate
- │
- └── Communication Subscription Consent DMO (Topic / Brand Level: "Weekly Deals")
- ├── Communication Subscription Channel Type DMO
- └── Data Use Purpose DMO (Legal Basis & Purpose: "Marketing", "Billing")
- Key Consent Data Model Objects (DMOs)
DMO Name Level of Granularity Core Attributes & Fields Business Function
Individual Person / Master Identity Id , DoNotTrack , HasOptedOutOfEmail , HasOptedOutOfFax , HasOptedOutOfPush , DoNotCall , SendIndividualData , ExportIndividualData Serves as the central anchor for global privacy preferences across all unified source profiles.
Contact Point Consent Channel Endpoint (Email, Phone, Device, Postal) ContactPointId , PrivacyConsentStatus , CaptureDate , EffectiveFromDate , EffectiveToDate , CaptureContactPointType , DoubleConsentCaptureDate Tracks whether a specific physical or electronic contact endpoint is authorized to receive communications. Statuses include OptIn , OptOut , Seen , and NotSeen .
Communication Subscription Consent Topic / Brand / Publication CommunicationSubscriptionChannelTypeId , DataUsePurposeId , ConsentStatus , EffectiveFromDate , EffectiveToDate Captures consent for a specific communication category (e.g., "VIP Monthly Newsletter" or "SMS Order Alerts"), linking channel types to business purposes.
Data Use Purpose Legal / Operational Basis Name , PurposeDescription , CanDataSubjectOptOut , LegalBasis Articulates the formal business purpose for data processing (e.g., Commercial Marketing vs. Operational Servicing under GDPR Art. 6).
Opt-In vs. Opt-Out Regimes Across Channels
Different communication channels operate under fundamentally divergent regulatory frameworks. Consultants must design consent capture and suppression logic tailored to channel-specific statutory standards:
1. Email Channel
United States (CAN-SPAM Act) : Operates primarily on an opt-out regime for commercial messages. Marketers may send commercial messages without prior explicit opt-in, provided the email contains clear identification, a physical postal address, and a functional, honored opt-out mechanism (processed within 10 business days).
European Union (GDPR) & Canada (CASL) : Require strict affirmative opt-in before sending commercial emails. Pre-checked boxes and implied consent are legally invalid. CASL distinguishes between express consent (perpetual until revoked) and implied consent (valid for 2 years following a transaction).
2. SMS and Mobile Messaging
United States (TCPA - Telephone Consumer Protection Act) : Strict prior express written consent is legally required before transmitting marketing text messages using automated telephone dialing systems. Violations carry statutory penalties of $500 to $1,500 per unauthorized message. Implied consent is prohibited for promotional SMS.
3. Mobile Push Notifications
Governed by mobile operating system permissions (iOS APNs / Android notification runtime permissions) combined with application-level subscription consent captured in Communication Subscription Consent .
4. Digital Advertising & Paid Media (AdTech)
CCPA/CPRA "Do Not Sell or Share My Personal Information" (DNS) : Consumers have the right to prohibit sharing their personal data for cross-context behavioral advertising. In Data Cloud, receiving a DNS flag or Global Privacy Control (GPC) signal must immediately trigger suppression from downstream activation targets (such as Google Ads Customer Match, Meta Custom Audiences, or Amazon Ads).
Filtering and Segment Suppression Based on Consent Flags
A critical failure point in Customer Data Platform implementations is relying on downstream execution systems (like Marketing Cloud or ad platforms) to handle consent filtering. A Data Cloud consultant must configure segment definitions to enforce consent suppression directly at the segmentation boundary.
Direct vs. Related Attribute Filtering
In the Data Cloud Segment Canvas, attributes are evaluated based on their relationship to the segment anchor (typically the Unified Individual DMO):
Direct Attributes : Global flags on the Individual DMO (e.g., HasOptedOutOfEmail EQUALS False or DoNotTrack EQUALS False ). These represent 1:1 attributes directly attached to the profile.
Related Attributes : Records residing in child DMOs with 1:N cardinality, such as Contact Point Consent or Communication Subscription Consent .
The Cardinality and Stale Record Trap
Because a customer may opt in in January, opt out in March, and opt back in in June, an Individual often has multiple historical Contact Point Consent records. Customer Record: John Doe
- ├── Contact Point Consent Record 1 (2024-01-01): PrivacyConsentStatus = 'OptIn'
- └── Contact Point Consent Record 2 (2025-06-15): PrivacyConsentStatus = 'OptOut'
- [!CRITICAL]
If a consultant constructs a segment condition: Contact Point Consent.PrivacyConsentStatus EQUALS 'OptIn' , the query engine checks if any child record meets the criteria. Because Record 1 matches 'OptIn' , the query evaluates to TRUE, inadvertently including an individual who actively opted out in Record 2!
The Architectural Solution : Always construct segment logic using a dedicated Exclusion Container :
Inclusion Criteria : Target audience criteria (e.g., high-value loyalty tier, recent purchase).
Mandatory Inclusion Rule : Related Attribute Contact Point Consent has PrivacyConsentStatus EQUALS 'OptIn' AND EffectiveToDate >= TODAY .
Exclusion Container : EXCLUDE any audience member where Contact Point Consent.PrivacyConsentStatus EQUALS 'OptOut' OR Individual.HasOptedOutOfEmail EQUALS True OR Individual.DoNotTrack EQUALS True .
Synchronization Across Systems & Preference Centers
Consent must remain synchronized across the enterprise ecosystem. If a consumer updates their preferences in an external portal, the update must propagate through Data Cloud and down to activation targets without lag.
External Preference Centers (OneTrust, TrustArc, Web Portals) : Capture consumer preference updates and push them into Salesforce via the Data Cloud Ingestion API or Salesforce CRM standard objects.
Salesforce Core CRM Sync : The standard Salesforce CRM Connector streams the Core Individual , ContactPointTypeConsent , and DataUseLegalBasis objects directly into Data Cloud standard DLOs, mapped 1:1 to canonical consent DMOs.
Consent Reconciliation in Identity Resolution : When Identity Resolution merges multiple source contact profiles into a single Unified Individual , privacy preferences can conflict. Consultants must enforce a Most-Restrictive (Conservative) Governance Policy : if any merged profile has an active opt-out flag ( OptOut ), the Unified Profile must treat the individual as opted out for that channel. Never use 'Last Updated' or 'Most Frequent' for consent reconciliation if doing so risks overwriting an explicit legal opt-out.