Explore Consent Tools and Concepts
Learning Objectives
After completing this unit, you’ll be able to:
- Describe how Consent Management deeply integrates with Data 360.
- Identify the key objects operating in the core consent data model.
- Describe the available consent tools and options.
How Consent Management Works: The Data 360 Connection
To truly understand Consent Management in Marketing Cloud Next, you must understand its deep architectural relationship with Data 360. Unlike legacy CRM systems that crudely store opt-outs directly as a simple checkbox on a lead or contact record, Marketing Cloud Next manages all consent centrally using Data 360. Every single time a customer opts in or opts out of a communication, that specific preference is instantly recorded and stored as a data model object (DMO) inside Data 360.
This centralization provides a massive advantage. Data 360 functions to unify customer data from multiple distinct sources—such as Agentforce Sales, Agentforce Service, and your external e-commerce website—creating a highly accurate Unified Individual profile. Because consent is securely anchored within Data 360, a customer service rep speaking on the phone views the exact same communication preferences as the digital marketing team building an email journey.
When an email or text message is queued to send, Marketing Cloud Next evaluates the consent records stored as DMOs in Data 360 for the recipient’s specific email address or phone number. By querying these unified DMOs at send time, the system confirms whether it’s compliant and safe to transmit the message. This deep integration ensures that your marketing engine operates using the most up-to-date, centralized permissions available, without relying on fragmented data.
Key Components of the Consent Model
To properly capture and manage consent at scale, Marketing Cloud Next uses a specific suite of interconnected primary objects. These objects work together seamlessly to build a complete, legally compliant picture of subscriber preferences.
- Contact Point: Defines the contact information required to consent to a marketing subscription and channel, such as an email address or phone number. The contact point objects securely store the actual routing addresses for the customer. It’s vital to recognize that consent is intrinsically tied to these specific contact points, not just the generic person record. If a customer changes their email address, the historical consent does not automatically transfer over. A brand-new consent record must be generated for the newly provided email address.
- Communication Subscription: Represents the actual list, topic, or category the customer is joining. Common examples include Monthly Newsletter, Product Updates, or Emergency Weather Alerts. Subscriptions act as the thematic buckets for your marketing content.
- Engagement Channel Type: Defines the broad communication medium itself. Standard engagement channel types include Email, SMS, and WhatsApp.
- Communication Subscription Channel Type: Defines the specific delivery method tied to the subscription. A single subscription theme can exist across multiple channels, but the user must opt in per channel. Examples include Email, SMS, or WhatsApp.
- Communication Subscription Consent: Defines the ultimate truth: whether a specific contact point has an explicit opt-in or opt-out status for a given subscription and a given channel. This is the core intersection record. It also tracks the exact date the consent was provided and the source of that consent.
Available Consent Tools and Options
Marketing Cloud Next provides several powerful, built-in tools designed to capture, display, and manage your consent preferences efficiently.
Preference Pages
Marketing Cloud Next empowers you to build and publish customizable Preference Pages directly within the Content tab. These are dedicated, branded web pages where your active subscribers can securely manage their own ongoing communication preferences. Marketers can easily control the look and feel without needing developer support. You can easily generate dynamic links directly within your email templates that route users to these secure pages. This empowers customers to selectively opt in or opt out of specific topics, vastly reducing global unsubscribe rates and minimizing customer frustration.
Consent Status
This is a useful Lightning Web Component (LWC) that Salesforce admins can drag and drop onto standard Prospect, Lead, Contact, and Person Account page layouts. It grants your frontline sales and service representatives the ability to manually view, verify, and update a customer’s opt-in or opt-out status via a simple, intuitive dropdown interface while they’re speaking with the customer.
Consent Imports
If your organization is undergoing a major digital transformation and migrating from another legacy marketing system, it’s necessary for you to bring historical consent data with you. Your admins can use the built-in Consent Imports feature to securely upload formatted CSV files to create or update consent statuses across thousands of records simultaneously. A few common examples of consent imports include Create Subscription Consent Record, Update Subscription Consent Record, and Create Contact Point Record.
Salesforce Flow Integration
You can automate complex consent capture scenarios using the power of Salesforce Flow. For example, you can build a flow that creates an opt-in subscription record the exact moment a net-new Lead submits a specific web-to-lead form on your corporate website.
Note that there are strict configuration requirements. The only supported flow triggers are Data Cloud Record-Triggered Flow, Automation Event-Triggered Flow, and On-Demand Triggered Flow. All other triggers are not supported. And you must select the correct actions depending on your trigger. For Data Cloud Record-Triggered flows, use the Create Consent action. For Automation Event and On-Demand Triggered flows, use the Consent Request action.
Crucial warning: Do not use the MessagingConsent.MessagingConsent or MessagingConsent.MessagingConsentV2 actions, as they can cause system issues. By adhering to these guidelines, you can securely configure flows to automatically generate new consent records when specific entry conditions are met.
What’s Next
Now you know how Consent Management deeply integrates with Data 360 to unify customer preferences across your entire organization. And you know about the key data model objects and powerful built-in tools like the Preference Pages and Salesforce Flow integrations. In the next unit, you explore the unique, channel-specific requirements for Email, SMS, and WhatsApp to guarantee compliance across every digital touchpoint.