--- title: Event Reports description: "Eventixa Pro provides event-focused reports for analyzing registrations, attendance, recurring occurrences, ticket capacity, check-ins, no-shows, booking statuses, payment activity, and coupon usage. Most event-level reporting is available under **Eventixa → Reports → Operational Reports**. > **Available in:** Eventixa Pro >…" url: "https://eventixawp.com/docs/event-reports/" updated: "2026-09-26" category: Reports --- # Event Reports Eventixa Pro provides event-focused reports for analyzing registrations, attendance, recurring occurrences, ticket capacity, check-ins, no-shows, booking statuses, payment activity, and coupon usage. Most event-level reporting is available under **Eventixa → Reports → Operational Reports**. > **Available in:** Eventixa Pro > **Admin Location:** Eventixa → Reports → Operational Reports > **Related features:** Bookings, Attendees, Tickets, Check-In, Recurring Events ## What Are Event Reports? Event Reports help you understand how individual events and recurring occurrences are performing. You can use them to answer questions such as: - How many people registered for an event? - How many attendees checked in? - How many registered attendees did not attend? - How much ticket capacity remains? - Which recurring occurrence had more registrations? - Which occurrence had a better check-in rate? - Which booking statuses are associated with the event? - Which payment methods were used? - How many bookings used coupons? Eventixa provides several predefined Operational Reports instead of one single event-report table. ## Open Event Reports Go to **Eventixa → Reports** and select **Operational Reports**. The Operational Reports screen provides controls for Date Range, Report Type, Organizer, Event, Occurrence, and Ticket. Select the report type and filters that match the event information you want to analyze. ## Available Operational Reports The current Eventixa Reports module includes: - Ticket Sales Count - Ticket Capacity - Event Attendance - Occurrence Attendance - Check-in Performance - No-show Report - Coupon Usage - Booking Status Breakdown - Payment Status Breakdown - Payment Method Breakdown Each report measures a different part of the event workflow. ## Filter by Event Use the **Event** filter to restrict report results to one Eventixa event. For example, selecting **Community Science Festival** limits applicable report data to that event. Selecting an event can also make its relevant Ticket and Occurrence filters available. ## Filter by Organizer Use the **Organizer** filter when you want to analyze events belonging to a particular organizer. Selecting an organizer can narrow the available Event options, making it easier to find the correct event when your site contains many events. ## Filter by Ticket After selecting an event, use the **Ticket** filter to focus the report on a particular ticket. For example: - Student Admission - Standard Event Pass - VIP Pass Ticket filtering is particularly useful for Ticket Sales Count and Ticket Capacity reports. ## Filter by Occurrence For recurring events, use the **Occurrence** filter to analyze one date independently from the rest of the recurring series. For example, a recurring event may have occurrences on April 15, August 16, and December 12. Selecting August 16 keeps the report focused on that occurrence instead of combining the entire recurring series. ## Event Attendance Select **Event Attendance** to review attendance grouped at the event level. The report can show: - Registered - Checked-in - Not Checked-in - Check-in Rate This helps you compare registrations with actual attendance. ## Event Attendance Date Range The Event Attendance report uses the **event date** for the selected reporting period. This is important because the selected date range does not represent when the attendee registered. For example, if you select August 1–31, Event Attendance includes relevant events whose event dates fall within August even if attendees registered several months earlier. ## Registered **Registered** represents eligible active attendee registrations included in the attendance report. Cancelled and refunded attendee records are excluded from the active attendance population. ## Checked-in **Checked-in** represents eligible attendees whose current check-in status indicates that they attended the event. ## Not Checked-in **Not Checked-in** represents eligible registered attendees who were not checked in. Conceptually, the relationship is: **Registered − Checked-in = Not Checked-in** ## Check-in Rate **Check-in Rate** shows the percentage of active registered attendees who checked in. Conceptually: **Checked-in ÷ Registered × 100** For example, if an event has 200 active registrations and 160 attendees checked in, the check-in rate is 80%. ## Occurrence Attendance Select **Occurrence Attendance** when analyzing recurring events. Instead of combining the whole recurring event into one result, Eventixa breaks attendance down by occurrence. The report can show Registered, Checked-in, Not Checked-in, and Check-in Rate for individual occurrence dates. ## Why Occurrence Attendance Is Useful Suppose the same recurring event has: - April 15 — 80 registered - August 16 — 120 registered - December 12 — 95 registered An overall event total can hide differences between those dates. Occurrence Attendance lets you compare individual event dates more accurately. ## Occurrence Attendance Date Range Occurrence Attendance uses the **occurrence date** for its reporting period. The attendee registration creation date does not determine whether that occurrence appears in the report. ## Check-In Performance Select **Check-in Performance** to analyze registration and check-in activity for events and occurrences. The report includes operational metrics such as Registered, Checked-in, Not Checked-in, and Check-in Rate. This can be useful after an event when evaluating actual attendance against registrations. ## Check-In Performance for Recurring Events Recurring-event check-in reporting retains occurrence context. This ensures that registrations and check-ins are evaluated against the correct event date rather than combined incorrectly across the recurring series. ## No-show Report The **No-show Report** helps identify eligible active registrations that were not checked in for the relevant event or occurrence. Cancelled and refunded attendee records are excluded from active no-show calculations. ## What Is a No-show? For Eventixa operational reporting, a no-show is an eligible attendee registration that remains **Not Checked-in** for the relevant event or occurrence. A registered attendee who never checked in can therefore appear in the No-show Report. ## Why No-show Data Is Useful No-show reporting can help you understand differences between registrations and actual attendance, evaluate venue utilization, identify attendance patterns, and improve planning for future events. ## Ticket Sales Count Select **Ticket Sales Count** to analyze ticket registration quantities. Despite the report name, Ticket Sales Count is a count-based registration report and does not calculate ticket revenue. ## Ticket Sales Count Date Range Ticket Sales Count uses registration activity dates rather than event dates. This is different from Event Attendance and Occurrence Attendance. Always consider the report's date meaning before comparing its numbers with another report. ## Ticket Capacity Select **Ticket Capacity** to review the current inventory status of event tickets. The report can show: - Ticket - Event - Capacity - Registered - Remaining - Utilization ## Capacity **Capacity** represents the configured ticket limit. For example, a ticket with a capacity of 100 can accommodate up to 100 registrations according to its current ticket configuration. ## Registered **Registered** represents the ticket's currently consumed registration quantity used by the capacity report. ## Remaining **Remaining** represents the current ticket quantity still available. For example: **Capacity:** 100 **Registered:** 75 **Remaining:** 25 ## Utilization **Utilization** indicates how much of the configured ticket capacity is currently consumed. For example, if Capacity is 100 and Registered is 75, utilization is approximately 75%. ## Ticket Capacity Is a Current Snapshot The Ticket Capacity report is different from most Eventixa reports because it displays the current inventory state. Changing the Date Range does not change the current Capacity, Registered, Remaining, or Utilization values. The selected Date Range is therefore not used as a historical capacity filter. ## Booking Status Breakdown Select **Booking Status Breakdown** to group booking activity by booking status. The report can show each status together with the number of Bookings and Tickets associated with that status. This is useful when reviewing the lifecycle state of bookings connected to an event. ## Booking Status Date Range Booking Status Breakdown uses the **booking created date**. It does not use the scheduled event date. ## Payment Status Breakdown Select **Payment Status Breakdown** to group bookings according to their payment status. The report provides booking and ticket counts for the payment states present in the selected dataset. ## Payment Status Is Not Revenue Payment Status Breakdown measures counts associated with payment states. It does not calculate aggregated revenue. Use this report to understand payment workflow activity rather than financial totals. ## Payment Method Breakdown Select **Payment Method Breakdown** to group booking activity by payment method. Depending on your Eventixa setup and booking data, methods may include PayPal, Stripe, Local / Offline, WooCommerce, or other supported methods. ## Payment Method Date Range Payment Method Breakdown uses the **booking created date** for its reporting period. ## Coupon Usage Select **Coupon Usage** to analyze coupon activity associated with bookings. The report can show the coupon value or code together with the number of Bookings and Tickets associated with that coupon. ## Coupon Usage Date Range Coupon Usage uses the **booking created date**. ## Understanding Event Report Date Ranges The meaning of Date Range changes according to the selected Operational Report. This is one of the most important concepts when working with Eventixa Reports. ### Event Attendance Uses the event date. ### Occurrence Attendance Uses the recurring occurrence date. ### Check-in Performance Uses the relevant event or occurrence date. ### No-show Report Uses the relevant event or occurrence date. ### Ticket Sales Count Uses registration activity dates. ### Booking Status Breakdown Uses booking creation dates. ### Payment Status Breakdown Uses booking creation dates. ### Payment Method Breakdown Uses booking creation dates. ### Coupon Usage Uses booking creation dates. ### Ticket Capacity Displays current inventory and does not use the Date Range as a historical filter. ## Date Range Presets Eventixa provides the following Date Range presets: - Today - Yesterday - Last 7 days - Last 30 days - This month - Last month - This year - Custom range The default reporting period is **Last 30 days**. ## Custom Date Range Select **Custom range** when you need a specific Start Date and End Date. Custom ranges are useful for conferences, monthly reporting, seasonal event analysis, or internal reporting periods. ## Applying Event Filters A typical Event Report workflow is: 1. Open **Eventixa → Reports → Operational Reports**. 2. Select the Date Range. 3. Choose the Report Type. 4. Select an Organizer if needed. 5. Select the Event. 6. Select the Occurrence if the event is recurring. 7. Select a Ticket if needed. 8. Apply the filters. 9. Review the resulting data. ## Changing the Report Type When you change the Report Type, remember that the meaning of the Date Range can also change. Do not assume that every Operational Report uses the same date field. ## Event Report vs Bookings Report Operational Event Reports and the detailed Bookings Report answer different questions. Use **Operational Reports** when you need aggregated information such as attendance, capacity, check-in rates, no-shows, or status breakdowns. Use the **Bookings** report when you need individual booking records, customer information, booking numbers, payment statuses, payment methods, or transaction details. ## Event Report vs Attendees Report Operational Reports provide aggregated event information, while the **Attendees** report lists individual attendee registrations. For example, Event Attendance may show that 160 attendees checked in. If you need to see who those 160 attendees were, open the Attendees Report and apply matching Event and Check-In Status filters. ## Recurring Event Reporting Recurring events should be analyzed carefully because the same event can contain multiple dates. Use **Occurrence Attendance** when comparing recurring dates and use the Occurrence filter when you need data for one particular occurrence. ## Example Recurring Event Review Suppose **Community Science Festival** occurs on April 15, August 16, and December 12. You can use Occurrence Attendance to compare Registered, Checked-in, Not Checked-in, and Check-in Rate for each date. You can then select one occurrence to investigate that specific date in more detail. ## Export Event Reports Eligible Operational Reports support **Export CSV** and/or **PDF Export**, depending on the report type and the current user's permissions. Exports respect the filters applied to the report. ## CSV Export Use **Export CSV** when you want event report data for spreadsheet analysis, internal records, further calculations, or sharing with another system. ## PDF Export Use **PDF Export** when you need a formatted table-style report for meetings, event summaries, internal records, or archiving. ## Export Permissions Eventixa controls report exports through dedicated permissions. Operational reports involving booking or payment information use the appropriate booking export capability, while attendance and ticket-focused reports use attendee export permissions. If an export option is missing, verify the current user's permissions. ## WooCommerce Event Data When WooCommerce checkout is used, detailed Eventixa booking reporting can include WooCommerce order information such as subtotal, discount, tax, final total, gateway, order, transaction ID, and currency. Operational Event Reports remain focused on counts and event-management metrics rather than aggregated financial reporting. ## Event Revenue Is Not Included The current Eventixa Reports implementation does not include a dedicated aggregated **Event Revenue** report. Booking-level financial information can exist in detailed booking reports and exports, but Operational Reports do not currently calculate total event revenue. ## Recommended Event Performance Review After an event, a useful workflow is: 1. Open **Event Attendance** and filter to the event. 2. Review Registered, Checked-in, Not Checked-in, and Check-in Rate. 3. Open **No-show Report** to review registrations that did not check in. 4. Open **Ticket Capacity** to review current ticket utilization. 5. Open **Ticket Sales Count** when you need registration activity by ticket. 6. Review Booking Status, Payment Status, and Payment Method breakdowns if relevant. 7. Export the required reports for your records. ## Recommended Recurring Event Review For recurring events: 1. Open **Occurrence Attendance**. 2. Select the recurring event. 3. Review the different occurrences. 4. Compare Registered counts. 5. Compare Checked-in counts. 6. Compare Check-in Rates. 7. Select an individual occurrence when deeper analysis is required. 8. Review its No-show data if needed. 9. Export the results. ## Common Problems ### Event Report Shows No Data Check the selected Event, Date Range, Report Type, Occurrence, and Ticket filters. Also verify what the Date Range means for the selected report. ### Attendance Report Misses an Event Check the event or occurrence date because attendance reports use scheduled event dates rather than registration creation dates. ### Old Registrations Appear in a Current Attendance Report This can be correct because attendance reports include eligible registrations for events occurring within the selected event-date range regardless of when those attendees originally registered. ### Ticket Sales Count Does Not Match Event Attendance This can be expected because Ticket Sales Count measures registration activity while Event Attendance measures active registrations associated with events in the selected event-date period. ### Ticket Capacity Does Not Change with the Date Range This is expected because Ticket Capacity is a current inventory snapshot rather than a historical report. ### No-show Count Seems High Compare the Registered and Checked-in counts and verify attendee statuses. Eligible active registrations that were not checked in are counted as no-shows. ### Occurrence Filter Is Missing Select a recurring event first. The Occurrence filter becomes relevant when Eventixa has recurring occurrences available for the selected event. ### Ticket Filter Is Missing Select an Event first so Eventixa can load tickets belonging to that event. ### Event Revenue Is Missing This is expected in the current Reports implementation because there is no dedicated aggregated Event Revenue report. ### Export Option Is Missing The current WordPress user may not have the Eventixa export capability required for that report. ## Important Notes - Event Reports require Eventixa Pro. - Event-level analysis is primarily available under Operational Reports. - Event Attendance uses event date. - Occurrence Attendance uses recurring occurrence date. - Ticket Sales Count uses registration activity dates. - Booking, payment, and coupon breakdowns use booking creation dates. - Ticket Capacity displays current inventory and does not use the Date Range historically. - Cancelled and refunded attendees are excluded from active attendance counts. - Recurring events can be analyzed per occurrence. - Operational Reports provide count-based information rather than aggregated revenue. - CSV and PDF exports respect the applicable report filters and user permissions. ## Related Documentation - [Reports Overview](https://eventixawp.com/docs/reports-overview/) - [Ticket & Registration Reports](https://eventixawp.com/docs/ticket-registration-reports/) - [Filtering Reports](https://eventixawp.com/docs/filtering-reports/) - [Managing Bookings](https://eventixawp.com/docs/managing-bookings/) - [Managing Attendees](https://eventixawp.com/docs/managing-attendees/) - [Ticket Capacity and Availability](https://eventixawp.com/docs/ticket-capacity-and-availability/) - [Recurring Events Overview](https://eventixawp.com/docs/recurring-events-overview/) - [Managing Event Occurrences](https://eventixawp.com/docs/managing-event-occurrences/) - [Event Check-In](https://eventixawp.com/docs/event-check-in/) - [WooCommerce Payments](https://eventixawp.com/docs/woocommerce-payments/)