In Salesforce Sales Cloud, a lead score segment must meet minimum lead and converted lead counts before Einstein Lead Scoring generates scores for it. Segments can fail this check even when a query on each segment alone shows enough leads, because a lead is counted in only one segment.
This article answers how Salesforce evaluates eligibility for lead score segments, why a segment can fail the check when it appears to have enough leads, and how to fix it.
The Documentation states that to be eligible for scoring, a segment must have 1,000 leads with 120 closed over the last year. However, the system actually starts with a configured default window of 180 days. If the thresholds are not met, it automatically expands the window in multiplied steps (180, 360, 540, and up to 720 days) until either the thresholds are satisfied or all attempts are exhausted.
The assessor counts only the leads already assigned to that specific segment. This means the count is scoped to leads that matched the segment's inclusion filter during crunching. Both the total lead count (minimum 1,000) and the converted lead count (minimum 50 in code, 120 per documentation) are evaluated against this expanding window for each segment independently.
A lead can be assigned to only a single segment. If a lead fits multiple segments, it is assigned to the first one in the segment list. This can cause confusing behavior, especially when you analyze each segment individually.
For example, an org has 2,500 leads and two segments. Querying each segment might show that both have more than 1,000 total leads and 125 closed leads. However, only Segment 1 might pass the requirements to generate scores. If 2,000 leads match Segment 1 and 2,000 leads match Segment 2, the shared leads are all assigned to Segment 1. This leaves Segment 2 with only 500 leads actually assigned to it, so it fails the eligibility check for scoring.
To resolve this issue, you have two options:
005459331

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.