Migrate consent records to Customer Insights - Journeys

When you install Customer Insights - Journeys, the consent center (Customer Insights - Journeys > Audience > Consent center) contains no records, even if you already gathered consent in outbound marketing. You don't need to re-enter contact consent data from outbound marketing if you plan to run journeys in Customer Insights - Journeys for contacts. If you want to reuse contact consent data for leads or profiles, or wish to add new consents, you can use one of three methods:

  • Add new consent records for email and text messages manually by selecting the corresponding option from the top ribbon.

Email and text consent entry screenshot.

  • Import consent settings from an Excel file.

Tip

If you don't see the Import from Excel option in the top ribbon, you might have to select the three dots on the right side of the ribbon to see more items.

  • Load consent information that was already captured for contacts or leads in Dynamics 365 Customer Insights - Journeys.

Important

If you segregate data across business units, you need to load consent from your sources (contacts, leads, and/or subscription lists) into each business unit's compliance profile(s) individually. This will ensure that valid consent records are created for each business unit and compliance profile combination.

The Load consent button loads consent information for email addresses that are stored in contact, lead, or subscription list records in Customer Insights - Journeys and set up in the audience configuration in settings. It's not intended to load consent from other data sources.

The following message appears:

Load consent screenshot.

To load consent from contacts or leads, the following conditions apply:

  1. Only one email address from a contact or lead record is loaded. This field is defined in the Audience configuration and an administrator can change it.
  2. For the commercial purpose, the system checks whether the contact has both the Bulk Email and Email fields set to Allow. If either of those fields is set to Do not Allow, the contact point consent record is set to Opted out.
  3. If you load consent from contacts, new "tracking" consent records are created based on the value in the tracking field on the contact.
  4. If two or more contacts or leads share the same email address, consent for the email is set to Opted in only when all contacts or leads contain the value Bulk email=Allow. In all other cases, consent for the email address is set to Opted out.
  5. If consent for the email already exists in Customer Insights - Journeys, the above-listed rule applies. The email address is only opted in if both email consent values are set to Allow and all consent records from contacts that share the same email address are set to Allow.

Consent loaded from contacts and leads relates to the email set in audience configuration and includes the following fields: Allow email, Allow bulk email, and Allow tracking.

Loading consent allows you to choose the compliance profile and the purpose where the consent should be loaded. Typically, you want to load consent from contacts or leads into the commercial and transactional purposes for the compliance profile with a preference center.

Subscription lists in outbound marketing typically map to topics within a specific purpose. For instance, if you had two subscription lists, you should create two topics within the commercial purpose of your compliance profile and then load consent from the subscription lists directly into the topics.

In addition, if you used outbound marketing subscription lists as "do not email" lists, you can load those records into the topics as "opted out" records to preserve that behavior.

Loading consent from subscription lists doesn't look at the Bulk email or Email fields on the contact or lead. It simply replicates the subscription list membership into the chosen purpose or topic with the selected consent value.

Scenarios

The following example scenarios detail how to load Customer Insights - Journeys consent in different contexts.

Note

Leads do not contain a field for tracking consent, so Customer Insights - Journeys tracking consent records will not be created.

  1. Choose whether you're loading consent from contacts or leads.
  2. Choose the appropriate compliance profile, which is likely a new profile with a preference center.
  3. Choose the purpose that should reflect the Bulk email field. Typically, this is the Commercial purpose if it hasn't been renamed.
  4. Choose the purpose that should reflect the Email field. Typically, this is the Transactional purpose if it hasn't been renamed.

If you managed consent in outbound marketing using subscription lists while also allowing people to opt-out of communications using the Bulk email and Email fields on contacts or leads, this scenario may apply.

  1. First, load consent records from your subscription lists into the topics that replace those lists. This creates the equivalent consent records in Customer Insights - Journeys.
  2. Next, load consent records from either the contacts or leads into the parent purpose of those topics. This ensures that the existing Bulk email and Email field values are respected.

Loading "do not contact" subscription lists

If you have set up a subscription list to track individuals who don't wish to be contacted, you can migrate this data in a couple of ways.

  1. If you have one subscription list that tracks everyone who has opted out of marketing messages, you should load that as "Opted out" into the Commercial purpose of the compliance profile.
  2. If you have one subscription list that tracks everyone who doesn't want to receive any messages, you should load that as "Opted out" into the Commercial and Transactional purpose of the compliance profile.
  3. If you have multiple subscription lists that track individuals who have opted out of specific communication themes or topics, you should load those as "Opted out" into the equivalent topics within the Commercial purpose of the compliance profile.

Important

If you store consent data for contacts in a field other than Allow bulk email, you'll need to use the Import from Excel option to load consent data to the consent center first. Only then will you be able to send commercial email in a journey in Customer Insights - Journeys.

Tip

If you restore data in Customer Insights - Journeys, all consent records will be returned to the state they were in at the time backup was made. This may result in consent data being obsolete. To avoid complications, export all consent data into Excel before starting the restore process and use it as a reference after the restore is completed.

Tip

To migrate consent data, you need to have local access permissions to:

  • Read contact, lead, and subscription list records
  • Create contact point consent records
  • Update contact point consent records

For more information on security roles, visit [Security roles and privileges]/dynamics365/customerengagement/on-premises/admin/security-roles-privileges?view=op-9-1#security-roles)

See also

Grow your business with multi-brand, custom preference centers Customer Insights - Journeys preference centers Outbound marketing compliance settings