--- schema_version: "1" id: ade3b6d6ab4295c841ac24a5300b844cfb2d894d0e6f8fb3c51dfb15c00c5859 title: Manually Match Consent and Subscriptions Between Account Engagement and Marketing Cloud Next collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mcae_mc_campaigns_consent.md canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mcae_mc_campaigns_consent.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 3f38ca925a14f666c0a075394fc517c917ed4ecd4641742738d85329544ed9cc description: Marketing Cloud Next consent management is powered by Data 360 so that you can manage multiple marketing channels with subscriptions. By default, consent isn’t shared between Account Engagement and Marketing Cloud Next. To use your prospect consent preferences in Marketing Cloud Next, export them from Account Engagement or API, and then import them into Marketing Cloud Next, one subscription at a time. The resulting output file includes prospects that need a corresponding subscription in Marketing Cloud Next. We recommend using a small, simple subscription to start. products: - Marketing - Marketing Cloud Account Engagement release: "264" --- # Manually Match Consent and Subscriptions Between Account Engagement and Marketing Cloud Next Marketing Cloud Next consent management is powered by Data 360 so that you can manage multiple marketing channels with subscriptions. By default, consent isn’t shared between Account Engagement and Marketing Cloud Next. To use your prospect consent preferences in Marketing Cloud Next, export them from Account Engagement or API, and then import them into Marketing Cloud Next, one subscription at a time. The resulting output file includes prospects that need a corresponding subscription in Marketing Cloud Next. We recommend using a small, simple subscription to start. ### Required Editions ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-pardot-264-0-0-production-enus/5fef4d4f-9a34-45c6-8cd3-e3200b9eeba8/images/icon_note.png) Note To automatically match overall email consent between products, [turn on the consent matching tool in your Account Engagement business unit](https://help.salesforce.com/s/articleView?id=mktg.mcae_match_email_consent_with_marketing_cloud.htm&language=en_US). Consent matching doesn't support Marketing Cloud Next subscription-level consent.
Available in: Salesforce Enterprise and Unlimited Editions with Account Engagement Growth, Plus, Advanced, and Premium Editions, along with Data 360 or Marketing Cloud Next editions.
## Considerations for Consent When preparing to use your Account Engagement consent and subscription preferences in Marketing Cloud Next, keep these considerations in mind. - To minimize the risk of missing opt-out requests, market to a subscription within either Account Engagement or Marketing Cloud Next, but not both. While subscriptions live only in one system, to ensure compliance, customers can opt out of all marketing between the systems. - Exporting from Account Engagement includes converting opt-in and opt-out consent signals for Account Engagement subscriptions and preferences into a single consent signal for the subscription. It also includes selecting a date for when consent started. The consent-given date isn’t captured from Account Engagement as records are imported into the system. Therefore, you select the best date for when consent started, such as the Last Updated date. - Marketing Cloud Next, consent is managed only via subscription preferences. In Account Engagement, if a user opts out via email, they’re opted out of all email communication. But if a user opts out at the preferences level, they’re opted out of the subscription email as follows: - If an email is opted in but no subscriptions are opted in, the person isn’t opted in to any subscription imported to Marketing Cloud Next. - If an email is opted out, but the user is opted in to subscriptions, the person isn’t opted in to any subscription imported to Marketing Cloud Next. To learn more about consent in Marketing Cloud Next, see [Understanding Consent Concepts in Marketing Cloud Next](https://help.salesforce.com/s/articleView?id=mktg.mktg_consent_tools_ref.htm&language=en_US). ## Export Subscription Preferences Using the Account Engagement App Export the preference list for the Account Engagement subscription that you want to import into Marketing Cloud Next. 1. In Account Engagement, go to **Prospects** | **Segmentation** | **Segmentation Lists**. 2. Select the public preference segmentation list that you want to import into Marketing Cloud Next. 3. From the Tools dropdown, select **CSV Export**. Express Output is recommended. 4. Modify the CSV output file to comply with the import format for Marketing Cloud Next. 1. Create two separate CSV files, one for "opt in" and one for "opt out." 2. Edit the CSV output files by removing all columns except Email and Updated. Filter out “opted out” and “do not email” entries. For more information, see [Formatting Marketing Consent Import Files](https://help.salesforce.com/s/articleView?id=mktg.mktg_consent_import_format.htm&language=en_US). ## Export Subscription Preferences Using the REST API Instead of exporting from the UI, a developer can export the members of a preference list via Account Engagement API. Use the list membership endpoint for this process. See [List Membership Object](https://developer.salesforce.com/docs/marketing/pardot/guide/list-membership-v5.html). 1. Query the list membership endpoint with the preference list ID and request these fields. - prospect.email - prospect.optedOut - list.name - optedOut - isDeleted - updatedAt - updatedBy.name 2. Filter the list with the conditions needed to subscribe in Marketing Cloud Next. For example, `If (optedOut = FALSE & prospect.optedOut = FALSE & isDeleted = FALSE)`, then you can conclude that the list member is safe to import as opted in to the same Marketing Cloud Next subascription. The conditions ensure that the prospect’s email is opted in, the prospect hasn’t opted out of the list, and the value is current. 3. The `updatedAt` field is when the consent was granted, and `updateBy` indicates the source or user that set the consent. The example format is:
EmailConsent Date
Sample.nulla@Integersem.com2011-01-10T08:00:00.000Z
## Import Subscription Preferences into Marketing Cloud Next Import the subscription preferences CSV file for each subscription into Marketing Cloud Next. See [Import Consent Data to Marketing Cloud Next](https://help.salesforce.com/s/articleView?id=mktg.mktg_consent_import_create.htm&language=en_US). #### See Also - [_Knowledge Article_: Understanding Consent Differences Between Account Engagement and Marketing Cloud Next](https://help.salesforce.com/s/articleView?id=005225288&type=1&language=en_US) - [Automatically Match Email Consent Between Account Engagement and Marketing Cloud Next](https://help.salesforce.com/s/articleView?id=mktg.mcae_match_email_consent_with_marketing_cloud.htm&release=264.0.0&type=5 "To align email consent automatically between Account Engagement and Marketing Cloud Next, turn on consent matching in your Account Engagement business unit. You can match consent for specific lists, or for all emails based on each prospect’s Opted Out field.") - [_Salesforce Help_: Understanding Consent Concepts in Marketing Cloud Next](https://help.salesforce.com/s/articleView?id=mktg.mktg_consent_tools_ref.htm&language=en_US)