Cross-Cloud Customer Identity and Data Management for Salesforce B2C Commerce -Enable Unified Customer Identity
What Products Does This Solution Require?
To execute this solution, NTO needs:
Community Cloud
Salesforce Identity
B2C Commerce
NTO likewise needs these licenses for their customers:
Community Cloud
Salesforce Identity
Pia surveys the work process graph remembered for the solution kit to perceive how Community Cloud, Salesforce Identity, and Salesforce B2C Commerce cooperate to make customer profiles and use them for confirmation.
Work process graph telling the best way to incorporate clouds to make a unified customer profile
The work process graph shows what happens when a customer makes another profile or explores the B2C Commerce retail facade in various situations. At the point when the customer pursues a record in the community, Salesforce Identity makes the profile and stores it in Community Cloud. At the point when a customer pursues a record in the retail facade, B2C Commerce passes the data to Community Cloud, which prepopulates data and passes it to Salesforce Identity for profile creation. Afterward, when the customer explores the retail facade, Salesforce Identity verifies the login, and B2C Commerce makes a stub record and updates the customer profile with cross-cloud identifiers.
Pia noticed that each cloud keeps a profile creation and alteration work process. She checks the solution kit and sees that this plan guarantees that important cross-cloud identifiers are remembered for each profile.
Set Up Community Cloud and B2C Commerce for Cross-Cloud Identity
Since the NTO planners have a concluded arrangement, they begin working with community and retail facade administrators to set up Community Cloud and Salesforce B2C Commerce to help cross-cloud identity. Since NTO previously set up the Salesforce B2C Commerce to Service Cloud Connector, and the connector upholds individual records out of the container, the group utilizes individual records rather than contact records to set up Community Cloud clients.
B2C Commerce administrators design Salesforce Identity as an OAuth2 supplier so customers can sign in with a solitary arrangement of certifications to the community and the retail facade. Despite the fact that center customer profile information is put away in Community Cloud, B2C Commerce likewise keeps a stub and shadow record to address the customer. Profiles in each cloud incorporate cross-cloud identifiers, which interface them together.
To carry out Embedded Login, the community administrator and customer-facing facade web engineer cooperate to make a login page with NTO marking and an associated application to deal with client logins and keep up the association between the community and retail facade site.
A) After NTO implements unified cross-cloud identity, which type of customer data is stored in Community Cloud?
Click here for Answers
B) True or False: In NTO’s Embedded Login solution, a connected app maintains the connection between the community and storefront site after the user logs in.
- 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:
