--- schema_version: "1" id: c5bc627926b601a8e44dfa313fbf6ee11fa229d1dc5d63bd9f4ace151a4aad4c title: Understand the Salesforce Consent Data Model collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/consent_data_model_mc_about.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.consent_data_model_mc_about.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 52a4fba028397ff46ac34d6420755f808a8feee12061ffb454b767dbbd4c9a57 description: 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. products: - Marketing Cloud Account Engagement - Cross Cloud release: "264" --- # 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. ![Objects in the Salesforce consent data model](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-consent_data_model_marketing_cloud-264-0-0-production-enus/97f3c6f5-3ec6-44f0-9e6d-b63f2fbbf136/consent_data_model_marketing_cloud/images/consent_data_model.png) Consent is managed in the data model on four levels: global consent (1), engagement channel consent (2), contact point consent (3), data use purpose (4). Brand (5) isn’t a consent object, but it’s a critical component for distinguishing consent preferences by different brands. ## Global Consent Global consent governs all-or-nothing consent settings managed on the [Individual object](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_individual.htm). Global consent captures whether a customer approved communication. [Data privacy records](https://help.salesforce.com/s/articleView?id=platform.individuals_fields.htm&type=5&language=en_US) based on the Individual object contain fields for managing global privacy settings. - Block Geolocation Tracking—Preference to not track geolocation on mobile devices, - Don’t Process—Preference to not process personal data, which can include collecting, storing, and sharing personal data. - Don’t Profile—Preference to not process data for predicting personal attributes, such as interests, behavior, and location. - Don’t Solicit—Preference to not solicit products and services, - Don’t Track—Preference to not track customer web activity and whether the customer opens email sent through Salesforce. - Export Individual’s Data—Preference to export personal data for delivery to the individual. - Forget This Individual—Preference to delete records and personal data related to this individual. - Individual’s Age—Indication for whether the individual is considered to be a minor. - OK to Store PII Data Elsewhere—Indication that you can store personally identifiable information outside of their legislation area. For example, you can store an EU citizen’s personal data in the US. ![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-consent_data_model_marketing_cloud-264-0-0-production-enus/97f3c6f5-3ec6-44f0-9e6d-b63f2fbbf136/images/icon_example.png) Example For example, Rachel Rodriguez gives consent to be contacted with a few caveats. Here’s what her Individual record looks like. ![Example Individual record](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-consent_data_model_marketing_cloud-264-0-0-production-enus/97f3c6f5-3ec6-44f0-9e6d-b63f2fbbf136/consent_data_model_marketing_cloud/images/consent_data_model_individual.png) ## Engagement Channel Consent Engagement channel consent is managed on the [ContactPointTypeConsent object](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contactpointtypeconsent.htm). Use [contact point type consent records](https://help.salesforce.com/s/articleView?id=platform.contact_point_type_fields.htm&type=5&language=en_US) to enter consent preferences by a particular contact type, such as email or phone. ![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-consent_data_model_marketing_cloud-264-0-0-production-enus/97f3c6f5-3ec6-44f0-9e6d-b63f2fbbf136/images/icon_example.png) Example Rachel Rodriguez decides to change how your company can contact her. She sends a message to a representative and says, “You can email me, but you can’t call me.” Here’s an example of her Individual record with those changes. ![An example contact point type consent record](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-consent_data_model_marketing_cloud-264-0-0-production-enus/97f3c6f5-3ec6-44f0-9e6d-b63f2fbbf136/consent_data_model_marketing_cloud/images/consent_data_model_contact_point_type_consent.png) ## Contact Point Consent A customer’s consent to be contacted is managed on the [ContactPoinConsent object](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contactpointconsent.htm). [Contact point consent records](https://help.salesforce.com/s/articleView?id=platform.contact_point_consent_fields.htm&type=5&language=en_US) help you set consent by a specific contact point to be able to consider different consent preferences. For example, record a customer’s preferences for using a personal email as opposed to a work email address. ![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-consent_data_model_marketing_cloud-264-0-0-production-enus/97f3c6f5-3ec6-44f0-9e6d-b63f2fbbf136/images/icon_example.png) Example Rachel Rodriguez further refines her email consent preferences. She’s OK being contacted at her work email address, but not at her personal email address. ![An example contact point consent record](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-consent_data_model_marketing_cloud-264-0-0-production-enus/97f3c6f5-3ec6-44f0-9e6d-b63f2fbbf136/consent_data_model_marketing_cloud/images/consent_data_model_contact_point_consent.png) ## Data Use Purpose The [DataUsePurpose object](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_datausepurpose.htm) captures consent based on the reason for a communication. It’s displayed in [data use purpose records](https://help.salesforce.com/s/articleView?id=platform.data_use_purpose_fields.htm&type=5&language=en_US). The reason can be any legitimate business interest, including items that: - Are legal in nature, such as recall notices. - Used for marketing purposes, such as weekly newsletters, - Provide a service, such as warranty support. Data use purpose can relate to Contact Point Type Consent and Contact Point Consent objects. ![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-consent_data_model_marketing_cloud-264-0-0-production-enus/97f3c6f5-3ec6-44f0-9e6d-b63f2fbbf136/images/icon_example.png) Example Here’s an example of a data use purpose record specifying that a user consents to emails, but only for new product updates. ![An example data use purpose record](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-consent_data_model_marketing_cloud-264-0-0-production-enus/97f3c6f5-3ec6-44f0-9e6d-b63f2fbbf136/consent_data_model_marketing_cloud/images/consent_data_model_data_use_purpose.png) ## Brand Brand is managed on the [BusinessBrand object](https://developer.salesforce.com/docs/atlas.en-us.sfFieldRef.meta/sfFieldRef/salesforce_field_reference_BusinessBrand.htm). While not strictly part of the consent data model, Brand helps you distinguish between privacy and consent preferences that vary between different brands operating in the same Salesforce org. The Brand object has a native relationship with Contact Point Type Consent and Contact Point Consent objects. To tie an originating contact record with its related contact point consent records in Marketing Cloud Engagement, we also connect Brand to the Contact object. ## Understanding Currently Available Consent APIs Users sometimes store consent preferences inconsistently across different locations. To locate customer consent preferences across multiple records, use Consent API with specific Data Cloud parameters. Tracking consent preferences helps you and your users respect the most restrictive requests. Consent API aggregates consent settings across the Contact, Contact Point Type Consent, Data Use Purpose, Individual, Lead, Person Account, and User objects when the records have a lookup relationship. The Consent API can’t locate records in which the email address field is protected by Shield Platform Encryption. The Consent API returns consent details based on a single action, like email or track. The multiaction endpoint allows you to request multiple actions in a single API call. ## Related Content
Icon of an arrow that points right.

Take the next steps in this implementation.
#### See Also - [_Marketing Cloud Engagement Cross-Cloud Products_: Subscriber Key](https://help.salesforce.com/s/articleView?id=mktg.mc_co_subscriber_key.htm&type=5&language=en_US) - [_REST API Developer Guide_: Consent](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_consent.htm)