Add Consent and Preference Filters to Omnichannel Journeys

For the email channel, Marketing Cloud Engagement stores consent at the SubscriberKey level and not the email address level. By using the MobilePush Key to send an email to the email address stored in the data extension, Cumulus might have violated their own consent strategy.

For example, in Marketing Cloud Engagement, Cumulus stored email consent for SubscriberKey John.Smith.Email, which is the associated EmailAddress john.smith@example.com in the data extension. However, Cumulus used the MobilePush Key John.Smith.MobilePush to send the EmailAddress john.smith@example.com. Thus, email consent for john.smith@example.com isn’t checked against the record for John.Smith.MobilePush.

Note Your company’s needs can differ. Review Data 360 Consent Management and Considerations and Best Practices for more information.

Cumulus must filter consent for the Email contact points directly in Marketing Cloud Engagement.

1. Drag the required activities onto the canvas for the 30-Day Credit Limit Alert journey.
2. To configure your activities, click the first Email activity on the canvas.
3. Complete the Message Definition and Message Configuration steps.
4. Click the Delivery Options tab.
5. Click Select under Suppression List.
6. Click the Shared Suppression Lists folder.
7. Locate the Unsubscribed list and click Select.
8. Click Summary.
9. Click Done.
10. Complete the rest of the journey configuration, and then click Activate.