Reports

Buzz ships four built-in reports that let you see how an event is selling, who has shown up, and what add-ons people bought. You run them from the Frappe Desk, filter by event, and export the result to Excel or CSV when you need to share it.

Who can use them

All four reports are available to the Event Manager role. Event Attendance Summary and Event Add-Ons Overview also grant access to the System Manager role, and Event Add-Ons Overview is additionally open to the Buzz User role. Ask an admin to assign you the Event Manager role (see Admin → Roles & Permissions) before you try to open them.

Open a report

Each report lives in the Desk report view. Open it directly by URL or search for its name in the Desk awesome bar:

• Event Overview — /app/query-report/Event Overview
• Event Attendance Summary — /app/event-attendance-summary
• Event Add-Ons Overview — /app/query-report/Event Add-Ons Overview
• Detailed Event Registrations — /app/detailed-event-registrations

Every report has an Event filter at the top. Pick the event, and the table refreshes. Use the menu in the top-right to export the rows to Excel or CSV.

Event Overview

A one-row-per-event summary of how much each event has sold. Use it as your high-level dashboard across all events.

What it shows: for each event, the number of tickets sold, the number of add-ons sold, and the total ticket sales revenue. Only submitted (confirmed) tickets and bookings are counted, so unpaid or draft bookings are ignored.

Filter:

• Event (optional) — leave it blank to list every event, one row each. Pick an event to narrow down to that single event.

Key columns:

Event Attendance Summary

A per-attendee, per-day check-in grid for a single event, with a bar chart and headline counts. Use it after (or during) an event to see who attended and on which days.

What it shows: one row per ticket that was checked in at least once. The first columns identify the attendee; after that, the report adds one column per check-in day found in the data — each shown as a tick box that is checked when that attendee was scanned in on that day. A multi-day event therefore grows extra day columns automatically.

Above the table you get:

• Report summary cards — the attendance count for each day, plus a Total Unique Attendees card (anyone who attended at least one day).
• A bar chart — attendees per day, so you can see how attendance rose or fell across the event.

Only submitted check-ins with a date are included, and rows are sorted by attendee name.

Filter:

• Event (required) — the report stays empty until you choose an event.

Key columns:

Event Add-Ons Overview

A flat list of every add-on purchased for an event — one row per add-on value, tied to the attendee and ticket. Use it to build pickup or fulfilment lists (T-shirt sizes, meal choices, workshop seats, and so on).

What it shows: for the selected event, each add-on value bought against a confirmed ticket, alongside the attendee it belongs to. If an attendee bought two add-ons, they appear on two rows. Only submitted tickets are included.

Filters:

• Event (required) — the event to report on.
• Add-On Type (optional) — limit to a single add-on (e.g. only "T-Shirt").
• Add-On Value (optional) — partial-match search on the value text (e.g. type XL to find all extra-large entries).

Key columns:

Detailed Event Registrations

The most complete export of who registered for an event. It starts with the standard ticket and booking details, then adds a column for every custom form field, every add-on, and every UTM parameter seen for that event — so the exact column set depends on how you configured the event.

What it shows: one row per confirmed ticket. The fixed columns cover the ticket, attendee, booking, and who placed the booking. After those, three groups of dynamic columns are appended:

• Custom fields — one column per enabled custom form field on the event. The value comes from the ticket's own answer if it has one, otherwise from the booking-level answer.
• Add-ons — one column per enabled add-on, showing the value that attendee chose (blank if they didn't buy it).
• UTM parameters — one column per UTM name captured on the bookings (e.g. utm_source, utm_campaign), so you can attribute registrations to marketing campaigns.

Only submitted tickets are included.

Filter:

• Event (required) — the report stays empty until you choose an event.

Key columns (fixed):

The remaining columns vary per event: one each for your custom fields, add-ons, and UTM parameters.