Ingesting Consent Preferences

Ingest consent preferences from wherever you’re storing them using connectors. Common storage locations include data extensions (Marketing Cloud Engagement Connector), Sales or Service Cloud standard or custom objects (Salesforce CRM Connector), or external sources (Cloud Storage Connector).

We recommend that consent preferences be mapped to objects from the Privacy Data Model, but they can be mapped to custom objects as well.

Note When using the Engagement Connector, only subscribers with Active status are ingested into Data 360.

For example, Northern Trail Outfitters ingests an Engagement Data Extension that includes Communication Subscription Consent and Communication Subscription Consent. These objects allow Northern Trail Outfitters to determine which engagement channels and communication subscription topics they can use to contact their customers. When creating the Data Stream for this Data Extension, Northern Trail Outfitters maps the Consent Preferences object to Data Model Objects (DMOs) from the Privacy Data Model.

Tip Map the relevant contact point objects for your consent objects. For Northern Trail Outfitters, they mapped Contact Point Email since Communication Subscription Consent and Communication Subscription Consent both contain email data. Northern Trail Outfitters also mapped the Party Identification object to create the required relationship with the Individual object.