Cross-Cloud Customer Identity and Data Management for Salesforce B2C Commerce >Manage Customer Data Across Clouds
So What’s the Solution?
Salesforce allows you to fabricate a profile dependent on personal records, records, and contacts, or a blend of both.
With various information displaying alternatives accessible, NTO has its own particular prerequisites for the model it executes here. For instance, some NTO customers are people buying a thing for personal use, and others are business purchasers buying things for an organization. Singular buyers and business purchasers can be similar people; different purchasers can be important for a family that buys a thing.
Pia finds a solution pack that can assist NTO with understanding its information. The pack diagrams how to receive an essential key that endures across the stage. By settling on deliberate decisions about their Salesforce execution information model, Pia exploits out-of-the-container cross-cloud mixes.
You Say, Customer, We Say Person Account
In spite of the fact that Pia has a couple of choices, she is intending to utilize personal records, which consolidate Account and Contact object credits to make an autonomous person without connecting them straightforwardly to a current business account. Person accounts have a couple of benefits.
They work with center item usefulness.
They handle the blending of B2B and B2C connections.
They interface a person’s record to a business contact utilizing a contact relationship.
A person account incorporates two key identifiers, which guide the contact record and record, separately: Account: PersonContactID and Account: ID. Pia will probably plan each customer to one PersonContactID, which is an exceptional, case-unfeeling, 18-digit CRM record ID.
Significantly, Pia has effectively done the majority of the workaround coordinating the Salesforce items that NTO utilizes, including Service Cloud, Marketing Cloud, and Commerce Cloud. These incorporations, which she worked out utilizing the other solution units and Salesforce connectors, permit information from one cloud to be found in another (for instance, permitting specialists to see customer request history from B2C Commerce in Service Cloud).
We should take a gander at the customer identifiers Pia is working with:
Deals Cloud and Service Cloud: The contact record ID is the essential ID across the Salesforce Platform.
Showcasing Cloud: The contact key in Contact Builder is intended to be the cross-channel customer ID.
B2C Commerce: CustomerID is the framework produced ID for a customer, while Customer.Profile. customer is the number that distinguishes customers.
All that is left for Pia to do is to ensure that as she incorporates across clouds, she’s focusing on which fields a guide to which. At the point when she synchronizes the Contact object to Marketing Cloud, for instance, it brings the two records from a personal record (the business account and the person account). What’s more, when she synchronizes the Account object to Marketing Cloud, it guides to the connected contact record.
A) What’s one advantage of using person accounts to manage cross-cloud data?
Click here for Answers
B) What’s one other possible data model for identifying customers across clouds?
- How do you keep up the momentum after your initial mobile rollout?
- When you’re preparing your measures for success, don’t forget:
- You can collect feedback from users by:
- What are some of the benefits of continuous delivery?
- What’s the difference between continuous delivery and continuous deployment?
- What characterizes continuous integration as a development process?
- What’s the benefit of combining B2B Commerce and CRM Data?
- Which functionality is specific to B2B Commerce?
- What do Einstein Product Recommendations do
- With Einstein for B2C Commerce: