KPI mapping · 5 min read
Creating a location override
When automatic matching can't confidently resolve a KPI for one sub-account, you tell RollupFox exactly which object to use for that location. An override applies to that location only and immediately brings it back into the roll-up.
Video walkthrough coming soon
When to use an override
Use an override when a location shows Needs override or Missing for a KPI — the automatic match is uncertain or absent, and you want to point it at the right object in that specific sub-account.
Create the override
- 1
Open the KPI's Location matching
In the KPI Template Library, open the template, find the KPI, and click Define & map, then the Location matching tab. It shows a summary like "{n} matched · {n} need override · {n} missing." You can also jump here from Mapping Health using Override locations.
- 2
Click Override on the location
Find the location that isn't matched and click Override. The dialog is titled "Override — {location name}."
- 3
Pick from the live catalog
Choose the matching object from that sub-account's live GoHighLevel catalog — Pipeline and Stages, Calendar, Tags, or Date field, depending on the KPI. Then click Save override.
What the override does
The override stores your chosen object for that one location and marks its mapping as Overridden. It takes precedence over the global rule, counts as a confident match, and the location rolls up into that KPI again on the next sync.
Faster fix for a common name
If several locations use the same alternate name for a pipeline, calendar, or date field, use Add value to rule in Mapping Health instead — it teaches the rule that name once and resolves every affected location on the next sync.