Event Tickets
Report Guide for Users
What this report shows, the choices you make when running it, and how to read each section.
What this report is for
The Event Tickets report lists every ticket tied to an event booking within a date range, along with whether each ticket has been scanned/used. It's useful for checking attendance, reconciling ticket counts against a booking, and spotting tickets that were never scanned in.
How the report works
You choose a date range based on when the event starts. The report then pulls every ticket associated with bookings in that window, and lets you narrow the results by ticket type, whether the ticket has been consumed (scanned), and whether the ticket was deleted.
A ticket with "Not Specified" as its type simply means no ticket type was assigned to it.
The choices you make when running it
These are the settings available. Everything else is calculated automatically.
1. The time period
| Setting | What it does |
|---|---|
| Event Start Date | The beginning of the date range you want to report on, based on the event's start time. |
| Event End Date | The end of the date range you want to report on, based on the event's start time. |
2. Ticket filters
| Setting | What it does |
|---|---|
| Ticket Type | Filter results down to one or more specific ticket types. Leave all selected to include every type, including tickets with no type assigned ("Not Specified"). |
| is Ticket Consumed | Choose whether to include tickets that have been scanned/used (Yes), tickets that haven't (No), or both. Both are included by default. |
| Deleted Tickets | Choose whether to include tickets that have been deleted. By default, only active (non-deleted) tickets are shown. |
Columns on the report
Summary
A small summary box at the top right of the report shows a quick count of tickets per order, broken out by whether they've been scanned:
| Column | Description |
|---|---|
| Order Id | The order number the tickets belong to. |
| is Ticket Complete/Scanned | Whether the tickets in that count have been scanned (Yes) or not (No). |
| Count | The number of tickets for that order matching that scanned status. |
Details
| Column | Description |
|---|---|
| Order Id | The order number the ticket belongs to. |
| Assignment | The staffing or resource assignment tied to the event booking. |
| Package Name | The event package booked. |
| Site Name | The site or space where the event takes place. |
| Booked On | The date and time the booking was made. |
| Start Date/Time | When the event begins. |
| End Date/Time | When the event ends. |
| Ticket Id | The unique identifier for the individual ticket. |
| Ticket Type | The type of ticket issued. |
| Ticket Barcode | The barcode number printed on or associated with the ticket. |
| is Ticket Complete | Whether the ticket has been scanned/used (Yes) or not (No). |
How to read the layout
The report has two sections:
- Summary – a compact box at the top of the report showing ticket counts by order and scanned status, useful for a quick at-a-glance check.
- Details – the full list of individual tickets matching your filters, with one row per ticket.
Use the Summary section to quickly spot orders where not all tickets have been scanned, then refer to the Details section below it to see exactly which tickets are still outstanding.
Comments
Please sign in to leave a comment.