---
schema_version: "1"
id: ce622fde1b19bc42480f7243ee33d6485ddcb690db35a86805d062d39c9a51c3
title: Workflow
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_workflow.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.consent_data_model_mc_workflow.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3f9775b8e7d0f8bf9e832083f5e1f8b23b679a094fdb4cefefdb48c24f31c1a5
description: 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.
products:
  - Marketing Cloud Account Engagement
  - Cross Cloud
release: "264"
---
# 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.

![Workflow for managing consent preferences in Marketing Cloud.](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_mc_workflow.png)

- Individual contact and consent data is created in the Salesforce Consent Data Model from a point of sale (POS) entry or account creation on Experience Cloud. It can also be captured from a custom profile page in Commerce Cloud during purchases. For example, from a POS entry, account creation process, or a preference page for a consumer’s profile. (1)
- Contact data is stored against any object that relates to the Individual object, including Lead, User, Person Account, and Contact. Consent data is stored in consent management objects, including Individual, Contact Point Type Consent, Contact Point Consent, and Data Use Purpose objects. (2)
- Contact and consent data is synchronized to Engagement via Marketing Cloud Connect to Synchronized Data Extensions. (3)
- Queries are created to relate subscribers to the associated contact point consent record, identifying which consent records relate to which subscribers. (4)
- A shared data extension is created and exposed to the required child business unit. (5)
- Contact data is now aligned to related consent data and is ready for marketing use and activation. (6)
- Subscribers receive an email that honors consent. (7)
- Subscribers can unsubscribe using spam flags, reply unsubscribe, or application unsubscribe. (8)
- Engagement stores the unsubscribe on the All Subscribers list. (9)
- Two processes monitor for unsubscribe events in Engagement and return the consent signal to the Salesforce Consent Data Model. (10)
    - Flow initiates an API call to Engagement to retrieve the unsubscribe events for the previous day.
    - A weekly refresh process retrieves all subscribers with an unsubscribed status.

## Related Content

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:7.6923076923076925%">
          <col style="width:92.3076923076923%">
        </colgroup>
        <tbody>
          <tr class="">
            <td class="slds-cell-wrap" style="text-align:left;vertical-align:top;">
              <span style="vertical-align:text-bottom;display:inline-block;"><img style="width:40px;margin-bottom:0;" src="https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-consent_data_model_marketing_cloud-264-0-0-production-enus/97f3c6f5-3ec6-44f0-9e6d-b63f2fbbf136/resources-global/_corporate/images/back_icon.png" alt="Icon of an arrow that points left."></span>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;">
              <p>Review earlier steps in this solution.</p>
              <ul>
                <li><a href="https://help.salesforce.com/s/articleView?id=xcloud.consent_data_model_mc_about.htm&amp;release=264.0.0&amp;type=5" title="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.">Understand the Salesforce Consent Data Model</a></li>
              </ul>
            </td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" style="text-align:left;vertical-align:top;">
              <span style="vertical-align:text-bottom;display:inline-block;"><img style="width:40px;margin-bottom:0;" src="https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-consent_data_model_marketing_cloud-264-0-0-production-enus/97f3c6f5-3ec6-44f0-9e6d-b63f2fbbf136/resources-global/_corporate/images/next_icon.png" alt="Icon of an arrow that points right."></span>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;">
              <p>Take the next steps in this implementation.</p>
              <ul>
                <li>
                  <a href="https://help.salesforce.com/s/articleView?id=xcloud.consent_data_model_mc_design_considerations.htm&amp;release=264.0.0&amp;type=5" title="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.">Design Considerations</a>
                </li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>