Use Distributed Marketing with Field Level Encryption

General Considerations:

• The Distributed Marketing entry source data extensions and personalization data extensions can’t have encrypted fields.
• Journeys must be configured to use encrypted email addresses and phone numbers. Review considerations for each supported channel for journey configuration changes.
• A value must exist for email addresses and phone numbers in CRM. This value is included in the Distributed Marketing injection payload (API). If the event data extension is configured without the fields (see channel considerations), this value isn’t stored in Marketing Cloud Engagement by Distributed Marketing. Also, this value can be encrypted.
• Recipients including Contacts, Leads, and Person Accounts must be synchronized into Marketing Cloud Engagement before sending through Distributed Marketing. When using synchronized data extensions, Marketing Cloud Engagement polls objects on a configurable interval. This interval is the minimum amount of time a user must wait before sending through Distributed Marketing after adding a recipient. It's also the minimum wait time when updating the email address or mobile number of an existing recipient.

Email Considerations:

• Configure journeys to use the encrypted email address. The email address used for the recipient is the email address on the Marketing Cloud Engagement contact record, not the email address normally seen in the Distributed Marketing entry event data extension. When creating the journey’s event data extension, don't include the email field. When configuring journey settings, set the Default Email Address to Use email attribute from Contacts, and select the appropriate field.
• Configure a unique journey for each object type you support. When synchronizing CRM Contacts, Leads, or Person Accounts into Marketing Cloud Engagement, each is represented as a separate object in Marketing Cloud Engagement Contact Model. If your distributed marketing users send to more than one CRM object, you must configure a unique journey for each object type, where the Default Email Address is selected from the respective object.

SMS Considerations:

• Configure journeys to use the correct mobile number. The mobile number used for the recipient is the mobile number on the contact record, not the mobile number normally used in the Distributed Marketing entry event data extension. When configuring journey settings, set the Default Mobile Number to Use mobile number attribute from Contacts, and select the appropriate field.
• Configure a unique journey for each object type you support. When synchronizing CRM contacts, leads, or person accounts into Marketing Cloud Engagement, each is represented as a separate object in Marketing Cloud Engagement Contact Model. If your Distributed Marketing users send to more than one CRM object, you must configure a unique journey for each object type, where the Default Mobile Number is selected from the respective object.
• Ensure that the tokenized mobile number and Contact Key are opted in before sending through Distributed Marketing. In Distributed Marketing, the Contact Key is the Contact Id or Lead Id in CRM. The Contact Key is represented as the id in the event data extension. The id relates to the subscriber on the Subscriber Key.