--- schema_version: "1" id: 34fa915010b1c38cb988f2466f20a1619e09a28f55c63a82e222f34b80feae7f title: Create Omnichannel Journeys Using Unified Individual Profiles in Data Cloud collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_omni_home.md canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_omni_home.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 66d8e23c29754b8b7eb988789d2a7952e4c2c1d4e46b95e68afc6be4f2e794ab description: Learn how to set up and use audience activations from Data Cloud to power an omnichannel journey in Marketing Cloud Engagement. This guide walks you through an example of how you can enable an omnichannel experience for your customers. 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. products: - Data 360 release: "264" --- # Create Omnichannel Journeys Using Unified Individual Profiles in Data Cloud Learn how to set up and use audience activations from Data Cloud to power an omnichannel journey in Marketing Cloud Engagement. This guide walks you through an example of how you can enable an omnichannel experience for your customers. 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. Before implementing an omnichannel journey, read this guide on [Omnichannel 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.") to understand the required decisions and processes. This solution kit makes these assumptions. You’re creating an omnichannel journey in Marketing Cloud Engagement that contains email, SMS, and MobilePush channels. Your organization has implemented single-channel contacts for Engagement for all three channels but hasn’t implemented omnichannel contacts. ## Use Case 1 Cumulus Bank and Financial Services want to create a 30-day Credit Limit Alert journey for customers approaching or reaching their credit limit. The journey broadcasts a high-priority message on all possible channels to inform customers that they’ve reached their credit limit. Then, the journey follows up with more targeted communications informing customers on whether they qualify for an additional line of credit. To complete this use case, review the features used, permissions required, and associated skills.
   
Products or Features

Data Cloud

  • Activation
  • Activation Target
  • Calculated Insight
  • Identity Resolution

Marketing Cloud Engagement

  • Contact Builder
  • Journey Builder
Roles and Permissions

Data Cloud

  • Data Cloud Architect, Data Cloud Activation Manager, or Data Cloud Activaiton Specialist permission set

Marketing Cloud Engagement

  • Salesforce Marketing Cloud Engagement | General | Access
  • Salesforce Marketing Cloud Engagement | Campaigns | General | Access
  • Contacts | Contact Builder | Administer Contact Model
Requirements or Skills Needed
  • Understanding of activation and activation targets in Data Cloud
  • Understanding of the Contact Model in Marketing Cloud Engagement
  • Understanding Identity Resolution in Data Cloud
  • Understanding of Calculated Insights in Data Cloud
## Related Content To help guide you through these use cases we suggest the following related content. ![second trailhead icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/data_cloud/images/trail_60.png) [_Trailhead_: Data and Identity in Data 360](https://trailhead.salesforce.com/content/learn/modules/data-and-identity-in-salesforce-cdp) ![second trailhead icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/data_cloud/images/trail_60.png) [_Trailhead_: Explore Synchronized Data Sources](https://trailhead.salesforce.com/content/learn/modules/marketing-cloud-contact-management/explore-synchronized-data-sources) ![second trailhead icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/data_cloud/images/trail_60.png) [_Trailhead_: Segmentation in Data 360](https://trailhead.salesforce.com/en/content/learn/modules/customer-360-audiences-segmentation) ![second trailhead icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/data_cloud/images/trail_60.png) [_Trailhead_: Marketing Cloud Engagement Contact Management](https://trailhead.salesforce.com/content/learn/modules/marketing-cloud-contact-management) ![footer image](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/data_cloud/images/SalesforceCDP_Divider-Banner.png) 1. **[Associated Terms for Omnichannel Journeys Using Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_terms.htm&release=264.0.0&type=5)** Review terms that you must know when creating your data foundation. 2. **[Model Your Contact Data for Omnichannel Journeys](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_model.htm&release=264.0.0&type=5)** This solution kit is designed for customers who have implemented single-channel contacts in Marketing Cloud Engagement. Customers who have implemented single-channel contacts in Marketing Cloud Engagement must follow this solution kit to execute omnichannel journeys. Determine whether you’ve implemented omnichannel or single-channel Contacts. 3. **[Omnichannel Journey Solution Workflow](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_workflow.htm&release=264.0.0&type=5)** Review the solution workflow for creating an omnichannel journey in Marketing Cloud Engagement using data from Data 360. 4. **[Stage Your Data in Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_stage.htm&release=264.0.0&type=5)** Customers commonly implement Marketing Cloud Engagement to create many different SubscriberKeys (Individuals) that represent the same person. Such SubscriberKeys are often channel-specific and, as a result, can’t natively execute omnichannel journeys. To build an omnichannel journey, use Data 360 and build a Unified Individual that represents a single person consisting of separate Marketing Cloud Engagement channel-specific SubscriberKeys (Individuals) and contact points. 5. **[Define Match Rules for Identity Resolution and Relate Separate Individuals](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_match.htm&release=264.0.0&type=5)** Let’s review the steps for defining match rules for Identity Resolution and relating separate Individuals in Data 360. 6. **[Define Reconciliation Rules to Prioritize Values for the Unified Individual](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_reconciliation.htm&release=264.0.0&type=5)** Reconciliation rules specify how to select the best value for a Unified field when that field can store only one value, such as a person’s first name. 7. **[Create a Calculated Insight to Select the MobilePush SubscriberKey](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_ci.htm&release=264.0.0&type=5)** Data 360 has numerous controls to select and activate a channel contact point. However, for some scenarios, you must create a Calculated Insight to filter or select a specific channel contact point. For example, Data 360 doesn’t support activating the Email, SMS, and MobilePush channels together. 8. **[Create an Omnichannel Audience in Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_audience.htm&release=264.0.0&type=5)** Let’s review the steps that Cumulus takes to create their Omnichannel audience in Data 360. 9. **[Create a Segment to Qualify the Correct Unified Individuals](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_segment.htm&release=264.0.0&type=5)** Cumulus creates a segment that qualifies the Unified Individuals they want to use for their journey. 10. **[Activate an Audience with Contact Points and Attributes](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_activate.htm&release=264.0.0&type=5)** Cumulus activates an audience with contact points and attributes for their journey. 11. **[Configure Omnichannel Journey Settings in Marketing Cloud Engagement](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_journey_settings.htm&release=264.0.0&type=5)** After the scheduled activation, a data extension is added to the Marketing Cloud Engagement business unit identified in activation. Edit this data extension and update its send relationship to relate the MobilePush Key attribute to SubscriberKey. As a result, Journey Builder defaults all orchestration, personalization, and sending lookups based on the value of the MobilePush Key (representing the MobilePush SubscriberKey selected from the Calculated Insight you created). 12. **[Update the Send Relationship in the Activated Data Extension](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_relationships.htm&release=264.0.0&type=5)** Cumulus updates the send relationship in the activated data extension. 13. **[Configure the Journey Entry to Use the Activated Data Extension Audience](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_configure.htm&release=264.0.0&type=5)** Next, Cumulus configures its journey entry source. 14. **[Configure Omnichannel Journey Settings](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_journey.htm&release=264.0.0&type=5)** Next, Cumulus configures their omnichannel settings. When a journey uses the Omnichannel Credit Limit Alert data extension Entry Source, Journey Builder defaults all orchestration, personalization, and sending lookups based on the value of the MobilePush Key. This Key is represented by the MobilePush SubscriberKey selected from the Calculated Insight. This action enables you to natively send messages using MobilePush activities. 15. **[Add Consent and Preference Filters to Omnichannel Journeys](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_consent.htm&release=264.0.0&type=5)** 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. 16. **[Omnichannel 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.