Park Attendance

Park Attendance – Report Guide

Park Attendance

Report Guide for Users

What this report shows, how to run it, and how to read the results.

What this report is for

The Park Attendance report shows who came into your park, based on their scans — tickets, sessions, entrance passes, and more. It’s the most flexible of the attendance reports: you can see high-level totals, a detailed list of every scan, or both, and you can filter and group the data many different ways.

Use it to understand attendance volume, find your busiest times, and look up exactly who scanned in and when.

This report has a lot of options. You can leave most of them at their defaults and only change the few that matter for your question.

1. Choose the time period and location

Setting What it does
Start Date / End DateThe period you want to look at.
LocationChoose one or more locations. You can pick several at once.

2. Choose the view and layout

Setting What it does
View ByChoose Summary and Details, Summary Only (just the totals), or Details Only (just the scan-by-scan list).
Details Group ByHow the detailed list is organized: Records (each scan), Hour, Date, or Week.
Columns To ShowPick which columns appear in the details table. Choose only the ones you need (see the list below).

3. Choose how scans are counted

Setting What it does
Ticket’s ScansControls which scans count for a ticket: All scans, the first scan, the last scan, the daily first scan, or the daily last scan. Use first/last to count one visit per ticket instead of every scan.
Use GuestWhen a ticket was bought by one person for another, this decides whose name to attribute the attendance to — the purchaser, the recipient, or one falling back to the other.

4. Narrow the results (optional filters)

All of these are optional — use only the ones that help. Leave the rest blank to include everything.

Filter What it does
TypeLimit to a kind of attendance (for example ticket, session, or entrance).
Scan ResultLimit to certain scan outcomes (for example accepted or denied).
Is Checked InFor events/sessions, limit to those that were checked in (or not).
Ticket / SessionLimit to specific ticket types or sessions.
Entrance EntitlementLimit to a specific entrance pass or entry type.
Item Category / ItemLimit to items in a category, or to specific items.
EmployeeLimit to scans handled by specific employees.

Columns you can show

In the details table you can turn columns on or off with “Columns To Show.” The most useful ones include:

Column What it tells you
Scan Date / Scan TimeWhen the scan happened.
Scan CountHow many scans are represented by the row.
Scan ResultWhether the scan was accepted or denied.
TypeThe kind of attendance (ticket, session, entrance, and so on).
Ticket Type Name / Item NameWhat was scanned.
Entrance EntitlementThe entrance pass used.
Barcode / Ticket IdIdentifiers for the scanned ticket.
Guest Name / Email / PhoneWho attended and how to reach them.
Employee NameWho handled the scan.
Is Checked InWhether the event/session was checked in.
Transaction Id / Transaction DateThe purchase behind the scan — useful for tracing.

Address fields (street, city, state, country, zip) and account details are also available if you need them.

How to use it, step by step

  1. Set your Start Date, End Date, and Location(s).
  2. Pick a View By: Summary Only for totals, Details Only for the full list, or both.
  3. If using details, choose Details Group By (Records, Hour, Date, or Week) and tick the Columns To Show you want.
  4. Choose how scans are counted with “Ticket’s Scans” — use first/last to count one visit per ticket.
  5. Add any filters (Type, Ticket, Entrance Entitlement, and so on) to narrow the results, then run the report.

Good to know

  • If a guest scans multiple times, “All scans” counts each one. Use a first/last option to count one visit per ticket — important for accurate attendance numbers.
  • Summary Only is fastest for a headline attendance number; switch to Details when you need to see individual scans.
  • Turn off columns you don’t need — a shorter details table is easier to read and quicker to load.
  • Grouping details by Hour or Date is the quickest way to find your busiest times.
  • The report counts scans (actual entries), not ticket sales.

Tip: for a clean attendance count, use a first/last scan option so repeat scans of the same ticket aren’t counted twice.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.