KPI mapping · 6 min read

How KPI matching works across locations with different naming

Every sub-account names things differently — one calls it "Sales Pipeline," another "New Deals." RollupFox matches your one corporate KPI to whatever each location actually calls it, and clearly flags anything it can't match with confidence.

Video walkthrough coming soon

Watch: how matching resolves names per location and what gets flagged.

What matching does

When a location syncs, RollupFox compares your KPI's expected names (the pipelines, stages, calendars, or tags in its rule) against that sub-account's live GoHighLevel catalog, and records the result for each location.

The possible outcomes

Matched
RollupFox found an exact name match (or you set an override). The location rolls up into that KPI.
Needs override
There's a close match but not an exact one — for example "Sales Pipeline" vs "Sales - Pipeline." RollupFox surfaces the closest candidate as a near match and asks you to confirm it with an override.
Missing
No close match was found, or the sub-account has no pipelines/calendars/tags of that kind at all.
Not defined
The KPI's rule doesn't specify what to look for yet (for example a tag KPI with no tags set).
N/A (not applicable)
No name matching is needed for this KPI at this location, so it rolls up automatically.

How the match is scored

RollupFox scores each candidate name for similarity to what your rule expects. An exact match scores highest and resolves automatically. A close-but-not-exact name is offered as a near match for you to confirm. Names that aren't similar enough aren't proposed, so you don't get false matches.

Why this protects your numbers

Only locations that are Matched (or N/A) roll up to the corporate dashboard. A location that Needs override or is Missing is excluded from that KPI — its data is held out, not counted as zero — so a naming mismatch never quietly deflates a total.

You resolve flagged matches in one of three ways: add the found name to the rule so it matches everywhere, create a per-location override, or rename the object in GoHighLevel. The next two guides cover the first two.

Related articles