The Park Attendance report is a robust report to get attendance at your facility using many parameters to account for the different ways customers track attendance. For example, you may grant access to your facility with barcoded tickets, membership cards, sessions, sessions with barcoded tickets, events, events with sessions (ie. waterfall), etc. Your particular attendance number may include only sessions checked-in with will call, but not the tickets tied to those sessions, or you'd result in a double count. Or maybe you have waterfall events where each attendee of an event also has a session, so you want to count just one or the other, but not both to avoid a double count. This report accommodates those scenarios, and as a result, there are many parameters.
Definitions
Access Control - see definition of Scan.
Scan - a scan of a ticket or membership barcode through the access control activity, a validate/scan selection in guest management activity, and a validate/scan selection in will call activity.
Parameters
Start Date - start date of attendance in range
Type - select the types of attendance items you want to include in your counts.
- Sessions only
- Events only
- Access control - a scan of a ticket or membership barcode through the access control activity, a validate/scan selection in guest management activity, and a validate/scan selection in will call activity.
- Waterfall (events where event attendees also have a session)
Scan Result: select whether you want to include only approved scans, only denied, N/A, or all. N/A is the value for attendance activities where there is no physical scan, such as with sessions and events.
Session: include only sessions where there is not also a ticket, include sessions where there is a ticket, include sessions where there is no corresponding ticket that has been scanned, include sessions where there is a corresponding ticket that has been scanned.
Is Check In: guests with a session can check in via will call. Select whether to include only checked in sessions or only sessions not checked in or all.
Item Category: select which item categories you'd like to include in the attendance report
Employee Name: select which employee who performed the attendance action
View By: select whether you want to see details of the attendance count, summary information or both.
End Date: end date of attendance in range
Scans: select which types of access control scans you'd like to include.
- Include guest membership scan - includes scans of guest memberships
- Include guest account membership scan - include scans of guest account memberships
- Include ticket group scan - include scans of a ticket generated in a ticket group as an attendance count.
- Include manual scan - include manual approvals (button used in access control when you don't have a valid barcode, but you grant access to your facility manually)
Ticket: include ticket scans where there is no corresponding session, or include ticket scans where there is a corresponding session
Entrance Entitlement: select the entrance entitlements you'd like to include in the attendance count
Item: select which sellable items you'd like to include in the attendance report
Use Guest: In cases where it is available, some of the fields in the result set can include information about the guests in the attendance count. There can be a guest on the purchase and a guest to whom the purchase is assigned, such as guest memberships where a parent makes the purchase, but assigns the guest membership to a child. This field allows you to decide which guest's information you want to return in the results.
Columns to Show: when the View By parameter has details selected, a table is displayed. Select the columns you'd like to view.
Fields (Detail View)
Scan Id: each access control record has a Scan Id
Scan Result: Approved, denied, or N/A. N/A is the value for attendance activities where there is no physical scan, such as with sessions and events.
Script Name: a short description of the Scan Result. The available script names and the default script text displayed to the guest follow:
- Approved Script Names
- Approved Script: Welcome to the facility! Hope you enjoy your time
- ScanOut: Scanned Out.
-
The following script names are only used for the Alvarado integration. When the Alvarado is offline, it will queue the ticket barcodes (or membership barcodes), and once back online, it sends the on to Aluvii to the access control to be validated. There are 4 Offline Scripts:
-
Offline Approved Ticket Invalid: When a ticket was scanned offline and the device showed approved, when it finally hit the access control after coming back online, the ticket was actually invalid.
-
Offline Approved Ticket Valid: When a ticket was scanned offline and the device showed approved, when it finally hit the access control after coming back online, the ticket was actually valid.
-
Offline Approve Membership Invalid: When a memberships were scanned offline and the device showed approved, when it finally hit the access control after coming back online, the memberships were actually invalid.
-
Offline Approved Membership Valid: When a memberships were scanned offline and the device showed approved, when it finally hit the access control after coming back online, the memberships were actually valid.
-
- Denied Script Names
- Already Used: Sorry, but it appears that you have already used your pass today
- No Active Membership: Sorry but you do not have an active membership
- Invalid Barcode: It appears that your barcode is invalid! Please see our guest interaction specialist
- Invalid Owner: It appears that your barcode has no valid user! Please see our guest interaction specialist
- Ticket Complete: Sorry, but it appears that you have already used your Ticket.
- Already Used: Sorry, you have already used this Ticket at this Entitlement
- Ticket Expired: Sorry, but your Ticket has expired.
- Invalid ticket entitlement: Sorry, but your Ticket is not valid at current Entrance.
- Entrance Invalid For Today: Sorry, but membership's entitlement is invalid for today.
- Restricted Time: Ticket entered cannot be used at this time. It is currently not in allowed time period (TIME)
- Day Restriction: The ticket {0} is not valid on {1}
- Invalid membership entitlement: Sorry, but your Membership is not valid at current Entrance.
- MaxScanPerDay: Ticket has already been scanned for the maximum allowed limit({0}) for the day.
- MembershipExpired: Sorry, but your membership has expired.
- MembershipConsumed: Sorry, but your membership has already been consumed.
- MembershipMaxScanPerDay: Sorry, but your membership has already been scanned for the maximum allowed limit({0}) for the day for this entitlement.
- MembershipMaxScan: Sorry, but your membership has already been scanned for the maximum allowed limit({0}) for this entitlement.
- MembershipDayRestriction: Sorry, but your membership is not valid on {0}.
- MembershipRestrictedTime: Sorry, but your membership cannot be used at this time. It is currently not in allowed time period (TIME).
- MembershipFutureStartDate: Sorry, your membership cannot be used at this time. this memebership having future start date(DATE).
Type: see Type parameter
Barcode: barcode number scanned
Ticket Id: Unique TicketId for the ticket scanned
Ticket Type Name: ticket type name
Transaction Id: TransactionId of the original purchase
Signed Waiver Id: SignedWaiverId of the waiver tied to the session
Scan Date: date of the attendance count. For access control this is the date scanned. For sessions and events this is the end date of the session or event.
Scan Time: time of the attendance count. For access control this is the date scanned. For sessions and events this is the end date of the session or event.
Session End Time: scheduled end time of the session
Entrance Entitlement: entrance entitlement name
Item Name: name of the sellable item associated with the attendance count
Guest Id: guestId of the guest as selected in Use Guest parameter
Guest Name: first and last name of the guest as selected in Use Guest parameter
Guest Last Name: last name of the guest as selected in Use Guest parameter
Guest First Name: first name of the guest as selected in Use Guest parameter
Guest Email: email of the guest as selected in Use Guest parameter
Guest Account Id: guestAccountId of the guest as selected in Use Guest parameter
Guest Account Name: guest account name of the guest as selected in Use Guest parameter
Guest Phone: primary phone, or if not available, secondary phone of the guest as selected in Use Guest parameter
Primary Street Address: primary street address of the guest as selected in Use Guest parameter
Secondary Street Address: secondary street address of the guest as selected in Use Guest parameter
City: city of the guest as selected in Use Guest parameter
State: state of the guest as selected in Use Guest parameter
Country: country of the guest as selected in Use Guest parameter
Zipcode: postal code of the guest as selected in Use Guest parameter
Is Checked In: check in status of the session
Employee Name: employee that performed the attendance action
Reconciling Park Attendance 2.0 to Will Call Activity
To match this report to the session numbers in the will call activity, set the report parameters as follows:
1. Only select "Sessions" for the Type parameter
------------------
2. "Select All" for the Session parameter.
(But you can also select the option that would fit what you're looking for.)
------------------
3. Select "Summary and Details" for the ViewBy parameter.
------------------
4. Then select the needed columns.
The basis info you need to replicate Will Call modules are:
-Transaction ID
-Signed Waiver ID
-Scan Date
-Scan Time
-Session End Time
-Guest Name
-Is Checked In
The screenshot shows the columns that you need to match the data in the Will Call module with some extra information. But this is customizable to your need.
After setting the parameters, run the report.
Now the following screenshots will show the info from the Park Attendance 2.0 BETA report vs the info from the Will Call module.
*The ProductName summary shows the sum per product similar to the Capacity in the Will Call module.
* Matching the information between Park Attendance 2.0 BETA report vs Will Call module.
Comments
Please sign in to leave a comment.