what you actually see.
Every figure below is generated sample data for a fake venue, so you can drive the thing before signing anything. It is the real console: the views, the filters, the date range, the compare-to-previous deltas and both CSV exports all work.
The quarter it models includes one deliberately bad week. A console that only ever shows a good fortnight teaches a venue nothing about reading a bad one — so find the slump, and notice that the credits stopped being spent while it was happening.
733
= $7,33019.0 CR/DAY · 38 DAYS LEFT
One credit is one verified person through your door. It is only spent when they scan the code at your counter.
buy creditsEvery delta on this page compares the selected range against the range immediately before it — 30 days against the 30 before those. The balance above does not move with the filter, because a balance is an account fact, not a date-range one.
585
585
$10
2.4x
Every stage is counted in PEOPLE, not pairs — a funnel that switches units halfway is a funnel that can go back up, and then the bar lengths stop meaning anything. Only the last stage costs you money.
683 quests, both halves of each pair. interest-matched to your room, never a blanket blast. free.
71% of sends. a pair accepts together, so this moves in twos. still free.
82% of accepts arrived. still free — being in the room is not the billing event.
585 credits · $5,850. the 213 who came and never scanned cost you nothing.
Check-ins by hour of the week. Useful for one thing: knowing which hours you can afford to send more people into, and which ones you cannot.
Three counts of people, one axis. Credits are not plotted here because credits and check-ins are the same series in different units — drawing both would be two y-scales dressed up as insight.
WHAT IS NOT IN HERE
No names, no contact details, no profiles, no photos, no lookalike export, no cross-venue tracking, and no way to ask for any of it. A venue gets counts. If you want to know who came, ask them at the till like everyone else.