---
title: Filtering Reports
description: "Eventixa Pro includes flexible report filters that help you narrow booking, attendee, ticket, attendance, payment, coupon, and recurring-event data to the records you actually need. The available filters depend on the report section you are using. > **Available in:** Eventixa…"
url: "https://eventixawp.com/docs/filtering-reports/"
updated: "2026-09-26"
category: Reports
---

# Filtering Reports

Eventixa Pro includes flexible report filters that help you narrow booking, attendee, ticket, attendance, payment, coupon, and recurring-event data to the records you actually need.

The available filters depend on the report section you are using.

> **Available in:** Eventixa Pro
> **Admin Location:** Eventixa → Reports
> **Report Sections:** Bookings, Attendees, Operational Reports, Exports

## Why Use Report Filters?

Filters help you isolate specific report data instead of reviewing every Eventixa record at once.

For example, you can filter reports to answer questions such as:

- Which bookings were created this month?
- Which attendees registered for one event?
- Which registrations belong to one recurring occurrence?
- Which customers booked a specific ticket?
- Which RSVP registrations are Going?
- Which attendees have checked in?
- Which bookings used Stripe?
- Which bookings used a specific coupon?
- Which records belong to a particular booking or customer?

## Reports Use Different Filters

Eventixa does not use one identical filter set across every report.

The available controls change according to the selected section:

- **Bookings** focuses on booking, ticket, payment, RSVP, coupon, and customer filters.
- **Attendees** focuses on attendee, registration, ticket, RSVP, status, and check-in filters.
- **Operational Reports** focuses on report type, organizer, event, occurrence, ticket, and date range.
- **Exports** uses report-related filters together with export type, scope, and column selection.

## Date Range

The Date Range is one of the most important filters in Eventixa Reports.

Available presets include:

- 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 to enter a specific Start Date and End Date.

This is useful for monthly reporting, seasonal analysis, conference periods, campaign reviews, or any custom reporting window.

If the entered dates are reversed, Eventixa normalizes them into chronological order.

## Date Range Meaning Depends on the Report

The same Date Range control does not always filter the same date field.

This is critical when interpreting Eventixa report results.

For example, the Bookings Report uses booking creation date, while Event Attendance uses the scheduled event date.

Always confirm what the selected report uses before comparing numbers between report sections.

## Bookings Date Range

The **Bookings** report filters by the date the booking record was created.

For example, a booking created on September 10 for an event taking place in December belongs to the September booking report period.

## Attendees Date Range

The **Attendees** report filters by attendee registration creation date.

This represents when the attendee record was created, not when the event occurs.

## Event Attendance Date Range

The **Event Attendance** Operational Report uses the event date.

A registration created months earlier can still appear if its event falls inside the selected event-date range.

## Occurrence Attendance Date Range

The **Occurrence Attendance** report uses the recurring occurrence date.

This allows recurring-event attendance to be analyzed according to the actual scheduled occurrence.

## Check-In Performance Date Range

The **Check-in Performance** report uses the relevant event or occurrence date rather than the attendee registration creation date.

## No-show Report Date Range

The **No-show Report** also uses the relevant event or occurrence date when identifying registrations that were not checked in.

## Ticket Sales Count Date Range

The **Ticket Sales Count** report uses registration activity dates.

It should not be interpreted as an event-date report.

## Booking and Payment Breakdown Date Range

The **Booking Status Breakdown**, **Payment Status Breakdown**, **Payment Method Breakdown**, and **Coupon Usage** reports use booking creation dates.

## Ticket Capacity and Date Range

The **Ticket Capacity** report is a current inventory snapshot.

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

The Date Range is therefore not used as a historical filter for Ticket Capacity.

## Filter by Event

The Event filter lets you restrict results to one Eventixa event.

This filter is available in multiple report areas.

For example, selecting **Community Science Festival** can limit booking, attendee, operational, or export data to that event.

## Why Select Event First?

Some dependent filters require an Event selection before their options can be loaded.

This commonly applies to:

- Occurrence
- Ticket

If the Ticket or Occurrence filter is missing, select an Event first.

## Filter by Occurrence

For recurring events, use the **Occurrence** filter to isolate one scheduled date.

For example, if an event runs on April 15, August 16, and December 12, selecting August 16 restricts relevant results to that occurrence.

## Occurrence Filtering Is Important

Recurring-event data can otherwise include multiple dates under the same event title.

Use the Occurrence filter whenever you need date-specific booking, registration, attendance, or ticket data.

## Filter by Ticket

Use the **Ticket** filter to restrict results to a particular ticket associated with the selected event.

For example:

- Student Admission
- Standard Event Pass
- VIP Pass

This is useful when comparing ticket types within the same event.

## Organizer Filter

Operational Reports include an **Organizer** filter.

Use it when you want to limit event reporting to events associated with a particular organizer.

Selecting an Organizer can also narrow the Event options shown in the Event filter.

## Report Type Filter

The **Operational Reports** section includes a Report Type selector.

Current report types include:

- 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

Changing the Report Type changes both the data shown and the meaning of some filters.

## Booking Filters

The Bookings Report includes filters for:

- Date Range
- Event
- Occurrence
- Ticket
- Registration Type
- RSVP Response
- Booking Status
- Payment Status
- Payment Method
- Coupon
- Customer or Booking search

These filters can be combined to create a very specific booking dataset.

## Registration Type Filter

Use **Registration Type** to separate:

- Standard
- RSVP

registrations.

This is useful when an event supports both normal ticket bookings and RSVP registrations.

## RSVP Response Filter

For RSVP records, use **RSVP Response** to filter by:

- Going
- Not Going

This allows you to isolate the actual RSVP response rather than treating all RSVP records as the same.

## Booking Status Filter

Use **Booking Status** to restrict results according to the current booking lifecycle state.

This can help you isolate active, completed, cancelled, refunded, failed, or other booking states supported by the current workflow.

## Payment Status Filter

Use **Payment Status** when you need to isolate bookings according to their payment state.

This is useful when reviewing payment workflows or preparing financial exports.

## Payment Method Filter

Use **Payment Method** to restrict bookings to a specific payment workflow.

Depending on your configuration, available values can include PayPal, Stripe, Local / Offline, WooCommerce, or other supported payment methods found in your booking data.

## Coupon Filter

Use the **Coupon** filter to find bookings associated with a particular coupon code.

This is useful when reviewing a promotion or discount campaign.

## Customer or Booking Search

The **Customer or booking** field lets you search for records using booking or customer information.

Useful search values can include:

- Customer name
- Customer email
- Booking number

This is often the fastest way to investigate one specific booking.

## Combining Booking Filters

You can combine several filters at once.

For example:

**Date Range:** This month
**Event:** Community Science Festival
**Ticket:** Standard Event Pass
**Payment Method:** Stripe
**Payment Status:** Paid

This produces a much narrower dataset than using any one filter alone.

## Attendee Filters

The Attendees Report includes filters for:

- Registration Date
- Event
- Occurrence
- Ticket
- Registration Type
- RSVP Response
- Attendee Status
- Check-In Status
- Booking Status
- Payment Status
- Check-in From
- Check-in To
- Attendee or Booking search

These filters are designed for registration-level and attendance-level analysis.

## Attendee Status Filter

Use **Attendee Status** to restrict results according to the current attendee state.

This can help separate active registrations from cancelled or refunded attendee records.

## Check-In Status Filter

Use **Check-In Status** to select:

- Checked-in
- Not checked-in

This is useful for both pre-event preparation and post-event attendance review.

## Check-In Date Filters

The Attendees Report provides **Check-in From** and **Check-in To** fields.

These let you filter attendees based on when their check-in occurred.

For example, you can isolate attendees checked in between 9:00 AM and 11:00 AM where the report's date/time controls support that period.

## Attendee or Booking Search

Use the attendee search to find a registration using attendee or booking information.

This is useful when you need to locate one person without manually browsing multiple report pages.

## Combining Attendee Filters

A useful combination could be:

**Event:** Community Science Festival
**Occurrence:** August 16, 2028
**Ticket:** Standard Event Pass
**Check-In Status:** Checked-in

This gives you a focused list of attendees who checked in for that ticket and occurrence.

## Operational Report Filters

Operational Reports provide filters for:

- Date Range
- Report Type
- Organizer
- Event
- Occurrence
- Ticket

These filters are intended for aggregated event analysis rather than individual booking or attendee records.

## Filter Dependency

Some filters depend on earlier selections.

For example:

1. Select an Organizer.
2. Event options can narrow to that organizer.
3. Select an Event.
4. Occurrence and Ticket options can then become available.

This prevents unrelated tickets or occurrences from being mixed into the report.

## Resetting Filters

When the current report results are too narrow or no longer useful, clear or reset the active filters and start again.

Resetting is especially useful after working with several dependent filters such as Event, Occurrence, and Ticket.

## No Results After Filtering

If no records are returned, one or more filters may be too restrictive.

Try:

1. Expanding the Date Range.
2. Removing the Ticket filter.
3. Removing the Occurrence filter.
4. Clearing status filters.
5. Confirming the selected Event.
6. Checking the report's date semantics.

## Filters Affect Exports

Report filters also determine which records are available for export.

If you filter the Bookings Report to one event and one payment method, an **Export All Filtered** action uses that filtered dataset.

Always verify your filters before generating an export.

## Export Current View

**Export Current View** exports the records represented by the current report page.

This is useful when you only need the currently displayed records.

## Export All Filtered

**Export All Filtered** exports all records matching the active filters, not just the visible page.

This is the better option when you need the complete filtered dataset.

## Export Scope in the Exports Tab

The Exports workflow also lets you choose between:

- All filtered results
- Current report page

This provides another level of control over the generated CSV.

## Preview Export

Use **Preview Export** before creating the final CSV.

The preview shows the matching row count and the first 20 matching rows.

This is one of the best ways to verify that your filters are correct before generating a large export.

## Filters and Background Exports

Large filtered datasets can be exported in the background.

The generated file appears under **Export History** after processing completes.

## Filters and Visible Columns

Filters control which rows appear, while the **Columns** control determines which fields are visible in the Bookings or Attendees table.

These are separate functions.

For example, you can filter to Stripe bookings and then hide Customer Phone or Coupon columns without changing which booking records match the report.

## Filters vs Export Columns

The same distinction applies to exports.

Filters decide which records are included, while export column selection decides which fields are written to the file.

## Example — Event Booking Report

To view completed bookings for one event:

1. Open **Eventixa → Reports → Bookings**.
2. Select the required Date Range.
3. Select the Event.
4. Set Booking Status to the required completed state.
5. Apply the filters.
6. Review the resulting bookings.

## Example — Ticket-Specific Report

To analyze one ticket:

1. Select the Event.
2. Select the Ticket.
3. Select an Occurrence if the event is recurring.
4. Apply any status or payment filters.
5. Review the results.

## Example — RSVP Going Report

To review RSVP guests who are Going:

1. Open the Bookings or Attendees report.
2. Select the Event.
3. Set Registration Type to RSVP.
4. Set RSVP Response to Going.
5. Apply the filters.

## Example — Checked-In Attendees

To find attendees who actually checked in:

1. Open **Eventixa → Reports → Attendees**.
2. Select the Event.
3. Select the Occurrence if relevant.
4. Set Check-In Status to Checked-in.
5. Apply the filters.

## Example — Stripe Bookings

To isolate Stripe transactions:

1. Open the Bookings Report.
2. Select the Date Range.
3. Select the Event if needed.
4. Set Payment Method to Stripe.
5. Apply Payment Status if needed.
6. Review or export the filtered records.

## Example — Coupon Campaign

To review bookings using a coupon:

1. Open the Bookings Report.
2. Select the required Date Range.
3. Select the Event if needed.
4. Choose the Coupon.
5. Apply the filters.
6. Review the matching bookings.

You can also use the **Coupon Usage** Operational Report for a count-based coupon summary.

## Example — Recurring Event Attendance

To analyze attendance for one recurring date:

1. Open **Operational Reports**.
2. Select **Occurrence Attendance**.
3. Select the Event.
4. Select the Occurrence.
5. Apply the Date Range if required.
6. Review Registered, Checked-in, Not Checked-in, and Check-in Rate.

## Example — No-show Analysis

To review no-shows for one event:

1. Open **Operational Reports**.
2. Select **No-show Report**.
3. Select the Event.
4. Select the Occurrence if recurring.
5. Apply the filters.
6. Review the resulting no-show data.

## Example — Current Ticket Capacity

To review one ticket's current capacity:

1. Open **Operational Reports**.
2. Select **Ticket Capacity**.
3. Select the Event.
4. Select the Ticket.
5. Review Capacity, Registered, Remaining, and Utilization.

Remember that changing the Date Range does not turn Ticket Capacity into a historical report.

## Recommended Filtering Workflow

A reliable filtering process is:

1. Choose the report section.
2. Select the correct Date Range.
3. Confirm what the Date Range means for that report.
4. Select an Organizer if relevant.
5. Select the Event.
6. Select the Occurrence if recurring.
7. Select the Ticket if needed.
8. Apply registration, status, payment, coupon, or check-in filters.
9. Review the results.
10. Adjust filters if the dataset is too broad or too narrow.
11. Preview the export before generating large files.

## Avoid Over-Filtering

Applying too many filters at once can easily produce no results.

If a report unexpectedly becomes empty, remove filters one at a time until you identify which condition excluded the data.

## Comparing Reports

When comparing two Eventixa reports, use equivalent filters where possible and confirm that both reports measure the same type of date and record.

For example, comparing Bookings created this month with Event Attendance this month is not a direct comparison because the first uses booking creation date while the second uses event date.

## Common Problems

### Date Range Shows Unexpected Records

Check which date field the current report uses.

Bookings use booking creation date, Attendees use registration date, and attendance-focused Operational Reports use event or occurrence date.

### Ticket Filter Is Missing

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

### Occurrence Filter Is Missing

Select a recurring Event first so Eventixa can load its occurrences.

### Report Has No Results

Expand the Date Range, reset status filters, remove Ticket or Occurrence filtering, and verify that you selected the correct Event.

### Booking and Attendance Reports Show Different Totals

This can be expected because they measure different records and can use different date semantics.

### Ticket Capacity Does Not Respond to Date Filters

This is expected because Ticket Capacity is a current snapshot.

### RSVP Report Includes the Wrong Responses

Set Registration Type to RSVP and then apply the required RSVP Response filter.

### Export Contains Fewer Records Than Expected

Check whether you used **Current report page** instead of **All filtered results**.

Also verify the active filters before exporting.

### Export Contains Too Many Records

Review the Event, Ticket, Occurrence, status, and Date Range filters before creating the export.

### Customer Search Does Not Find a Record

Verify the spelling of the customer name, email, or booking number and check whether other active filters are excluding the record.

## Important Notes

- Report filters require Eventixa Pro.
- Different report sections provide different filter sets.
- Date Range meaning changes according to the report type.
- Bookings use booking creation date.
- Attendees use registration creation date.
- Attendance-focused reports use event or occurrence date.
- Ticket Capacity is a current snapshot and does not use Date Range historically.
- Event selection can control available Ticket and Occurrence filters.
- Registration Type can separate Standard and RSVP records.
- RSVP Response can separate Going and Not Going.
- Booking and attendee reports support status and payment filtering.
- Attendees support Check-In Status and check-in date filtering.
- Operational Reports support Organizer, Event, Occurrence, and Ticket filters.
- Filters determine which records are available for export.
- Export scope and export columns are separate from report filters.

## Related Documentation

- [Reports Overview](https://eventixawp.com/docs/reports-overview/)
- [Event Reports](https://eventixawp.com/docs/event-reports/)
- [Ticket & Registration Reports](https://eventixawp.com/docs/ticket-registration-reports/)
- [Revenue Reporting](https://eventixawp.com/docs/revenue-reports/)
- [Managing Bookings](https://eventixawp.com/docs/managing-bookings/)
- [Managing Attendees](https://eventixawp.com/docs/managing-attendees/)
- [RSVP Tickets](https://eventixawp.com/docs/rsvp-tickets/)
- [Recurring Events Overview](https://eventixawp.com/docs/recurring-events-overview/)
- [Event Check-In](https://eventixawp.com/docs/event-check-in/)
- [Ticket Capacity and Availability](https://eventixawp.com/docs/ticket-capacity-and-availability/)