Within the Einstein Recommendation Builder (ERB), the Data Checker tool displays two columns: Record Count and Required. These columns show whether your org has sufficient data to train an Einstein recommendation model.
The minimum required record counts for the objects used in the Einstein Recommendation Builder are:
| Object | Minimum Required Records |
| Recommended Items | 10 |
| Recipients | 100 |
| Positive Interactions | 400 |
If your record counts fall below these thresholds, the Einstein Recommendation Builder (ERB) will not be able to generate a recommendation model. This article explains how these record counts are calculated.
When setting up the Einstein Recommendation Builder (ERB), you select and associate three types of objects:
The Interactions object must have either a Lookup or Master-Detail relationship with both the Recipients object and the Recommended Items object.
The Positive Interactions record count reflects the total number of records in your selected Interactions object. Einstein Recommendation Builder requires at least 400 Interaction records for the model to train successfully.
For example, if you selected the Interaction custom object, the Data Checker counts all records in that object. If the count is below 400, the Data Checker will show insufficient data.
The Recommended Items record count reflects the number of Recommended Items objects that have at least one related Interaction record. In other words, only items that have actually been interacted with are counted — items with no interaction history are excluded.
Einstein Recommendation Builder requires at least 10 Recommended Items that have related Interaction records.
For example, if you selected Recommended_Items as your Recommended Items object, and Recommended_Items__c is the lookup field on the Interaction object pointing to Recommended_Items, the Data Checker counts only those Recommended Items records that appear in at least one Interaction record.
Note: The Recommended_Items__c field referenced above is a custom Lookup or Master-Detail relationship field on the Interaction object, relating it to the Recommended Items object. Your field name may differ based on your org configuration.
The Recipients record count reflects the number of Recipient objects that have at least one related Interaction record. Similar to Recommended Items, only Recipients with interaction history are counted.
Einstein Recommendation Builder requires at least 100 Recipients that have related Interaction records.
For example, if Recipients is your Recipients object and Recipients__c is the lookup field on the Interaction object pointing to Recipients, the Data Checker counts only those Recipient records that appear in at least one Interaction record.
Note: The Recipients__c field referenced above is a custom Lookup or Master-Detail relationship field on the Interaction object, relating it to the Recipients object. Your field name may differ based on your org configuration.
004052218

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.