---
schema_version: "1"
id: ee86864eb965b59329f9402195cec4ba2767b839fcb19dfc7886023159baf215
title: Add Consent and Preference Filters to Omnichannel Journeys
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_omni_consent.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_omni_consent.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: feee8e842989f91f84f0c85b817f2b4e1c5c9b66563b83f2c8f3919f4ab0a10d
description: 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.
products:
  - Data 360
release: "264"
---
# 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note Your company’s needs can differ. Review [Data 360 Consent Management](https://help.salesforce.com/s/articleView?id=data.c360_a_consent_management.htm&release=264.0.0&type=5 "Learn more about Consent Management in Data 360.") and [Considerations and Best Practices](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_best_practices.htm&release=264.0.0&type=5 "There are important aspects and trade-offs to consider before implementing this solution. This guide is just one example of how to enable an omnichannel experience for your customers. For example, instead of separate single-channel journeys, users can create seamless customer experiences by using Data Cloud to orchestrate one journey with all Email, SMS, and MobilePush activities together.") 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**.