Respect Consent Preferences in Marketing Cloud Engagement with the Consent Data Model

Understand the Salesforce Consent Data Model, its components, and purpose. Then use that data model to manage and respect consent preferences in Marketing Cloud Engagement.

Get Started

Take Trailhead modules related to this solution. Salesforce Solution Kits: Quick Look European Union Privacy Law Basics California Consumer Privacy Act Basics US Privacy Law Basics

With the Salesforce Consent Data Model, you can implement simple and complex consent management practices based on your business and regulatory requirements. Add components to refine and expand consent management with more granular controls as business needs change. Then connect that consent data to the Engagement org so that communications respect users’ consent preferences.

This solution kit helps you:

• Capture and manage consent effectively at multiple consent levels.
• Consume and honor consent preferences in Engagement.
• Understand how to use consent objects to access and use consent data.

Note This solution depends on a 1:1 data model between the Contact record and the contact point information contained on that contact record. Before beginning this solution, structure your data model to use one email contact point per contact. Marketing Cloud Connect requires the originating contact record ID as the key for the subscriber in Engagement. The Design Considerations outline this requirement in more detail.

Data flows for subscriber and consent information related to mobile SMS opt-in and lead conversion are outside the scope of this solution. Consider these data flows separately.

• Understand the Salesforce Consent Data Model
  The Salesforce Consent Data Model is the standard data model for managing consent at multiple levels, from global preferences to more granular controls. This data model, the foundation of Salesforce’s long-term view of consent, considers the individual’s entire experience, not just a single contact point. Any record that relates to an individual can have related consent considered within this model, including leads, users, person accounts, and contacts. It also provides flexibility to choose which level to manage consent initially. You can then add levels of granularity as business needs evolve or regulatory requirements change for managing that consent data.
• Workflow
  Learn how data flows through the configurations when you use the Salesforce Consent Data Model to manage and respect consent preferences in Marketing Cloud Engagement. For this solution kit, we consider a scenario where contact point information ties to a Contact record.
• Design Considerations
  To take full advantage of the Salesforce Consent Data Model, keep these design considerations in mind. They’re designed to help you access and interpret privacy preferences. They also help you create a durable design that can accommodate changes to consent-related business needs and regulatory requirements.
• Configurations
  Follow these configuration steps to use the Salesforce Consent Data Model to manage and respect consent preferences in Marketing Cloud Engagement.