Lead Quality & Segmentation
What this page is — the distribution of lead quality, segmented by grade, source and custom fields, plus a top-leads table.
What it is for — telling whether you are getting better leads or merely more of them.
The problem it solves — volume without quality is not growth. But this report is built on the score, and scoring does not run until somebody makes it — so a page reading zero across the board is the expected state on an untuned tenant, not a fault.
Route: /org/analytics/lead?tab=quality · Permission: Lead Quality & Segmentation
1. What it measures
| Panel | Reads |
|---|---|
| Score distribution | Each lead's score |
| Segmentation | Grades, sources, custom fields |
| Top leads | The highest-scoring leads, with company and value |
2. This report depends entirely on scoring having run
Scoring does not run when a lead is created or updated — only when somebody runs Recalculate on the Scoring Rules tab.
So on a tenant where nobody has, every lead scores 0, the distribution is a single bar at zero, and Top Leads is an arbitrary selection. Nothing on this page indicates that scoring has never been applied.
If this report looks broken, run a recalculate first — but read the warning below before you do.
It derives a grade from each new score and writes it across the project, with no confirmation and no undo. If your team grades leads by hand, a recalculate to fix this report destroys that work.
Verify the rules produce sensible scores on a few leads first.
3. Segmentation by custom field
Segmenting by a custom field only works if the values are stored as an object.
An import or integration that sends custom_fields as text containing JSON, rather than as a JSON
object, stores values that nothing can read back. They appear nowhere here and the segment reads as
unset, even though the values were accepted.
See custom fields.
4. Grade segmentation shows the STORED grade
Unlike the leads list — which recomputes the grade from the score — reporting
reads lead_grade. So this report and the list can disagree about the same lead's grade, and both are
"correct".
5. The admin contract
| Needs | Or |
|---|---|
| Scoring rules that fire | Every score is 0. Section 2 |
| A recalculate having run | Same |
| Grades configured | Grade segments fall back to the built-in default bands |
| Custom fields stored as objects | Custom-field segments are empty. Section 3 |
6. Don't confuse this with…
| This | Not this |
|---|---|
| Grade here — stored | Grade in the list — computed |
| Score | Grade |
| Top leads | Leads most recently created |
7. Troubleshooting
| Symptom | Cause |
|---|---|
| Every score 0 | No recalculate has run. Section 2 |
| Grades disagree with the list | The list computes; this reads stored. Section 4 |
| A custom-field segment is empty | Values stored as a string. Section 3 |
| Top Leads looks arbitrary | All scores are equal, usually 0 |