---
schema_version: "1"
id: d5b58ea0920b9f989216105bce92809552e5d54b5f49780e54cc9a47d11af85f
title: Consent Management for Marketing Cloud Engagement
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/consent_management_marketing.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.consent_management_marketing.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7e57bf4164df86b8bcacd96dc766373230a3b7323da8fd71b92356544fd0073b
description: Honor and respect your customers’ wishes when they request only specific forms of contact from your company or opt-out of certain types of data-sharing. We provide details to help you determine the best way to comply with the data protection and privacy regulations that apply to your company.
products:
  - Security
  - Cross Cloud
release: "264"
---
# Consent Management for Marketing Cloud Engagement

Honor and respect your customers’ wishes when they request only specific forms of contact from your company or opt-out of certain types of data-sharing. We provide details to help you determine the best way to comply with the data protection and privacy regulations that apply to your company.

Many data protection and privacy regulations require you and your company to honor people’s requests about how you use their data. Customers can also request that you restrict tracking and analytical processing using their data. These functions can occur when deciding what content to deliver to customers or using that data to predict future behavior. We’ve listed a few of the regulations that are important to many companies collecting and processing their customers’ data.If you have customers or users who request specific methods of contact from your company, review these common requests and the procedures related to them.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col style="width:33.33333333333333%">
        <col style="width:33.33333333333333%">
        <col style="width:33.33333333333333%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d25339e41">Common Customer Request</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d25339e44">Actions to Consider</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d25339e47">Things to Consider</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="Common Customer Request" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e41 ">
            <ul>
              <li>Email Studio users need to obtain consent for contacts receiving
                marketing communications.</li>

              <li>MobileConnect users need to obtain consent for contacts
                receiving marketing communications, including double opt-in best
                practices and compliance with local regulations.</li>

              <li>MobilePush users need to obtain consent for contacts receiving
                push notifications. Consent is not required to send inbox or
                in-app messages to contacts.</li>

              <li>GroupConnect users need to obtain consent for contacts receiving
                marketing communications.</li>

              <li>Audience Studio users need to obtain consent for contacts
                receiving marketing communications.</li>

            </ul>
          </td>

          <td data-label="Actions to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e44 ">
            <ul>
              <li>Use profile and preference center functionality for <a href="https://help.salesforce.com/s/articleView?id=mktg.mc_es_profile_pref_attributes.htm&amp;type=5&amp;language=en_US" target="_blank">Email
                  Studio</a> to capture consent and opt-in confirmation for
                your marketing messaging activities. These consent mechanisms
                also govern access to email data used in Einstein Engagement
                Frequency and Send Time Optimization.</li>

              <li>MobileConnect, MobilePush, and GroupConnect users should use
                your website or messages to notify subscribers of privacy
                changes and reestablish consent.</li>

              <li><a href="https://konsole.zendesk.com/hc/en-us/articles/360000488433" target="_blank">Review consent management information for
                  Audience Studio</a>.</li>

            </ul>
          </td>

          <td data-label="Things to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e47 ">
            <ul>
              <li>Collection of compliance requests takes place outside of
                Marketing Cloud Engagement functionality. Determine the best
                process for your business to receive and store this information
                as part of your data protection and privacy regulation
                review.</li>

              <li>Make sure your consent language corresponds to your privacy
                notices and policies. Provide explicit information about the
                data you collect.</li>

              <li>Consent must be specific, informed, and unambiguous. Collect
                positive consent and avoid automatically selected
                checkboxes.</li>

              <li>The process for obtaining consent regarding messaging to
                children is stricter.</li>

              <li>Contacts must be able to withdraw consent at any time.</li>

              <li>Contacts must freely give consent, and you cannot base usage of
                your website on provision of consent.</li>

              <li>Consent to use data must be specific for each purpose for which
                you use data.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Common Customer Request" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e41 ">I do not want Marketing Cloud Engagement to track my messaging and
            online behavior.</td>

          <td data-label="Actions to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e44 ">
            <ul>
              <li>Create a mechanism for receiving a <a href="https://help.salesforce.com/s/articleView?id=mktg.mc_es_do_not_track_email_opens_and_clicks.htm&amp;type=5&amp;language=en_US" target="_blank">Do Not Track request</a>, such as a preference
                center.</li>

              <li>Use the <a href="https://help.salesforce.com/s/articleView?id=mktg.mc_es_configure_the_preference_attribute_for_do_not_track_email_opens_and_clicks.htm&amp;type=5&amp;language=en_US" target="_blank">DoNotTrack preference attribute</a> to
                suppress subscriber-level events, such as opens, clicks, and
                replies. </li>

              <li>This process does not affect messages or tracking sent before
                the Do Not Track request.</li>

              <li>Review any ENS subscriptions that contain engagement
                events.</li>

            </ul>
          </td>

          <td data-label="Things to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e47 ">
            <ul>
              <li>This process permits continued sending to contacts with the
                DoNotTrack preference attribute enabled.</li>

              <li>You cannot track related behavioral interactions.</li>

              <li>This function applies only to Email Studio and as a preference
                attribute.</li>

              <li>Messages sent to contacts with the DoNotTrack preference
                attribute enabled do not appear in tracking reports and can
                cause incomplete or inaccurate reporting.</li>

              <li>The Do Not Track feature stops your account from receiving open
                and link tracking data for a data subject for any sends after
                the request date. Sends from before the request date continue to
                return this data. We plan to stop reception of this data for all
                sends in a future release.</li>

              <li>Contact records receive a value for the DoNoTrack attribute upon
                creation of the record. Any import after that creation does not
                overwrite that value. Any change requires a specific update in
                Marketing Cloud Engagement or via an API call.</li>

              <li>The Do Not Track process doesn’t stop subscriber data events
                from emitting to your Event Notification Service Callback if
                you’re subscribed to events that contain subscriber data. Events
                can be emitted from before and after the Do Not Track request if
                the subscriber continues to engage with Marketing Cloud
                Engagement content with tracking. Users should carefully opt-in
                and understand the implications to using the ENS engagement
                events.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Common Customer Request" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e41 ">One of my customers in California asked me to delete her information.
            How do I delete their personal data from the contact record?</td>

          <td data-label="Actions to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e44 ">
            <a href="https://help.salesforce.com/articleView?id=mc_cab_contact_deletion.htm&amp;type=5&amp;language=en_US" target="_blank">Contact Delete in Contact Builder</a>
          </td>

          <td data-label="Things to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e47 ">
            <ul>
              <li>Deleting a contact in MobilePush and MobileConnect also deletes
                opt-out preferences associated with the contact.</li>

              <li>Identify whether you track this customer in other Salesforce
                Clouds, and consider removing his contact data from them.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="Common Customer Request" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e41 ">What data fields do Marketing Cloud Engagement Einstein features
            process?</td>

          <td data-label="Actions to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e44 ">
            <a href="https://trailhead.salesforce.com/en/content/learn/modules/einstein-for-marketing-cloud-basics" target="_blank">Learn about Marketing Cloud Engagement
              Einstein</a>
          </td>

          <td data-label="Things to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e47 ">Data sets vary by feature, but Marketing Cloud Engagement Einstein
            processes data as needed for generating outputs of any specific feature.
            For example, to generate recommendations, Send Time Optimization and
            Engagement Frequency features look at email engagement data.</td>

        </tr>
        <tr class="">
          <td data-label="Common Customer Request" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e41 ">How do opt-out and rights request tools in Marketing Cloud Engagement
            affect Marketing Cloud Engagement Einstein features?</td>

          <td data-label="Actions to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e44 ">
            <a href="https://help.salesforce.com/articleView?id=data_deletion_marketing.htm&amp;type=5&amp;language=en_US" target="_blank">Data Deletion for Marketing Cloud
              Engagement</a>
          </td>

          <td data-label="Things to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e47 ">Marketing Cloud Engagement Einstein features process a rolling 90-day
            window of data.</td>

        </tr>
        <tr class="">
          <td data-label="Common Customer Request" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e41 ">A customer in California requested that I restrict his information.
            If I restrict or delete that contact in Marketing Cloud Engagement, is
            his information also removed from Advertising Studio segments?</td>

          <td data-label="Actions to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e44 ">
            <a href="https://help.salesforce.com/articleView?id=data_deletion_marketing.htm&amp;type=5&amp;language=en_US" target="_blank">Data Deletion for Marketing Cloud
              Engagement</a>
          </td>

          <td data-label="Things to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e47 ">To fully address a contact's rights request, consider any actions to
            take on social network platforms for which you've sent audience
            segments.</td>

        </tr>
        <tr class="">
          <td data-label="Common Customer Request" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e41 ">My customer in California wants to know what information we disclose
            to social network partners when I transfer an audience segment from
            Advertising Studio. Where do I find this information?</td>

          <td data-label="Actions to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e44 ">
            <a href="https://help.salesforce.com/articleView?id=mc_ads_get_started_with_advertising_audiences.htm&amp;type=5&amp;language=en_US" target="_blank">Get Started with Advertising
              Audiences</a>
          </td>

          <td data-label="Things to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e47 ">Review social network partners' privacy statements and compliance
            tools, as well as customer's privacy statement. Advertising Studio sends
            data to Facebook and Twitter and presents information to the data
            subject. These social media services act as the data controller.</td>

        </tr>
        <tr class="">
          <td data-label="Common Customer Request" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e41 ">What data fields do you collect in Marketing Cloud Engagement for
            statistical data based on clicks and opens? </td>

          <td data-label="Actions to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e44 ">
            <p style="margin-bottom:0;">Review the column to the right for detailed information about what
              information is collected by Marketing Cloud Engagement application. </p>
          </td>

          <td data-label="Things to Consider" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e47 ">
            <p>Some data that may be collected by click or open in Marketing Cloud
              Engagement for statistics includes:</p>
            <ul>
              <li>IP Address</li>

              <li>Country</li>

              <li>Region</li>

              <li>City</li>

              <li>Postal Code</li>

              <li>Latitude</li>

              <li>Longitude</li>

              <li>Metro Code</li>

              <li>Area Code</li>

              <li>Application used to click to open an email</li>

              <li>The deivce’s operating system used to open an email</li>

              <li>Whether a mobile device is used to open an email</li>

            </ul>
          </td>

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

- General Data Protection Regulation (GDPR), European Union
- California Consumer Privacy Act (CCPA), United States
- Telephone Consumer Protection Act (TCPA), United States
- Canada’s Anti-Spam Law (CASL)
- Personal Information Protection Act (PIPA), Japan

Marketing Cloud Engagement collects different information based on the apps you use.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col style="width:23.474178403755868%">
        <col style="width:76.52582159624413%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d25339e373">App</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d25339e376">Data Collected</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="App" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e373 ">Advertising Studio</td>

          <td data-label="Data Collected" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e376 ">Advertising Studio sends data to Facebook and Twitter and presents
            information to the data subject. These social media services act as the
            data controller.</td>

        </tr>
        <tr class="">
          <td data-label="App" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e373 ">Audience Studio</td>

          <td data-label="Data Collected" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e376 ">
            <ul>
              <li>Three email pixels contained in Audience Studio content capture
                the hashed email address, the subscriber or contact ID value,
                and media content. Audience Studio uses this data for audience
                creation or segmentation.</li>

              <li>A web tracking pixel obtained during login to a web site
                identifies a person. This function treats each different browser
                as an independent login and identifier.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="App" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e373 ">Email Studio</td>

          <td data-label="Data Collected" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e376 ">
            <ul>
              <li>An open pixel determines when an email recipient opens a
                Marketing Cloud Engagement email. Marketing Cloud Engagement
                uses this data for email job statistics and reporting.</li>

              <li>Marketing Cloud Engagement uses link tracking to log information
                about which links the email recipient clicks. Marketing Cloud
                Engagement uses this link tracking data for email job statistics
                and reporting.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="App" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e373 ">Marketing Cloud Engagement Einstein Platform</td>

          <td data-label="Data Collected" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e376 ">
            <ul>
              <li>Einstein imports email templates, standard data tables such as
                data views, some user agent data, and the members_ subscriber
                list. Email content is not imported.</li>

              <li>Einstein imports personalization strings, but not the data
                called by those strings.</li>

              <li>Einstein does not import custom object data or data stored in
                custom data extensions.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="App" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e373 ">GroupConnect</td>

          <td data-label="Data Collected" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e376 ">The LINE messaging service acts as the data controller. Collect
            consent for messaging using the LINE service.</td>

        </tr>
        <tr class="">
          <td data-label="App" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e373 ">MobileConnect</td>

          <td data-label="Data Collected" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e376 ">MobileConnect does not collect this kind of behavioral
            information.</td>

        </tr>
        <tr class="">
          <td data-label="App" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e373 ">MobilePush</td>

          <td data-label="Data Collected" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e376 ">
            <ul>
              <li>MobilePush records the geographic location of a device when the
                customer mobile app is used.</li>

              <li>MobilePush records a message receipt that reports back on the
                messages the data subject received through the customer mobile
                app.</li>

              <li>MobilePush tracks how many times the customer mobile app is
                opened, how long it is used, and other app usage
                statistics.</li>

              <li>Your app must use the latest version of the MobilePush SDK to
                implement Do Not Track functionality.</li>

              <li>If a data subject makes a data compliance request via Marketing
                Cloud Engagement, we send a silent push to the customer app to
                indicate the applicable change. The SDK also makes the customer
                app check in daily for data compliance changes. If Marketing
                Cloud Engagement sends the silent push and the device does not
                process it before the next check-in, the device may not comply
                with regulations until then.</li>

              <li>Mobile app developers can consult the <a href="http://salesforce-marketingcloud.github.io/JB4A-SDK-Android/sdk-implementation/data-privacy-android.html" target="_blank">Android</a> and <a href="https://salesforce-marketingcloud.github.io/MarketingCloudSDK-iOS/sdk-implementation/data-privacy-iOS.html" target="_blank">iOS</a> data protection
                and privacy documents for MobilePush SDK.</li>

            </ul>
          </td>

        </tr>
        <tr class="">
          <td data-label="App" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e373 ">Personalization Builder</td>

          <td data-label="Data Collected" class="slds-cell-wrap" style="vertical-align:top;" headers="d25339e376 ">
            <ul>
              <li>Web &amp; Mobile Analytics records the sites from which web site
                users come.</li>

              <li>Web Recommendations uses a web tracking pixel to track web site
                user behavior. This information only includes links to the web
                site user browsing the web site if that web site user logged
                into that site. Web Recommendations uses the data to provide
                more relevant recommendations for purchase. If the web site user
                does not log into the site, then the data is collected and
                returned anonymously.</li>

              <li>Personalization Builder apps use an in-app interface to deal
                with Do Not Track and Do Not Profile requests from data
                subjects. This action prevents Marketing Cloud Engagement from
                collecting tracking or profiling information on a data
                subject.</li>

              <li>You can make Do Not Track and Do Not Profile preferences
                available in a customer profile center.</li>

            </ul>
          </td>

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

Data protection and privacy compliance can require you to encrypt all data during transit. We recommend taking these steps to ensure compliance.

- To help ensure TLS compliance, use the latest version of your browser and HTTPS addresses to connect to Marketing Cloud Engagement.
- Use OAuth [access token](https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-getting-started.meta/mc-getting-started/get-access-token.htm) authentication for REST and SOAP API calls.
- Follow our [API security best practices](https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/api-security.htm).
- Use [SSL certificates](https://help.salesforce.com/articleView?id=000232477&type=1&language=en_US) for all landing pages.

#### See Also

- [Deliverable Name: DMP Documentation Portal](https://konsole.zendesk.com/hc/en-us/sections/360000109694)
- [Do Not Track Script](https://help.salesforce.com/s/articleView?id=mktg.mc_ctc_do_not_track.htm&type=5&language=en_US)
- [Marketing Cloud Engagement Data Protection and Privacy Tools](https://help.salesforce.com/s/articleView?id=mktg.mc_overview_data_protection_privacy.htm&type=5&language=en_US)
- [Marketing Cloud Engagement Add Contact Preferences REST API Documentation](https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/addContactPreferences.htm)
- [Marketing Cloud Engagement Add Contact Preferences by ID REST API Documentation](https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/addContactPreferencesById.htm)
- [Marketing Cloud Engagement Get Contact Preferences by ID REST API Documentation](https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/getContactPreferencesById.htm)
- [Marketing Cloud Engagement Get Contact Preferences by Key REST API Documentation](https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/getContactPreferencesByKey.htm)
- [Marketing Cloud Engagement Search Contact Preferences by Reference Type REST API Documentation](https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/searchContactPreferencesByReferenceType.htm)