---
title: "Event Analytics shows attendance and ticket sales across every event"
url: https://tidyhq.com/blog/event-analytics-attendance-ticket-sales-across-events
date: 2026-09-25
updated: 2026-09-30
author: "Isaak Dury"
categories: ["Product", "Events"]
excerpt: "Events now has an Analytics view that adds up attendance, ticket sales and revenue across all your events, plus repeat buyers and scan-in rates. You can also filter contacts by who bought a ticket versus who actually attended."
---

# Event Analytics shows attendance and ticket sales across every event

> Events now has an Analytics view that adds up attendance, ticket sales and revenue across all your events, plus repeat buyers and scan-in rates. You can also filter contacts by who bought a ticket versus who actually attended.

![Composition N. 1 with Red and Blue by Piet Mondrian, illustrating Event Analytics shows attendance and ticket sales across ev](https://cdn.sanity.io/images/bp0k7h82/production/398c3771f6c0cbcaef6c75face607cfd8cec927d-800x800.jpg?w=1200&fm=webp)

## Key takeaways

- Since September 2026, TidyHQ has an Event Analytics view under Events, then Analytics, that combines attendance, ticket sales and revenue across all events in a chosen date range.
- TidyHQ Event Analytics reports unique attendees, tickets sold, repeat buyer rate, repeat attendee rate and scan-in rate, plus estimated revenue, average revenue per event, average ticket price and refunds issued.
- Revenue in TidyHQ Event Analytics is estimated at current ticket prices, so it will not match payment totals if a ticket price was changed after sales began.
- TidyHQ Contacts filters can now separate the people who bought an event ticket ("Buyer of") from the people assigned to attend ("Attendee of"), including for events shared into the organisation.
- Event Analytics was labelled Beta at launch in September 2026, and results can be exported to CSV.

The committee wants to know whether the new twilight fun run is worth doing again\. The treasurer wants to know how much the season’s events actually brought in, net of refunds\. And somebody at the last meeting asked, quite reasonably, whether the same forty families come to everything\. Until now, answering any of that meant opening each event, exporting each attendee list, and building a spreadsheet the night before the meeting\.

In September we added Event Analytics: one view that adds up attendance, ticket sales and revenue across all your events\. You will find it in **Events**, then **Analytics**\.

## What does Event Analytics show?

Event Analytics shows totals for every event running in the date range you pick, in two panels plus a breakdown table\.

The **Attendance** panel shows unique attendees, tickets sold, repeat buyer rate, repeat attendee rate and scan\-in rate\. Its chart puts each ticket in the month its event ran, split into new attendees \(their first event with you\), returning attendees and cancellations\.

The **Ticketing & revenue** panel shows estimated revenue, average revenue per event, average ticket price and refunds issued\. Its chart follows the money as it moved, so a sale sits in the month it was paid and a refund in the month it was refunded\.

Underneath, the **Breakdown** table lists each event with tickets sold, estimated revenue and how many were scanned, with figures for each ticket type\. **Export CSV** gives you the lot in a spreadsheet for the AGM report\.

![The Attendance panel in TidyHQ Event Analytics, showing unique attendees, tickets sold, repeat buyer rate, repeat attendee rate and scan-in rate beside a monthly chart split into new, returning and cancelled](https://cdn.sanity.io/images/bp0k7h82/production/0c830d41a5872fc68199111f787334931e9e15bf-1360x777.png?w=1200&fm=webp)

*The Attendance panel for a financial year, with a small arrow showing how each number has moved.*

## What is the difference between repeat buyers and repeat attendees?

Repeat buyer rate is the share of ticket holders who held tickets for two or more events in the range, whether or not they were scanned\. Repeat attendee rate only counts people scanned in at two or more events\.

That distinction matters\. If your volunteers do not scan tickets at the gate, the repeat attendee rate will sit near zero and tell you nothing\. The repeat buyer rate still works\. Scan\-in rate is the share of sold tickets scanned at least once, and a ticket scanned at the gate and again at the bar still counts once\.

Every figure has a small info icon that explains exactly how it is counted\. It is worth reading them before you quote a number to the committee\.

## Can I filter by date, event type or organiser?

Yes\. Pick a date range \(This Financial Year is one of the presets\), and filter by event tags if you tag your events, for example “juniors” or “social”\. If your organisation receives events shared from other organisations, you can choose which organisers to include\.

![The Ticketing and revenue panel, showing revenue, average revenue per event, average ticket price and refunds issued beside a monthly bar chart of ticket sales](https://cdn.sanity.io/images/bp0k7h82/production/f1b84c6b2a0561a2f08a75608c53dc7d2c744265-1335x544.png?w=1200&fm=webp)

*Ticketing and revenue follows the money by the month it moved.*

## How do I find who attended versus who paid?

Use the Contacts filters\. Under **Events**, you can now choose **Buyer of** or **Attendee of**, and filter by event, event name, ticket name or event dates\. Buyer of finds whoever paid\. Attendee of finds whoever the ticket was assigned to\.

So when one parent books for three kids, Buyer of finds the parent \(handy for a receipt query\) and Attendee of finds the three kids \(handy for the “bring a water bottle” email or checking junior registrations\)\. Save the filter as a Smart Group and it keeps itself up to date\. This also works for events shared into your organisation, within whatever ticket restrictions the sharing organisation set\.

![The Add Filter menu on the Contacts table with Events selected, listing Event, Event Name, Ticket Name, Event Start Date and Event End Date under both Buyer of and Attendee of](https://cdn.sanity.io/images/bp0k7h82/production/1294cb0e035074ac211790a0dc6325282b113c98-835x874.png?w=1200&fm=webp)

*Buyer of and Attendee of sit side by side in the Events filters.*

On the same theme, the automatic contact group created for each event now includes attendees as well as buyers\.

## Limits and caveats

Event Analytics is labelled **Beta**, and there is a **Share feedback** button on the page\. Tell us what is missing\.

Revenue is an estimate, calculated at current ticket prices\. If you changed a price partway through sales, the figure will not match your payment totals\. For the exact money, use Finances\. Estimated revenue already has refunds and cancelled tickets taken out, so do not subtract refunds again\.

If an event is shared with your organisation for specific tickets only, its tickets are counted but its revenue is hidden\. Events built in the older version of Events are not included\.

Each individual event also has an Overview with its own estimated revenue, refunds and unique attendees, and a link to Event Analytics\. Volunteers using the ticket scanner do not see it, so the gate crew never sees the revenue\.

If you do not scan tickets yet, the [scanning support article](https://support.tidyhq.com/en/articles/15099685-scanning-tickets-at-your-event) is a good place to start, since scan\-in and repeat attendee numbers depend on it\. More on [events](/products/events) and [contacts](/products/contacts), or see the [changelog](/changelog)\.

---
Header image: *Composition N. 1 with Red and Blue* by Piet Mondrian, via [WikiArt](https://www.wikiart.org/en/piet-mondrian)

---
Canonical: https://tidyhq.com/blog/event-analytics-attendance-ticket-sales-across-events | Retrieved from: https://tidyhq.com/blog/event-analytics-attendance-ticket-sales-across-events.md | Published by TidyHQ (https://tidyhq.com)