Lead Analytics and Reports
What this page is — the five reports that sit over Pulse's lead and deal data.
What it is for — answering questions the working screens cannot: which channels convert, where the funnel leaks, how the team is loaded.
The problem it solves — moving from individual records to patterns. It also states plainly which data problems distort every report on the page, because a funnel that does not reconcile with your lead count is usually the data, not the report.
Route: /org/analytics/lead · Module: org_lead_analytics — 8 permissions
Route permission: none — see section 2
1. The five reports
| Tab | Permission | Page |
|---|---|---|
| Lead Overview & Executive Summary | Lead Overview & Executive Summary | Overview |
| Acquisition & Source Insights | Acquisition & Source Insights | Acquisition |
| Pipeline Health & Funnel Analysis | Pipeline Health & Funnel Analysis | Pipeline health |
| Lead Quality & Segmentation | Lead Quality & Segmentation | Quality |
| Team Performance & Engagement | Team Performance & Engagement | Team performance |
Each report's API is gated individually, so a user holding one permission sees exactly one tab. The tab list is built from the permissions you hold.
2. The route has no permission gate
/org/analytics/lead is registered with no required permission — every other Pulse route names one. A
user with no analytics permissions can navigate here, the shell and title render, and then each panel's
request is refused individually.
The result is a page with no tabs and no data rather than a clear Access Denied. This is not a data leak: the five report APIs are each correctly gated, so nothing is exposed. It is a confusing failure.
If a colleague reports Lead Analytics as "broken and empty", check their permissions before their data.
3. Deep links
| Param | Note |
|---|---|
?tab=overview | The default |
?tab=acquisition · pipeline · quality | As named |
?tab=teamperformance | Also accepts ?tab=performance, which is aliased to it |
4. What the reports read
Leads with no status are absent from funnel figures but present in totals, so the two do not reconcile. Imported leads are all in this state.
Leads carrying a lifecycle stage outside the five valid values, created before that value was checked, are miscounted by anything grouping on that field.
Both are described in status, grade and score. Read a funnel here as indicative until the underlying data is clean.
5. The admin contract
| Needs | Or |
|---|---|
| The per-report permissions | The page opens with no tabs. Section 2 |
| Sources on leads | Acquisition cannot attribute |
| Status categories set correctly | The funnel is meaningless |
| Enabled agents | Team Performance has no rows |
| A recalculate having run | Every score-based figure reads 0 |
6. Don't confuse this with…
| This | Not this |
|---|---|
| Lead Analytics and Reports | The Analytics tab inside the leads list |
| The five lead reports here | Timesheet analytics, a separate module with its own permissions |
| Pipeline Health | The deals board |
7. Troubleshooting
| Symptom | Cause |
|---|---|
| Page opens with no tabs | No report permissions. Section 2 |
| Funnel total ≠ list total | Leads with no status. Section 4 |
| Average score reads 0 | Scoring has never been recalculated |
| Team Performance empty | No enabled agents |
| Acquisition shows most leads unattributed | Those leads have no source — common after an import |