---
title: "Ticket & Registration Reports"
description: "Eventixa Pro provides detailed reporting for ticket registrations, booking quantities, attendee records, ticket capacity, RSVP responses, recurring-event occurrences, and check-in activity. Ticket and registration information is available across the **Bookings**, **Attendees**, and **Operational Reports** sections under **Eventixa → Reports**. >…"
url: "https://eventixawp.com/docs/ticket-registration-reports/"
updated: "2026-09-26"
category: Reports
---

# Ticket & Registration Reports

Eventixa Pro provides detailed reporting for ticket registrations, booking quantities, attendee records, ticket capacity, RSVP responses, recurring-event occurrences, and check-in activity.

Ticket and registration information is available across the **Bookings**, **Attendees**, and **Operational Reports** sections under **Eventixa → Reports**.

> **Available in:** Eventixa Pro
> **Admin Location:** Eventixa → Reports
> **Primary Sections:** Bookings, Attendees, Operational Reports
> **Related features:** Tickets, Bookings, Attendees, RSVP, Recurring Events, Check-In

## What Can Ticket & Registration Reports Show?

Eventixa can help you answer questions such as:

- How many tickets were registered?
- Which ticket types were selected?
- How many tickets belong to each booking?
- Which attendees registered for each ticket?
- Which recurring occurrence was selected?
- How much ticket capacity remains?
- Which registrations are Standard or RSVP?
- Which RSVP registrations are Going or Not Going?
- Which attendees have checked in?
- Which registrations are still active?
- Which booking or payment statuses are associated with registrations?

## Where Ticket Reporting Appears

Ticket and registration reporting is spread across three main report areas.

### Bookings

Best for booking-level information such as ticket quantities, customers, booking statuses, payment statuses, payment methods, and coupons.

### Attendees

Best for individual registration records, attendee names, ticket assignments, RSVP information, and check-in activity.

### Operational Reports

Best for aggregated ticket counts, ticket capacity, attendance, no-shows, and operational breakdowns.

## Bookings Report

Go to **Eventixa → Reports → Bookings** to review booking-level ticket activity.

Each booking row can include information such as:

- Booking Number
- Booking Date
- Event
- Occurrence Date
- Customer Name
- Customer Email
- Customer Phone
- Ticket(s)
- Quantity
- Coupon
- Booking Status
- Payment Status
- Payment Method
- Transaction ID

## Ticket Quantity in Bookings

The **Quantity** field shows the total ticket quantity associated with the booking.

For example, a booking may contain: **Standard Event Pass × 2** and **Student Admission × 1**

The booking quantity represents the registered ticket quantities belonging to that booking.

## Multiple Tickets in One Booking

A booking can contain more than one ticket type where the Eventixa checkout flow allows it.

The Bookings Report can therefore represent a booking containing several ticket lines rather than assuming one ticket per booking.

## Ticket Names

The **Ticket(s)** column identifies the ticket or tickets associated with the booking.

This helps administrators understand which ticket products contributed to the registration.

## Filter Bookings by Ticket

Select an Event first and then use the **Ticket** filter to narrow the Bookings Report to a particular ticket.

For example:

**Event:** Community Science Festival
**Ticket:** Standard Event Pass

The report then focuses on bookings associated with that ticket.

## Filter by Event

Use the **Event** filter when you want ticket registration data for one specific event.

Selecting an event also enables related ticket and occurrence filtering where applicable.

## Filter by Occurrence

For recurring events, use the **Occurrence** filter to isolate registrations for one event date.

This is important because the same ticket can be used across multiple recurring occurrences depending on the event configuration.

## Recurring Registration Example

Suppose an event has these occurrences:

- April 15, 2028
- August 16, 2028
- December 12, 2028

Selecting **August 16, 2028** lets you review only the registrations associated with that occurrence.

## Booking Date Range

The Bookings Report uses **booking created date** for its primary reporting period.

This means the date filter reflects when the booking was created, not when the event takes place.

For example, a booking created in September for an event taking place next March belongs to the September booking report period.

## Registration Type Filter

The Bookings Report can filter by **Registration Type**.

Current types include:

- Standard
- RSVP

This helps separate regular ticket bookings from RSVP registrations.

## Standard Registrations

A Standard registration represents the normal ticket booking workflow.

Depending on the ticket and configuration, it can involve:

- Free ticket registration
- Paid checkout
- Attendee collection
- Ticket issuance
- Payment workflow

## RSVP Registrations

An RSVP registration uses the Eventixa RSVP workflow.

RSVP tickets can contain responses such as:

- Going
- Not Going

The Reports module allows RSVP activity to be analyzed separately from Standard registrations.

## RSVP Response Filter

When reviewing RSVP data, use the **RSVP Response** filter to choose:

- Going
- Not Going

This allows you to isolate attendance intent within RSVP registrations.

## RSVP Going

**Going** represents an RSVP registration where the attendee has confirmed attendance.

## RSVP Not Going

**Not Going** represents an RSVP response indicating the attendee does not plan to attend.

These registrations should not be interpreted in the same way as active capacity-consuming attendance when reviewing event participation.

## Booking Status Filter

Ticket registrations can also be analyzed according to the current booking status.

Use the **Booking Status** filter to narrow the report to a particular booking state.

This is useful when separating active bookings from cancelled, failed, expired, or refunded records.

## Payment Status Filter

Use **Payment Status** to narrow registrations according to the payment lifecycle.

This is useful when you need to review registrations with specific payment states.

## Payment Method Filter

Use **Payment Method** to view bookings created through a specific payment workflow.

Depending on your Eventixa setup, available methods can include PayPal, Stripe, Local / Offline, WooCommerce, or other supported methods.

## Coupon Filter

The Bookings Report supports filtering by coupon code.

This lets you identify ticket registrations associated with a particular Eventixa coupon.

## Customer or Booking Search

Use the **Customer or booking** search to find registration records using information such as:

- Customer name
- Customer email
- Booking number

This is useful when investigating a specific registration.

## Attendees Report

Go to **Eventixa → Reports → Attendees** when you need individual registration records instead of booking-level totals.

One booking can contain multiple attendees, so attendee reporting provides more granular registration information.

## Attendee Report Columns

The current attendee report can include:

- Attendee Name
- Attendee Email
- Event
- Occurrence Date
- Ticket
- Booking Number
- Booking Customer
- Attendee Status
- Checked-in
- Checked-in At
- Checked-in By
- Checked-out At
- Seat
- Registration Date

Configured attendee fields can also appear as additional columns.

## One Booking vs Multiple Attendees

A single booking can produce multiple attendee records.

For example:

**Booking Quantity:** 3

may create:

- Attendee 1
- Attendee 2
- Attendee 3

The Bookings Report shows the booking and quantity, while the Attendees Report shows the individual registration records.

## Ticket Assignment per Attendee

The **Ticket** column shows which ticket belongs to each attendee.

This is useful when one event has multiple ticket types.

## Attendee Registration Date

The Attendees Report uses **registration date** for its date filtering.

This reflects when the attendee record was created.

It does not use the scheduled event date as the primary attendee report date.

## Attendee Status

Use **Attendee Status** to filter registrations according to their current attendee state.

Cancelled and refunded attendee records can be separated from active registrations.

## Check-In Status

The Attendees Report can filter by:

- Checked-in
- Not checked-in

This makes it useful for both pre-event registration review and post-event attendance analysis.

## Checked-in At

The **Checked-in At** column records when the attendee was successfully checked in.

## Checked-in By

The **Checked-in By** column identifies the user or workflow associated with the recorded check-in where this information is available.

## Checked-out At

The **Checked-out At** column can record checkout activity where Eventixa's attendee workflow supports it.

## Seat Information

The **Seat** column can display seat-related data where the attendee has an associated seat value.

## Configured Attendee Fields

Custom attendee registration fields can appear as additional report columns.

For example, if your registration form collects information such as:

- Company
- Job Title
- Dietary Preference

those configured attendee values can be included in attendee reporting and exports where supported.

## Registration Type in Attendee Reports

The Attendees Report also supports filtering by **Registration Type**, allowing Standard and RSVP registrations to be reviewed separately.

## RSVP Response in Attendee Reports

RSVP attendee records can be filtered by **Going** or **Not Going**.

This is useful when you need the individual people behind RSVP response totals.

## Booking Status in Attendee Reports

Attendee records can also be filtered according to the status of their associated booking.

This helps administrators avoid mixing registrations attached to different booking lifecycle states.

## Payment Status in Attendee Reports

Use **Payment Status** when you need to review attendees whose associated bookings are in a particular payment state.

## Check-In Date Filters

The Attendees Report provides **Check-in from** and **Check-in to** filters.

These filters are useful when you need to identify attendees checked in during a specific time period.

## Attendee or Booking Search

The attendee report search can help find records using attendee or booking information.

This is useful when locating a particular registration without manually browsing every page.

## Ticket Sales Count Report

Go to **Operational Reports** and select **Ticket Sales Count** to view aggregated ticket registration counts.

Despite the name, this is a count-based ticket registration report rather than a revenue calculation.

## What Ticket Sales Count Measures

Ticket Sales Count focuses on ticket registration activity.

It can be filtered by:

- Date Range
- Organizer
- Event
- Occurrence
- Ticket

This makes it useful for comparing registration activity between ticket types.

## Ticket Sales Count Date Range

Ticket Sales Count uses registration activity dates.

It does not use event date in the same way as Event Attendance.

Always confirm this distinction when comparing reports.

## Ticket Capacity Report

Select **Ticket Capacity** under Operational Reports to review current ticket inventory.

The report can show:

- Ticket
- Event
- Capacity
- Registered
- Remaining
- Utilization

## Capacity

**Capacity** represents the configured ticket limit.

For example:

**Capacity:** 100

means the ticket can accommodate up to 100 registrations according to its current inventory configuration.

## Registered

**Registered** shows the ticket's currently consumed registration quantity used by the capacity report.

## Remaining

**Remaining** represents the current available quantity.

For example:

**Capacity:** 100
**Registered:** 80
**Remaining:** 20

## Utilization

**Utilization** represents the percentage of configured capacity currently consumed.

For example:

**Capacity:** 100
**Registered:** 80

results in approximately: **80% utilization**

## Capacity Is a Current Snapshot

Ticket Capacity is not a historical report.

Changing the report Date Range does not change the current Capacity, Registered, Remaining, or Utilization values.

## Unlimited Capacity Tickets

Tickets configured without a fixed capacity may not behave like limited-capacity tickets in the Ticket Capacity report.

Interpret capacity values according to the ticket's actual Eventixa inventory configuration.

## Ticket Registration vs Attendance

Registration and attendance are not the same measurement.

A customer can successfully register for a ticket but never attend the event.

Use registration reports to measure signups and attendance reports to measure actual check-in activity.

## Example

Suppose an event has:

**Registered:** 120
**Checked-in:** 90
**Not Checked-in:** 30

The registration count is 120, but actual checked-in attendance is 90.

## Ticket Registration vs Booking Quantity

Booking quantity and attendee count can also differ depending on the registration workflow.

The Bookings Report focuses on the booking transaction and ticket quantities, while the Attendees Report focuses on individual attendee records.

Use the report that matches the question you are trying to answer.

## Free Tickets

Free Standard tickets appear in reporting like other eligible ticket registrations even though no payment is required.

Their booking/payment information should be interpreted according to the free-ticket workflow.

## Paid Tickets

Paid tickets can include additional payment-related data such as payment status, payment method, transaction ID, and booking-level totals.

These financial fields do not change the ticket registration count itself.

## RSVP Tickets

RSVP tickets should be analyzed with both Registration Type and RSVP Response where relevant.

This avoids mixing Going and Not Going registrations into one interpretation.

## Recurring Event Tickets

Recurring-event registrations retain occurrence context.

Use the **Occurrence** filter whenever you need to separate registrations for different dates of the same recurring event.

## Same Ticket Across Multiple Occurrences

If a recurring ticket is associated with multiple occurrences, an overall event-level report may combine activity unless you explicitly filter by occurrence.

For occurrence-specific analysis, select the correct recurring date.

## Ticket Registration and Check-In

Ticket registration reports can be combined with attendee check-in data.

For example, you can:

1. Filter Attendees by Event.
2. Select a Ticket.
3. Select an Occurrence if recurring.
4. Set Check-In Status to Checked-in.
5. Review the individual attendees who actually entered the event.

## Ticket Registration and No-shows

To compare ticket registrations with no-shows, use the appropriate attendance or No-show Operational Report.

A registered ticket does not automatically mean the attendee checked in.

## Visible Columns

The Bookings and Attendees reports include a **Columns** control.

Use it to show only the registration information you need.

For example, a ticket registration review may show:

- Booking Number
- Event
- Ticket
- Quantity
- Booking Status

while hiding unrelated payment columns.

## Export Current View

Use **Export Current View** to export the records displayed on the current report page.

This is useful when you only need the currently visible subset.

## Export All Filtered

Use **Export All Filtered** to export every record matching the active filters.

This is useful for complete event registration lists.

## Attendees Export

The dedicated **Attendees** export can include fields such as:

- Attendee ID
- Registration Date
- Registration Time
- Attendee Name
- Attendee Email
- Booking details
- Event
- Occurrence
- Ticket
- Attendee Status
- Check-in details
- Seat
- Attendee Notes
- Configured attendee fields

## Event Guest List Export

The **Event Guest List** export provides a simplified registration list.

It can include fields such as:

- Attendee Name
- Attendee Email
- Booking Number
- Booking Customer
- Event
- Occurrence
- Ticket
- Attendee Status
- Seat

This is useful when you need a clean attendee list without the full reporting dataset.

## Check-In List Export

The **Check-in List** export focuses on attendance operations.

It can include:

- Attendee Name
- Attendee Email
- Booking Number
- Event
- Occurrence
- Ticket
- Attendee Status
- Checked-in
- Checked-in At
- Checked-in By
- Checked-out At
- Seat

## Preview Registration Exports

Use **Preview Export** before generating a CSV.

Eventixa shows the matching row count and a preview of the first 20 matching rows.

This helps confirm that your event, ticket, occurrence, and status filters are correct before generating the file.

## Large Registration Exports

Large CSV exports can run in the background.

Completed files are shown under **Export History** and expire automatically after 48 hours.

## Recommended Ticket Report Workflow

1. Go to **Eventixa → Reports → Bookings**.
2. Select the Date Range.
3. Select the Event.
4. Select the Ticket.
5. Select the Occurrence if recurring.
6. Choose Standard or RSVP if needed.
7. Apply booking/payment filters if relevant.
8. Review ticket quantities.
9. Export the filtered data when needed.

## Recommended Attendee Report Workflow

1. Go to **Eventixa → Reports → Attendees**.
2. Select the Registration Date range.
3. Select the Event.
4. Select the Ticket.
5. Select the Occurrence if recurring.
6. Apply Attendee Status or Check-In Status.
7. Apply RSVP Response if needed.
8. Review individual registrations.
9. Export an Attendees, Guest List, or Check-In List when required.

## Recommended Capacity Review

1. Open **Operational Reports**.
2. Select **Ticket Capacity**.
3. Select the Event.
4. Select a specific Ticket if needed.
5. Review Capacity, Registered, Remaining, and Utilization.
6. Remember that the Date Range does not change the current capacity snapshot.

## Common Problems

### Ticket Registration Count Looks Different from Booking Count

This can be expected because one booking can contain multiple ticket quantities or multiple attendees.

Booking count, ticket quantity, and attendee count measure different things.

### Ticket Quantity Does Not Match Attendee Count

Check the registration workflow and booking details.

The Bookings Report measures booking ticket quantities, while the Attendees Report contains individual attendee records.

### RSVP Numbers Look Incorrect

Apply both **Registration Type = RSVP** and the appropriate **RSVP Response** filter.

Going and Not Going should not be interpreted as the same attendance state.

### Recurring Ticket Registrations Are Mixed Together

Select the relevant **Occurrence** to isolate one recurring date.

### Ticket Capacity Does Not Change with the Date Range

This is expected because Ticket Capacity is a current inventory snapshot.

### Registration Report Does Not Match Event Attendance

This can be expected because registration activity and event attendance use different date semantics and measure different stages of the event workflow.

### Cancelled Attendee Is Missing from Active Counts

This can be expected because cancelled and refunded attendees are excluded from active attendee reporting where appropriate.

### Ticket Filter Is Missing

Select an Event first so Eventixa can load the tickets associated with that event.

### Occurrence Filter Is Missing

Select a recurring event first so Eventixa can load its available occurrences.

### Export Button Is Missing

The current user may not have the required Eventixa export capability.

## Important Notes

- Ticket & Registration Reports require Eventixa Pro.
- Booking count, ticket quantity, and attendee count are separate measurements.
- The Bookings Report uses booking creation date.
- The Attendees Report uses registration creation date.
- Ticket Sales Count uses registration activity dates.
- Ticket Capacity is a current inventory snapshot.
- Standard and RSVP registrations can be filtered separately.
- RSVP registrations can be filtered by Going and Not Going.
- Recurring-event registrations can be filtered by occurrence.
- Check-In Status can be used to separate registered attendees from actual attendees.
- Custom attendee fields can appear in attendee reports and exports where configured.
- Registration exports can be generated from current views, full filtered datasets, Guest Lists, or Check-In Lists.
- Large exports can run in the background and expire after 48 hours.

## Related Documentation

- [Reports Overview](https://eventixawp.com/docs/reports-overview/)
- [Event Reports](https://eventixawp.com/docs/event-reports/)
- [Filtering Reports](https://eventixawp.com/docs/filtering-reports/)
- [Creating Event Tickets](https://eventixawp.com/docs/creating-event-tickets/)
- [Ticket Capacity and Availability](https://eventixawp.com/docs/ticket-capacity-and-availability/)
- [RSVP Tickets](https://eventixawp.com/docs/rsvp-tickets/)
- [Managing Bookings](https://eventixawp.com/docs/managing-bookings/)
- [Managing Attendees](https://eventixawp.com/docs/managing-attendees/)
- [Recurring Event Tickets](https://eventixawp.com/docs/recurring-event-tickets/)
- [Event Check-In](https://eventixawp.com/docs/event-check-in/)