Reading your data · 6 min read
Reading Mapping Health
Mapping Health shows where your network's KPIs resolve to each sub-account's GoHighLevel data — and the exact naming mismatches to fix. Only resolving KPIs roll up to the corporate dashboard, so this is the screen that keeps your totals honest.
Video walkthrough coming soon
Dashboard readiness
The first section is a coverage summary that reads "{reporting} of {total} KPIs reporting," and notes any KPIs not yet defined. Each KPI shows either "Not set up" or "{x} of {y} locations reporting," with a colored dot: green for reporting, red for failing, gray for not set up.
A KPI is "reporting" when every synced, applicable location resolves it. "Not set up" KPIs have no rule authored yet and are shown separately — they're never counted as failing.
Findings
The Findings section groups each naming mismatch once across your whole network so you fix it in one place. Each finding card shows the dimension (Pipeline, Calendar, Tag, Stage, Lead source, or Date field), a status of Missing or Needs override, and how many locations are affected.
The card lists what the rule expects and what was Found across your network, tagging each value as a Near match, Not present, or No match. From here you can Add value to rule (for a pipeline, calendar, or date field), Override locations, or copy a canonical name to Standardize in GHL.
When everything resolves you'll see "All KPIs resolving across your network" — every defined KPI resolves to its sub-accounts' data with no mismatches to fix.
The Locations table
The Locations table shows how each sub-account's KPIs resolve. KPIs resolving reads "{resolved} / {total}," where the total is that location's defined, applicable KPIs (it excludes KPIs that aren't set up and ones marked N/A). The Values found column names any KPIs that still need resolving, and Review links back to the Locations screen.
The count only includes KPIs that actually need mapping at that location, so the number always agrees with what you see in the coverage summary.