Know who your customers are with the new Audience and Attendees reports
You know how many tickets you sold. You rarely know who bought them.
Age, gender, where they live, how far ahead they book: all of it already sits in your orders and your customer forms. Reading it meant exporting a CSV and building the pivot table yourself, so most of the time nobody did, and the next campaign got targeted on instinct.
That changes today with two new reports: Audience Insight and Attendees.
Both are read at two levels: across your whole organization from Analytics in the sidebar, and on a single event from its Analytics tab. Nothing to set up. They are built from the data you already collect.
What's available:
- 🌍 Where your customers come from. A map and a country-and-city breakdown, built on the address from your customer form rather than the delivery address, so it reflects where people actually live.
- 🎂 How old they are. The average age of your customers, the full age distribution, and the sample size behind the figure, so you know how much to trust it.
- 🚻 Gender split. The same reading on gender, both on the people who pay and on the people who walk in.
- ⏳ Order anticipation. How far ahead of the event your audience actually buys, so you stop guessing when the decision happens.
- 🔁 New versus returning customers. Acquisition over the period, and how much of it comes from people who had already bought from you.
- 🎟️ Attendees, not only customers. One person often buys for four. The Attendees report reads age and gender on the ticket holders themselves, which is rarely the same crowd as the one in your orders.
- 📦 Sales per variant. The Products report gains a panel that breaks sales down variant by variant (size, colour, option) instead of stopping at the product.
- 🏢 Organization-wide or event by event. The same reports at both levels: your whole activity, or the one show you are about to programme again.
Why it matters:
- 🎯 Targeting on facts, not on instinct. Your ad audiences, your mailing segments and your line-up choices can finally lean on who actually bought, not on who you assume shows up.
- 🗺️ Knowing where to play next. The city breakdown tells you which markets already carry you, and which ones you are paying to reach for nothing.
- ⏱️ Opening the sale at the right time. Order anticipation shows whether your audience books three months out or three days out, and your announcement calendar follows.
- 🤝 Something to show partners. Sponsors, venues and media partners ask who your audience is. Now the answer is a dashboard, not a guess.
🎉 The result: the data you were already collecting finally reads as an audience. Who buys, who attends, from where, at what age and how early. Two reports, at organization level and event level, without a single export.
Improvements
Analytics
- Organization-level analytics gained new panels, and an event running several dates is now read across all of its sessions.
Emails
- The delivery status of the order confirmation email is now shown in the Orders table, and the status of the guest invitation email in the Guests table, so a message that never arrived is visible without asking support.
Access control
- The scan status of each ticket (scanned in, scanned out, not scanned) is now visible from the Attendees & tickets page, and can be searched ticket by ticket.
API Platform
- Tickets can be marked as resalable per pricing, and GET /tickets now exposes a transferable property, for resale partners.
- The forms data returned by the endpoints preview no longer repeats the same fields twice.
- The next API release moves from 1 to 15 September.
Fixes
Analytics
- Corrected several figures in the Orders report.
Studio
- Fixed the attendee-data call to action appearing on a sales channel that has no offers.
Payments
- Stripe early-warning fraud notifications are now recognised instead of being logged as unknown events.
