Connect Multiple Orgs with Data Cloud One
Learning Objectives
After completing this unit, you’ll be able to:
- Identify Data Cloud One benefits.
- Learn Data Cloud One best practices and use cases.
- Explain next steps for getting started with Data Cloud One.
Data Cloud One is a pilot or beta service that is subject to the Beta Services Terms at Salesforce.com | Legal Agreements or a written Unified Pilot Agreement if executed by Customer, and applicable terms in the Product Terms Directory. Use of this pilot or beta service is at the Customer’s sole discretion.
What Is Data Cloud One?
As your company grows, your business needs grow as well. You might create different Salesforce orgs for different departments, regions, or brands, or inherit them as part of an acquisition. And data about the same customer can end up stored in multiple orgs. It’s great to have all that data, but it’s more valuable if every part of your business can access a single view of each customer.
Standard Salesforce CRM connections let you ingest data from many orgs into Data Cloud where it’s unified in the Data Cloud home org. The home org is the primary org where Data Cloud is provisioned and managed. But connected orgs can’t directly access unified data. To make use of unified data in connected orgs, you have to rely on data actions to trigger flows in connected orgs based on the Data Cloud data, or set up complicated custom-coded solutions. Or you have to provision, set up, and maintain a Data Cloud on every org. That sounds time-consuming and expensive!
Data Cloud One makes accessing a single Data Cloud across multiple orgs a snap. Orgs connected through a Data Cloud One companion connection are called companion orgs. On top of ingesting data through a standard connection, users in companion orgs also have access to a subset of Data Cloud functionality in the Data Cloud One app. Companion org users can see a complete view of their customers from unified profiles, build custom flows on unified data, directly access calculated insights, and optimize business processes for their use case by powering CRM platform features with Data Cloud.
Benefits of Data Cloud One
When connecting an org to Data Cloud, you can choose between a standard connection and a Data Cloud One companion connection. Let’s compare the benefits of each.
Access to Data Cloud Data
Companion orgs can access Data Cloud metadata, objects, and records in shared data spaces. Data spaces are logical partitions of data within Data Cloud. You can invest in enhanced data security by using Data Cloud data spaces to organize and govern shared data. Standard connections don’t grant access to Data Cloud data and data spaces.
Access to Data Cloud Features
Companion orgs can access some Data Cloud features in the Data Cloud One app, such as calculated insights and Data Explorer. You also have access to platform features powered by Data Cloud, such as Flows. Standard connections don’t let you access Data Cloud features and platform features powered by Data Cloud.
Your Sales Reps’ Use Case
The sales reps at your company are always looking for ways to improve their sales. They have an idea to create a calculated insight that ranks customers by spending in different product types. They can use this data to create a promotional marketing campaign to select customers using Einstein. You might have different Sales orgs for each product line, so data on customer spending and product sales is scattered across several orgs. The sales reps need to ingest it into the home org with a standard connection. Then, they’ll ask the home org admin to make the calculated insight. Finally, the sales reps can create custom code to pull the results into their Marketing org where they can kickstart the campaign. It’s complicated and time-cosuming, and with their busy schedules they’re not sure when they can get this done.
Fortunately for your sales reps, you just set up Data Cloud One. Now they get a single view of their customer, with all of their information, in every org they log into. Your sales reps can create calculated insights right in their Marketing org. They can also power an AI-driven campaign using the single source of truth in the home Data Cloud org. You save time and gain even more return on your investment.
Best Practices
Keep these best practices in mind when considering Data Cloud One.
- Consult your legal department before connecting orgs across different regions. All data in companion orgs becomes resident in the region of the home org, which could create data residency issues.
- Confirm that your long-term growth objectives support the decision to implement a single Data Cloud instance. If you foresee significant growth in one area, consult your data architecture team to discuss provisioning a separate Data Cloud instance for that org.
- Assess whether all orgs require complete control over their data and Data Cloud configurations. If so, creating multiple Data Cloud orgs is advisable. However, if you want to centralize control across orgs and minimize data silos, connect multiple orgs to a single Data Cloud.
Get Started with Data Cloud One
When you’ve decided that Data Cloud One is the right fit for your business, follow these steps to get started.
- Make sure your orgs you want to connect don’t have Data Cloud provisioned in them or a companion connection to another Data Cloud.
- Plan your data space strategy. Which data spaces will you share with each companion org?
- Connect the companion org to the home org.
- Share data spaces and sync metadata.
Now your users across all connected orgs can access a single source of truth through Data Cloud, and use Data Cloud for their specific needs.