Keep these considerations in mind when you use Distributed Marketing with Marketing Cloud Engagement accounts that use tokenized sending.
General Considerations:
- The Distributed Marketing entry source data extensions and personalization data extensions can’t have encrypted fields. This setup is typical.
- Journeys must be configured to use tokenized email addresses and phone numbers. Review considerations for each supported channel for journey configuration changes.
- Sometimes users can't send to new or updated recipients immediately. Contacts, leads, and person accounts (recipients) must be synchronized into Marketing Cloud Engagement and exist on your token server 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 tokenized email address. The email address used for the
recipient is the email address on the Marketing Cloud Engagement contact record. It's 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.
Note If the email address stored in your CRM or Experience Cloud environment is the tokenized email address, you can configure journeys using the standard Distributed Marketing configuration. - 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.
- Ensure that the email address is in your token server. When sending in tokenized environments, Marketing Cloud Engagement doesn’t send to the plain text email address. It sends to the token, which is resolved at send time.
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.Note If the mobile number stored in your CRM or Experience Cloud environment is the tokenized number, you can configure journeys using the standard Distributed Marketing configuration.
- 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 mobile number is in your token server. Similar to an email address, Marketing Cloud Engagement sends to the tokenized number, not the plain-text number.
- Ensure that the tokenized mobile number and Contact Key are opted in before sending. 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.