Consent Management Objects
Get familiar with the objects that you can use for managing your customers’ privacy and consent.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: all editions. The Individual object is available for partner and customer community users. |
After you learn about these objects and fields, you can track and store certain data privacy preferences. But keep in mind that you must decide how to honor your customers’ privacy, and then implement a process to accomplish that.
For example, if you send communications to customers with Marketing Cloud Engagement, you can manage customers’ preferences for how they want to be contacted using consent management objects. To learn more, read the Respect Consent Preferences in Marketing Cloud Engagement with the Consent Data Model solution kit.
Note Consent management object records aren’t counted toward your storage usage.
| Object | What It Tracks |
|---|---|
| Authorization Form | The version number and effective dates of the authorization form. |
| Authorization Form Consent | Information related to the customer’s consent to the authorization form. |
| Authorization Form Data Use | The data use purpose associated with the authorization form. |
| Authorization Form Text | The text and language of the authorization form. |
| Communication Subscription | The customer’s preferences for a communication subscription. |
| Communication Subscription Channel Type | The engagement channel through which to contact a customer for a communication subscription. |
| Communication Subscription Consent | Information related to the customer’s consent to the communication subscription. |
| Communication Subscription Timing | The customer’s timing preferences for receiving a communication subscription. |
| Contact Point Consent | Information related to the customer’s consent to be contacted via a specific contact point. |
| Contact Point Email | The customer’s preference for the time that they prefer to be contacted via email. |
| Contact Point Phone | The customer’s preference for the time that they prefer to be contacted via phone. |
| Contact Point Type Consent | Customer allows contact via a specific contact point type like email, but not through phone calls and mail. |
| Data Use Purpose | The reason for collecting customer data. |
| Data Use Legal Basis | The legal basis for contacting an individual or party, such as legitimate interest. |
| Engagement Channel Type | The channel to use to reach a customer, such as email or web. |
| Individual | The customer’s preferences for:
|
| Party Consent | Information related to an individual’s consent. |
- Authorization Form Objects
Keep track of data related to authorization forms, such as terms of service, privacy policy, and other consent forms. Each authorization form object stores different data. You can use them together to create a full picture of your customer’s consent to the authorization form. - Communication Subscription Objects
You can store and manage the data related to your customer’s communication subscriptions, such as newsletters or appointment reminders. Different communication subscription objects store different data, such as how the customer consented to the communication subscription and preferred contact timing. - Fields in Data Privacy Records
Get the skinny on the fields that appear in data privacy records based on the Individual object. Data privacy records store certain privacy settings for your customers. - Fields in Contact Point Consent Records
Represents a customer's consent to be contacted via a specific contact point, such as an email address or phone number. - Fields in Contact Point Email Records
Fields in contact point email records store multiple email records related to an individual. - Fields in Contact Point Phone Records
Fields in contact point phone records store multiple phone records related to an individual. - Fields in Contact Point Type Consent Records
Contact point type consent records let you enter details about how a customer has agreed to be contacted by your company. For example, you can indicate that a customer consented to a specific contact point like email, but not phone calls and mail. - Fields in Data Use Purpose Records
Represents a category that defines the reason for contacting an individual. For example, billing, marketing, or surveys. - Fields in Data Use Legal Basis Records
Represents the legal basis for contacting an individual. For example, billing or contract. - Fields in Party Consent Records
Represents consent preferences for an individual.
Did this article solve your issue?
Let us know so we can improve!
