Plan Your Implementation
Learning Objectives
After completing this unit, you’ll be able to:
- List the general steps you take to implement Commerce Cloud Einstein.
- List three features that you can test after data enablement.
- Describe the methodology that makes the best use of data.
Introduction
Implementing Einstein is a team effort. An implementation team includes a B2C Commerce administrator, a developer, and a merchandiser. Each role is responsible for specific tasks throughout the process.
Here’s a list of the general steps it takes to implement the Einstein features.
- Enable the data in the Einstein Status Dashboard in Business Manager (admin).
- Modify the templates (developer).
- Create custom recommenders in the Configurator (merchandisers).
- Configure the content slots in Business Manager to specify the template and choose the exact recommender that displays the products on the storefront (merchandisers).
- Go live (all).
- A/B Test and add recommenders throughout the site (merchandisers).
Enable the Data
In the previous unit, you learned that Einstein uses different forms of data for the storefront. Einstein collects data and uses data that’s already collected.
Einstein only runs on the primary instance group (development, staging, and production) for feature activation and testing. Einstein only collects data on a production instance where shoppers look and buy. A sandbox instance is not involved.
These are the Einstein data feeds.
- One-time historical order feed
- Daily order feed
- Daily product feed
- Commerce Insights
- Einstein Search Dictionaries
The Administrator uses the production instance of Business Manager to collect credentials, and schedule the catalog and order feed from the Einstein Status Dashboard.
Clickstream Data
Einstein captures real-time clickstream data and uses it in the Einstein algorithms.
Here’s how you set up Einstein to use clickstream data.
- In Business Manager, click the App Launcher and then select Merchant Tools | Site | Site Preferences | Privacy Settings.
- Enables the clickstream data.
After data enablement, these features are ready to test without development effort or quality assurance.
Develop Templates
The developergathers requirements and comp designs so they can create or modify the storefront page templates. When finished, the Product Recommendations template is ready to test.
For Predictive Sort, the developer validates that the cache is invalidated on category and search grid pages if Predictive Sort is activated. (See the If Attribute Example section on the Infocenter iscache page for more details.)
For Einstein Search Recommendations, the developer’s tasks depend on your goals. The merchandiser can enable personalized auto-correction and term completion instantly in Business Manager. Developer effort is only required for optional enhancements, such as configuring the search flyout to present available options to the shopper that are specific to popular searches, and recent searches. A developer is also needed to extend the functionality of the search flyout. To learn more, take a look at Feature versus Effort in the Set Up Search Recommendations module.
Configure Recommenders
Merchandisers use Configurator to create recommenders, a set of rules and strategies used by Product Recommendations. Recommenders tell the storefront to display recommendations based on Einstein data.
The Commerce Cloud Recommendation Validator (Chrome Extension) validates recommendation activities on the storefront.
When the merchandiser completes these steps, Product Recommendations is ready to test.
Review Einstein Revenue
Merchandisers can monitor the Einstein Dashboard in the Commerce Cloud Reports and Dashboards software to compare Einstein attributed revenue relative to overall site revenue and share with his managers.
Put the Data to Work
After Einstein Recommendations are live on your production environment, start developing a test-and-learn methodology. You can use the A/B testing tool in Business Manager or a tool from a third-party platform. For an in-depth review of your A/B Test results, consult with your Commerce Cloud Customer representative.
Sample Einstein Implementation Timeline for Sites Going Live on B2C Commerce
Here are the steps to enable and implement Einstein on a storefront.
Step | Type | Description | Role(s) |
|---|---|---|---|
1 | Plan | Review the site readiness assessment (SRA). Define feature scope and agree on development steps. | Partner/developer, business user |
2 | Plan | Define content slots and assets for Product Recommendations. | Partner/developer, business user |
3 | Plan | Meet to clarify technical questions around Recommendations styling and search functionality. | Functional architect, business user |
4 | Develop | Update or create search flyout, storefront template code, and slot rendering. Ensure they follow Einstein best practices for Product Recommendations. | Partner/developer, business user |
5 | Deploy | Begin activation of Einstein after the site is on the production instance of Business Manager, with a catalog assigned that has products with inventory.. | Administrator |
6 | Deploy | Ensure the Merchandiser’s email addresses have been set up in B2C Commerce Account Manager. | Administrator |
7 | Deploy | Request Configurator access for yourself and (optional) login credentials SFTP External/Store order feed credentials from Support. | Administrator |
8 | Deploy | Wait 24-48 hours for the initial data deployment to complete. | Administrator |
9 | Deploy | Log a ticket and request that Salesforce Support adds the initial Site Admin user to the Configurator tool. | Administrator |
10 | Deploy | (Optional) Send external order data via SFTP if there is external store data that you want factored into Einstein. | Developer/Support |
11 | Deploy | After the site admin user is provisioned, access the configurator tool and add Merchandiser’s email address with user access. | Administrator |
12 | Test | Validate in staging:
| Partner/developer |
13 | Run | Commerce Cloud Einstein goes live. | Team |
14 | Run | Review best practices with the Merchandising team. | Merchant |
15 | Run | Create A/B tests to measure success. | Merchant |
Next Steps
In this unit, you learned the rolesinvolved in Einstein enablement and implementation for a site going live on Commerce Cloud. Next, explorethe effort required to implement specific features.
Resources
- Trailhead: Commerce Cloud Features
- Developer Center: iscache Element
- Trailhead: Smarter Search with Commerce Cloud Einstein
