Analytics
See what's happening, without an export.
The dashboard reports on the programme itself: who is showing up, how far they get, and what moves. Per environment, one range at a time.
Four sections, one range
Seven, thirty or ninety days. One switch moves all four.
Each section is its own tab, and only the open one fetches, so looking at streaks never pays for a funnel you did not ask about.
| Section | What it shows |
|---|---|
| Active players | Distinct players, daily, weekly and monthly, plus one count for the chosen range. |
| Mission funnel | Occurrences seen, opt-ins and completions, per mission. |
| Streaks | How many customers are on a run right now, and how every ended run ended, by length. |
| Marketplace | Units sold and points spent, by day. |
How it counts
Four numbers, and none of them are the same kind of thing.
- Daily, weekly and monthly do not add up. A player who returns twice in a week is one player in the weekly figure and two in the daily one, on purpose.
- The range figure is the billing one. It is a separate read, ending today rather than yesterday, and it is the number a Live invoice is written from.
- A run only counts once it breaks. The length histogram grows when a streak ends; how many are live right now is a second, separate read.
- UTC, not local. A day boundary that followed your own clock would ask some players for tomorrow before their today had finished.
What this will not do
Points already have a screen. This is not a second one.
The economy chart lives on the points screen, next to the balances it is understood against. A second copy here would just be two homes for one job.
It is not a BI tool either. It answers whether a mechanic is working, not what that did
to revenue, because revenue is not an event we were sent.
Tell us which number matters first.
We will show you where it lives in the dashboard, and what it looks like once your programme has a week of activity behind it.