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
| 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.
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.
- In Account Engagement, go to Prospects | Segmentation | Segmentation Lists.
- Select the public preference segmentation list that you want to import into Marketing Cloud Next.
-
From the Tools dropdown, select CSV Export.
Express Output is recommended.
-
Modify the CSV output file to comply with the import format for Marketing Cloud
Next.
- Create two separate CSV files, one for "opt in" and one for "opt out."
- 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.
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.
-
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
-
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. -
The
updatedAtfield is when the consent was granted, andupdateByindicates the source or user that set the consent. The example format is:Email Consent Date Sample.nulla@Integersem.com 2011-01-10T08:00:00.000Z