You are here:
Considerations for Setting Up Einstein Opportunity Scoring
Before setting up Einstein Opportunity Scoring, consider these requirements, limitations, and nuances.
Required Editions
| Available in: Lightning Experience and Salesforce Classic. |
| Available with Sales Cloud Einstein, which is available in Performance and Unlimited Editions, and for an extra cost in Enterprise Edition |
| Available to eligible customers for no extra cost in: Enterprise, Performance, and Unlimited Editions |
Note Einstein Opportunity Scoring is available to users with a Sales Cloud Einstein license and
eligible customers without a Sales Cloud Einstein license.
Data Requirements and Access
- You must have at least 200 closed won opportunities in last 24 months, each with a lifespan of at least 2 days.
- You must have at least 200 closed lost opportunities in last 24 months, each with a lifespan of at least 2 days.
- For each opportunity, the change history records must have at least two records with
open stages, not just those in closed stages. Opportunities with only the final closed
stage, and no open stages in its history, prevent Einstein Opportunity Scoring from
scoring these opportunities. It also prevents from training the scoring model, affecting
all opportunities.
Note If your org doesn’t have its own predictive scoring model, Einstein scores the open opportunities using the global model. - Opportunity history shows an average of one update to each closed opportunity.
- Use the standard opportunity Stage field because it’s used to calculate win rates, and win rates are used to generate scores. If you change the names of the opportunity stage picklist values, make sure that the values are mapped to the correct stage type: Open, Closed/Won. or Closed/Lost.
- If your win rate is extremely high or low, your scores could be skewed. For example, if your win rate is above 90 percent, you could get a large number of opportunities with scores above 90. To avoid skewed scores, make sure that opportunities are set to the correct closed stage. (A win rate is calculated by dividing the last two years of closed-won opportunities by all closed opportunities from that same period.)
- If you don’t have enough opportunity data to build your own predictive model, Einstein uses a global model. The global model uses anonymous data from many Salesforce customers. When you accumulate enough opportunity data, Einstein builds a scoring model with your data and uses the model with the better results.
- After you turn on Einstein Opportunity Scoring, it can take up to 48 hours to analyze your data, build a scoring model, and add scores to opportunities. You can check the status from the Einstein Opportunity Scoring setup page. If Einstein is still analyzing your data after 48 hours, turn off Einstein Opportunity Scoring and then turn it on again, or edit your settings.
- Depending on when you purchased Sales Cloud Einstein, Einstein Opportunity Scoring might be on by default. If it is, scores aren’t available for opportunities that are related to a person account. To get scores on those opportunities, turn off Einstein Opportunity Scoring and then turn it on again.
- If you don’t have any Sales Cloud Einstein licenses but your org meets specific requirements, all users with a Salesforce user license have access to scores on all opportunities. For information about your eligibility, contact Salesforce Customer Support.
Reporting
- Opportunity scores are available in standard reporting and in custom report types. Model factors, which are used to build scoring models, are available in custom report types. For examples, see Create Custom Report Types for Einstein Opportunity Scoring.
Field-Level Security
- For each opportunity score, Einstein shows the factors that have contributed most to the score. The contributing factors that sales reps see alongside opportunity scores are dependent on the reps’ field access. For example, reps who don’t have access to the Amount field don’t see factors that are based on amount. Keep in mind that factors include only field names, not field values. For example, the Amount keeps going up factor doesn’t shows amount values to any users.
Lightning Experience and Salesforce Classic
- In Lightning Experience, we show Not Available when there’s no score. We show Hidden when a score isn’t available because the user has limited access to opportunity scores. In Salesforce Classic , we show a blank value when there’s no score and when a score isn’t available due to limited user access. For details on why there’s no score, see Understand How Einstein Scores Your Opportunities.
- In Lightning Experience, when you use the Opportunity Score field in any type of filtering, use null in the filter criteria (when non-numeric values are allowed) to include opportunities that Einstein hasn’t calculate a score for yet. Use -1 in the filter criteria to include opportunities that don’t have scores because of limited access to opportunity scores. In Salesforce Classic, for the same scenarios use null in the filter criteria (when non-numeric values are allowed).
Did this article solve your issue?
Let us know so we can improve!

