What is the Tickets Report?
The Tickets Report is a comprehensive reporting dashboard in FEARTICKET that gives event organizers a complete overview of ticket sales, addon sales, scan activity, and gross revenue, all in one place.
It provides both tabular data and visual pie charts so you can quickly understand the performance of your event.
Note: Results in the Tickets Report are refreshed from cache every 5 minutes for performance optimization.
How do I access the Tickets Report?
- Log in to your FEARTICKET organizer account.
- From the left-hand navigation, click on Reports.
- Select Tickets Report from the submenu.

What filters are available in the Tickets Report?
The Tickets Report includes two primary filters:
1. Date Range
Filter your report by a custom date range using the Date Range selector at the top of the page. Set a start date and end date, then click Go to apply.
2. Selling Point
Filter results by how tickets were sold:
| Option | Description |
|---|---|
| All | Shows combined data from all selling points |
| Online | Shows only tickets sold through the online ticketing portal |
| Box Office | Shows only tickets sold at your physical box office |
What does the Summary Bar show?
At the top of the report, a summary bar displays high-level totals for the selected date range and selling point:
| Field | Description |
|---|---|
| Tickets | Total number of tickets sold |
| Addons | Total number of addons sold |
| Misc. Charges | Any miscellaneous charges applied |
| Service Fees | Total service fees collected |
| Service Tax | Total service tax applied |
| Discount | Total discount amount applied |
| Social Discount | Discounts applied via social sharing promotions |
| Cancelled | Number of cancelled tickets |
| Gross Revenue | Total gross revenue generated for the event |
What is the "Sales By Ticket" section?
The Sales By Ticket table breaks down sales performance by individual ticket type. Each row represents one ticket type created for your event.
Columns explained:
| Column | Description |
|---|---|
| Ticket | The name of the ticket type (e.g., Audition, Online, Regular Ticket, Selection) |
| Sales | Total number of tickets sold for that type |
| Online | Number sold through the online portal |
| Box Office | Number sold at the box office |
| Cancelled | Number of cancellations for that ticket type |
| Revenue | Total revenue generated by that ticket type |
A pie chart on the right side visually represents the revenue share of each ticket type.
Can I export this data?
Yes! Click the red Export button at the top-right of the table to download the Sales By Ticket data.
What is the "Sales By Ticket Addon" section?
The Sales By Ticket Addon table shows sales data for all addons (upsells) associated with your tickets.
Columns explained:
| Column | Description |
|---|---|
| Addon | The name of the addon (e.g., Beverages, Tea) |
| Sales | Total number of addon units sold |
| Price | Price per unit of the addon |
| Online | Number sold online |
| Box Office | Number sold at box office |
| Cancelled | Number of addon cancellations |
| Revenue | Total revenue from that addon |
A pie chart on the right side shows the revenue breakdown across all addon types.
Can I export addon data?
Yes! Click the Export button on the Addon table to download the data.
What is the "Scan Stats" section?
The Scan Stats table provides detailed check-in and scanning data for each ticket type. This is especially useful for monitoring gate activity during your event.
Formula: Total Sold = Scanned + Not Scanned + Cancelled
Columns explained:
| Column | Description |
|---|---|
| Ticket Type | The ticket or addon type being scanned |
| Scanned | Number of tickets that have been successfully scanned/checked in |
| Not Scanned | Number of valid tickets that have not yet been scanned |
| Cancelled | Number of cancelled tickets |
| Total Sold | Total tickets sold (Scanned + Not Scanned + Cancelled) |
| Duplicate Scanned | Number of tickets that were scanned more than once (flagged as duplicate) |
| Invalid Scanned | Number of scan attempts that were invalid or failed |
Tip: Monitor Duplicate Scanned entries to identify potential ticket fraud or scanner errors at the gate.
Can I export Scan Stats?
Yes! Click the Export button on the Scan Stats table.
What is the "Sales By Category" section?
The Sales By Category table groups your ticket sales by category (if categories are assigned to ticket types).
| Column | Description |
|---|---|
| Category | The category name (e.g., "No Category" if unassigned) |
| Online | Tickets sold online in that category |
| Box Office | Tickets sold at box office in that category |
| Cancelled | Cancellations in that category |
| Total | Total tickets sold in that category |
A pie chart on the right visually shows the distribution of tickets across categories.
Can I export all report data?
Yes. Each section of the Tickets Report has its own Export button (highlighted in red). Clicking it will download a file of that section's data, which you can open in spreadsheet software like Microsoft Excel or Google Sheets.
Why do some box office numbers appear as links (in orange/red)?
Clickable numbers in the Online or Box Office columns are hyperlinks. Clicking them will drill down into a more detailed transaction view for that specific ticket type and selling channel.
How often is the Tickets Report updated?
The Tickets Report data is cached and refreshed every 5 minutes. If you do not see the most recent sales, wait a few minutes and refresh the page.
Best Practices for Using the Tickets Report
- Use Date Range filters to isolate specific event nights or sales windows.
- Check Scan Stats during your event to monitor real-time check-in progress.
- Watch Duplicate Scanned counts to quickly catch gate issues.
- Export regularly to keep offline backups of your sales data.
- Cross-reference Online vs. Box Office sales to understand your most effective selling channel.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article