KPI row
Put 1 to 6 single-value metrics side by side in one widget, each with its own event, aggregate, and delta.
A KPI row is one widget that shows several single-value counters next to each other. Instead of adding four separate metric widgets just to see four numbers, you put them all in one tidy row. Each number is its own little metric with its own event and aggregate, so you can mix unrelated figures (new players, revenue, average order value) in a single tile.
When to use it
Reach for a KPI row when you want a quick "scoreboard" at the top of a dashboard: the handful of headline numbers you glance at first. If you only need one number, or you want to plot it over time or break it down, use a metric widget instead.
How each KPI works
A KPI row holds 1 to 6 metrics. Each one is configured on its own:
Prop
Type
The aggregates you can pick
These are the same aggregates a metric widget uses.
count is the only one that needs no property; every other aggregate needs you
to point it at a property to work on.
| Aggregate | What it does | Needs a property? |
|---|---|---|
count | Counts matching events | No |
sum | Adds up a numeric property | Yes |
avg | Averages a numeric property | Yes |
min | The smallest value of a numeric property | Yes |
max | The largest value of a numeric property | Yes |
uniq | Counts distinct values of a string property | Yes |
Blanks never skew the number
For any aggregate other than count, events that are missing the chosen
property are simply left out. A missing value never gets counted as zero, so it
cannot drag an average or a sum around.
The delta
Every KPI item also shows a delta: a small up-or-down figure comparing the current window against the window of equal length right before it. If your dashboard time range is the last 24 hours, each number is compared with the 24 hours before that, so you can see at a glance whether things are up or down.
The delta is hidden when the previous window was zero. There is nothing meaningful to compare against, so TopStats shows the number on its own rather than an impossible percentage.
Example row
Say you run a game and want a single scoreboard tile. A five-item KPI row could
look like this, all pulling from your player_join and purchase events:
| Label | Event | Aggregate | Property |
|---|---|---|---|
| New players | player_join | count | (none) |
| Purchases | purchase | count | (none) |
| Revenue | purchase | sum | amount |
| Avg order value | purchase | avg | amount |
| Countries | player_join | uniq | country |
That gives you five headline numbers side by side, each with its own delta, in one widget at the top of the dashboard.