Event Overview
Help articles may not be fully accurate — they can lag behind the app due to frequent updates and automated translation. If in doubt, please contact support.
On this page
Event Overview is the dashboard you land on after opening Manage for an event: at-a-glance numbers, ticket sales, recent bookings, lifecycle controls and the Event Intelligence readiness panel. Everything else in the manage area is reached from the sidebar this page also renders.
What is on this page
- Status badge and lifecycle buttons — the header shows the event's current status and one button per status it is allowed to move to next (see Lifecycle below). Pausing and cancelling ask for confirmation first; the others act immediately.
- Preview / Public page link — opens the live public event page once the event is Live; for anything else it opens an authenticated preview so the link never 404s while you are still setting up.
- Stat cards — confirmed bookings, pending bookings (dimmed at zero), total revenue, tickets sold and tickets available. Confirmed bookings, pending bookings and revenue each link straight into Orders (pre-filtered) or Reports.
- Ticket type breakdown — sold/capacity and a progress bar per active ticket type, plus a line for tickets sold against a ticket type that has since been deleted, so the numbers still add up to the total.
- Recent bookings — the five most recent, with a link to the full Orders list.
- Event Intelligence panel — see below.
- AI Tools — Analytics Insight, FAQ Generator and Staff Briefing, shown only when AI features are enabled for the platform.
Event lifecycle from here
| From | Buttons shown |
|---|---|
| Draft | Schedule, Go Live |
| Scheduled | Go Live, Cancel Event |
| Live | Pause, Cancel Event, Mark Complete |
| Paused | Go Live, Cancel Event |
| Completed / Cancelled | none — both are final states |
- Going Live on an event that has any ticket priced above zero is blocked until Stripe Connect is verified — the button shows an error instead of switching status.
- Cancelling triggers an automatic refund of every confirmed booking and notifies attendees; this cannot be undone from here.
- There is no button to send a Scheduled, Live or Paused event back to Draft — Draft is only ever a starting state.
Event Intelligence: the readiness score
The violet ring is a weighted completeness score across six checks: description and image present (basics), a venue or online link (location), at least one active ticket type, checkout questions, a discount code, and at least one task — plus whether the event is published. Basics, location and tickets are critical: until all three are done, the “Ready to publish” button beside the ring does not appear, whatever the numeric score says.
- Each unticked check links straight to the screen that fixes it.
- Below the ring, up to three live recommendations surface time-sensitive issues — pending payments awaiting confirmation, sales running slow with the event date approaching, or a near-sold-out ticket type — each with a one-click action. “Open Command Center” shows the rest.
- The score only reflects what is on the event; it is not a prediction of ticket sales.
Good to know
- This page does not use the shared tab-strip layout the other manage pages use — it renders its own header and sidebar, so the section tabs you see on Information/Schedule/Pricing and similar pages do not appear here.
- The lifecycle buttons only appear if you hold the publish permission for the event; without it you see the status badge but no action buttons.
- “Tickets sold” and the per-type breakdown can disagree briefly after a ticket type is deleted while it still has confirmed sales — the difference is called out as a separate “removed ticket types” line rather than silently dropped.
Troubleshooting
- Go Live shows an error instead of publishing — a ticket on this event is priced above zero and Stripe Connect has not been verified yet.
- There is no lifecycle button at all, only the badge — you (or your team role) do not hold the publish permission for this event.
- The readiness ring is high but I still cannot publish — check the three critical items specifically (basics, location, tickets); a high score can still be missing one of them if the non-critical checks are all done instead.
- Revenue looks lower than expected — it only counts confirmed bookings; pending ones are shown separately and excluded until confirmed.