KPI mapping · 6 min read
Defining a KPI rule
A KPI's rule decides which records it counts. RollupFox uses the same condition style you already know from GoHighLevel, and the rule you write applies to every sub-account.
Video walkthrough coming soon
Open the rule editor
In a template, find the KPI and click Edit rule. The dialog is titled "{KPI name} — rule" and explains: count the chosen records in the period that match these conditions, with the same rule applied to every sub-account.
Choose what to count
- What to count — Contacts (leads), Opportunities, or Appointments.
- Measure — Count of records, or Sum of value ($) for opportunities (for a metric like Pipeline Value).
Add conditions
Conditions decide which records qualify. Records are kept when they match ANY block below — and within a block, all conditions must match. If you add no conditions at all, the KPI counts all records of that type in the period.
Each condition is a Field, an operator (is or is not), and a value. Available fields depend on the data source:
- Contacts — Tag, Source
- Opportunities — Pipeline, Stage, Status, Source
- Appointments — Calendar, Status
Use AND to require several conditions together in one block, and OR block to add an alternative set. For example: "Tag is customer" OR "Source is Meta." Values autocomplete from what RollupFox has seen across your sub-accounts.
Preview and save
When creating a KPI from the library, a Live preview panel lets you pick a Sample location and Run preview to see how many records match before you commit. Click Save rule (or Save KPI) when it looks right.
KPIs that map by name instead
Some built-in KPIs use a name-based definition rather than a condition builder. For those, use Define & map and fill in fields like Date field, Pipeline name, Stage names, Calendar name, Tag names, or Lead sources. If a KPI reads directly from standard GoHighLevel data, RollupFox tells you it needs no mapping and rolls it up automatically.
"Not set up" vs "N/A"
"Not set up" means a KPI has no rule authored yet — it isn't failing, it just isn't defined. "N/A" (not applicable) means a location needs no name matching for that KPI, so it still rolls up normally.