Bookitive
Analytics

Analytics

The organization dashboard and the event's Overview, Sales, and Attendance tabs — date ranges, comparisons, benchmark events, and auto-generated insights.

Not verified yet

Bookitive answers "how are we doing?" at two zoom levels: the organization dashboard across every event, and each event's own Overview / Sales / Attendance tabs. Both read from live data — the numbers you see are the numbers right now.

The organization dashboard

The organization home (Dashboard) is mission control:

  • Attention rows — the things that need you today: paused sales, orders held for review, reservations expiring within 48 hours, refunds queued, a missing billing profile, an overdue invoice.
  • Windowed KPIs — revenue, tickets, and orders across the chosen range, with a revenue-over-time chart. Reserved sits alongside them but reflects the current state — seats held by unpaid reservations right now — so it doesn't move with the date range.
  • Per-event pulse — each event's live occupancy and lifetime revenue, plus the newest orders across all events.

It's where you start the day; the event tabs are where you dig in.

The event dashboard tabs

Inside an event, a shared control bar sits above three tabs:

  • A date range picker, and
  • Compare to — Previous period, Previous year, or a specific benchmark event you search for. The comparison is remembered per event, so your "vs last year" view is one click every time.

The three tabs:

  • Overview — the headline KPIs, revenue chart, alerts, recent orders, and the sales-by-ticket-type breakdown.
  • Sales — the full revenue story: funnel, per-type and per-phase splits, discounts, recovery emails, pace.
  • Attendance — the door: arrivals, no-shows, and scanner throughput.

The Overview tab

The event's front page. Net revenue — gross takings minus refunds — is the headline money number, shown against a global benchmark bar that places this event among your others at a glance. Below it: the revenue chart, alerts, recent orders, and the sales-by-ticket-type breakdown.

The occupancy card leads with seating coverage — seated tickets sold against the total seats on your seat map, so it answers "how full is the room?" honestly and ignores standing capacity and general-admission headroom. A Seats / Full toggle switches to the whole-room number (seats plus standing) when you want it. Events with no seats at all fall back to that full-room figure.

Sales by ticket type counts active (paid) units — not pending reservations — and measures each seated type against the capacity drawn from its seat map.

Throughout the dashboards, sold means currently active: valid tickets on orders that are paid right now. Cancel a paid order or revoke a single ticket and it drops back out of every count — tickets sold, revenue, the sales curve, the per-type splits — even on a day that's already past. (Unpaid reservations never counted in the first place.)

Insights that read the data for you

Across the dashboards, Bookitive surfaces plain-language insights computed from your own numbers — no AI, just arithmetic you'd otherwise do by hand:

  • Sold 64 % of capacity (320 of 500 tickets).
  • At the current sales pace you'll sell out around 11 Aug 2026. (Or: …won't sell out before it starts.) No projection shows in the first few days of a sale, when there's too little pace to trust.
  • In the last 7 days you made 48,000 Kč, 20 % more than the week before.
  • 12 % of valid tickets were never scanned at the door.

And the charts annotate themselves — the highest daily revenue so far, an unusually high day, a gap of days without sales — pinned on the timeline so a pattern never hides in the noise.

On this page