Reports

Reports in the admin sidebar opens on a 30-day summary (tickets sold, revenue, page views, and how your last mailout delivered) with a card into each report below it. Every report exports as a CSV, named for the report, your venue, and today's date — for example sales-report-yourvenue-2026-08-01.csv; exports respect the filters active on the page, and each download is recorded in your audit log.

The section is visible to admins and managers only — event managers and door roles don't see it. All figures use your venue's timezone, and every chart has a View as table link underneath showing the same numbers as a plain table.

Sales report

The sales report covers a date range you pick (presets from 7 days to a year, or a custom from/to pair) and shows:

• Tickets sold per day and revenue per day as line charts.
• Sales channels — the split between online checkout and the tickets you issued yourself, listed by the channel picked when you made them: complimentary, manual, or phone.
• A per-event breakdown with per-date lines for multi-date events.

Only paid orders count. Pending checkouts and expired holds are excluded, so these figures always match the dashboard and the Tickets pages. Revenue is the ticket price plus any booking surcharge; discounts aren't subtracted here, but the CSV export includes the discount columns so you can reconcile against your Stripe payouts.

Filter the whole report to a single event when you want one show's numbers. Export CSV downloads one row per order (date, event, occurrence, buyer, tickets, revenue, channel, discount and its label, and the UTC order time), honouring whatever range and filter you have active.

Issues report

The issues report is where problems surface:

• Checkout funnel — how many orders were reserved, reached payment, and were paid, with a conversion percentage. Expired holds (buyers who walked away) and failed payment attempts appear alongside.
• Declined payments — each failed attempt with the card network's reason code (card_declined, insufficient_funds, and so on). A declined buyer can still retry; a decline row is an attempt that didn't go through, not a lost sale.
• Open payment exceptions — the "money captured but no tickets" cases. They surface here with a link; you still review and resolve them on the Payments page, and Payment exceptions covers what each flag means and how to refund one.
• Broken links — public pages of yours that visitors requested but that don't exist (for example an event link shared before the event was renamed), with how often and which site last linked there. Security probes and guesses are deliberately excluded — only genuine dead links appear.

Funnel data exists only from the day the feature went live. Both halves export as CSV.

Page views report

The page views report shows traffic on your public pages (home, events listing, event pages, and the checkout), including views that happen inside pages you've embedded on your own website. You get a views-per-day trend, your top pages, a direct-versus-embedded split, and a CSV export.

What Platypus collects, in plain language: when someone loads one of your public pages, Platypus records the page's address, the day, whether it was inside an embed, and the website that linked them (the site name only). It stores no cookies, no IP addresses, and no browser fingerprints — so there's no consent banner, and it works the same inside embeds. "Unique visitors" are estimated per day only: the same person visiting on two different days counts once each day, because nothing links their visits across days.

A few caveats: known crawlers and bots are filtered out, but the filter isn't perfect; your own visits while signed in to the admin aren't counted; and the data starts the day the feature went live, so there's no history before that.

Mailouts report

The mailouts report lists every campaign sent in the range with its delivered and failed counts and a success rate, plus a per-day delivery trend chart. The numbers come from the same per-recipient tracking recorded when each campaign was sent — nothing new is collected.

For any campaign with failures, Failures CSV downloads the failed addresses with their error messages, so you can chase bounces or clean your list.

Audit log (admins only)

The audit log answers "who did what, when": logins, settings changes, event edits, campaign sends, exports, and payment warnings, each with the acting user and time. Filter by level, actor, date range, or message text, and open a row for its full details. The filtered view exports as CSV, and that export is recorded like everything else.

Only the admin account can see the audit log: entries include team members' email addresses and connection details, so managers and other roles don't get access. Entries are kept for 12 months. Anything from before the log existed survives only in the platform's short-lived server logs.

If a number here disagrees with Stripe, your bank, or your own records, don't assume you're misreading it — email support@platypus.tickets with the report name and the date range you had active.