Sometimes you need a quick view of ticket sales without logging into the WordPress admin area. Maybe an event manager, client, partner, or venue team wants to see progress from a simple private page.
The Ticket Sale Stats add-on was created for that exact use case. It lets you display event ticket sales stats on the front end using shortcodes.
Short version: install the add-on, place one of the available shortcodes on a page or post, and use it to show upcoming, past, or specific event ticket sales statistics outside the WordPress admin dashboard.
Why Show Ticket Stats on the Front End?
Front-end stats are useful when someone needs visibility but does not need full admin access. This keeps the workflow simpler and safer.
- Clients can monitor sales without entering wp-admin.
- Event managers can check progress from a private page.
- Venue partners can see ticket movement at a glance.
- Teams can review past-event performance without digging through settings.
Download and Install the Add-On
Download the add-on here:
Download Ticket Sale Stats add-on
Install and activate it like any other WordPress plugin. After activation, you can add the available shortcodes to a page, post, or private dashboard page.
Available Shortcodes
| Shortcode | What it shows |
|---|---|
[tc_custom_event_stats type="upcoming"] | Ticket sales stats for upcoming events. |
[tc_custom_event_stats type="past"] | Ticket sales stats for past events. |
[tc_custom_event_stats event_id="123"] | Stats for one specific event. Replace 123 with the event ID. |
Where to Place the Stats Page
Do not publish sensitive sales data publicly unless that is intentional. In most cases, create a private or password-protected page and share it only with the people who need it.
- Use a private page for internal teams.
- Use password protection for simple client access.
- Use membership or role restrictions for stricter control.
- Avoid showing revenue or capacity data publicly unless it supports your marketing strategy.
How Front-End Stats Help Event Decisions
Ticket stats are not only for curiosity. They can help you decide when to promote harder, open more capacity, adjust pricing, or communicate urgency.
For deeper reporting after the event, combine this with Tickera CSV Export. Front-end stats are great for a quick view; CSV exports are better for detailed analysis.
Ticket Stats Checklist
- Download and install the add-on.
- Create a private or protected stats page.
- Add the shortcode for upcoming, past, or a specific event.
- Confirm the output shows the correct event data.
- Share access only with people who need it.
- Review stats regularly during active campaigns.
What the Stats Page Should and Should Not Do
A front-end stats page should be a quick operational view, not a replacement for full reporting. Keep it focused on the numbers people need to make decisions: how many tickets have sold, which events are active, and whether a campaign needs attention.
Avoid turning the page into a public analytics dashboard. If partners only need totals, do not show revenue, customer names, order details, or anything that creates unnecessary privacy risk.
Good Use Cases for Front-End Ticket Stats
- Client reporting: an agency can give an event client a simple page showing progress without wp-admin access.
- Venue coordination: venue teams can estimate staffing, bar stock, seating, or entry flow based on ticket movement.
- Promotion decisions: marketing teams can see when sales slow down and decide whether to send another campaign.
- Internal dashboards: organizers can keep a private overview page for multiple upcoming events.
If you need deeper post-event analysis, export the attendee data and review it with spreadsheets. Front-end stats are best for visibility during the sales cycle; exports are better for detailed review after the event.
Access Control Matters
Because ticket statistics can reveal business performance, treat the stats page like internal information. A password-protected page may be enough for a small team, but larger organizations should consider role-based access or a membership-style restriction.
Also review access after the event. If a contractor, sponsor, or temporary partner no longer needs the page, remove their access. Reporting convenience should never create a long-term data exposure problem.
Used this way, the stats page becomes a simple operational checkpoint: quick enough for daily review, limited enough to stay safe, and focused enough that non-technical stakeholders can understand it without training.
Frequently Asked Questions
Can I show stats for only one event?
Yes. Use [tc_custom_event_stats event_id="123"] and replace 123 with the actual event ID.
Should ticket sales stats be public?
Usually no. Sales data is often sensitive, so use a private, password-protected, or role-restricted page unless there is a clear reason to make it public.
Can clients view stats without admin access?
Yes. That is one of the main benefits of using a front-end stats page.
Final Thoughts
Front-end ticket stats give the right people visibility without giving them unnecessary admin access. Keep the page protected, use the right shortcode, and treat the stats as a simple decision-making dashboard for your event.
