> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/owners-playbook/analytics/analytics+-package/basic-report-customer-activity-and-events.md). # Basic Report - Customer Activity & Events ### Glossery Overview The Customer Activity & Events basic report inside the Analytics+ package contains one row per Reservation, Event signup, or invitee record, with columns describing the booking, the people involved, and the resulting revenue. Each column header is described below so the data can be interpreted accurately when exporting or filtering the report. #### Identifiers and Event Metadata * **series\_id** — The ID of the Series. If you open a Series in the Dashboard, the ID is in the URL * **Event Id** — The ID of the Event. If you open an Event in the Dashboard, the ID is in the URL * **event\_name** — The name of the Event, visible to the Customer in the App and to staff in the Dashboard * **Event Type** — The type of Event. Also shown on the Purchase page Export and the Settlements CSV * **Location** — The venue location and the booking experience (pickleball courts, ping pong tables, etc.) * **Recurring / One Time** — If "Recurring" is selected, the Event is part of a Series. If "One Time" is selected, the row represents a single Event or a Reservation #### Date and Time * **Date** — The date the Reservation or Event occurred * **Weekday** — The specific day of the week * **Event Time** — The local time at the Club when the Event started * **Event Duration** — Length in minutes of the Reservation or Event * **# courts per event** — Quantity of courts associated with the Event or Reservation * **court\_names\_list** — Court shortname is pulled from your environment settings * **Week** — Which week of the year the Reservation or Event fell on (1–52) * **Month** — Which month the Reservation or Event fell on #### Status and Cancellation * **Event Status** — For an Event, the canceling person is an Admin; for a Reservation, the canceling person is the Customer who booked it * **Canceled By User** — True or False (Null = False). For an Event, the canceling person is an Admin; for a Reservation, the canceling person is the Customer who booked it * **Canceled At Date** — When the Event or Reservation was canceled. Only appears if the booking was canceled #### Revenue and Payments * **Revenue** — Total revenue generated by the Reservation or Event * **Cash** — Amount collected as cash * **Paid to Coach** — Amount paid to the Coach, when a Coach is attached to the Reservation or Event #### Capacity and Attendance * **# Members in Waitlist** — Null if there are no Members in the Event Waitlist * **# Non Members in Waitlist** — Null if there are no Non-members in the Event Waitlist * **Event Attendees** — Number of Customers in the attendee list of the Reservation or Event * **Available Spots** — How many available spots existed in the Event when it was first created {% hint style="warning" %} This column is being updated soon to reflect `updated_at` rather than `created_at`. After that change, Available Spots will reflect any later edits an Admin makes to the participant quantity in Event settings. {% endhint %} * **% Fill Rate** — Available spots in the Event versus the total Customers who signed up * **Is Locked** — Whether the court / table is locked. Always locked for an Event, and locked for a Reservation if the Customer locks it down during booking #### Reservation Holder (Reservation Owner) * **Resv Holder** — Name of the Customer who signed up, or the Reservation Owner if it is a private Reservation * **Booking Resv Holder Gross** — Amount paid by the Reservation Holder for the Reservation booking or Event signup * **When Resv Holder booked / signup at?** — For private Reservations, it is the time the Reservation was created; for Events it is the timestamp of when they signed up for the Event * **Resv Holder Email** — Email of the Customer who booked the Reservation * **Resv Holder Is Member** — Indicates whether the Reservation Owner pays for a Membership * **Resv Holder Membership Name** — The name of the Reservation Owner's Membership * **resv\_holder\_DUPR** — DUPR ID for the Reservation Owner * **resv\_holder\_current\_DUPR\_rating\_singles** — Reservation Owner's singles DUPR rating * **resv\_holder\_current\_DUPR\_rating\_doubles** — Reservation Owner's doubles DUPR rating #### Invitee * **Invitee In Private Resv** — Another Customer who was invited to a Reservation, or a Guest inside an Event signup * **Invitee accepted at** — timestamp of when the Reservation or Event invite was accepted by the invitee * **Signup Resv Holder Gross** — The gross amount paid by the user for an Event signup * **is\_checked\_in** — Whether the invitee has checked in to the Reservation or Event * **invitee\_canceled** — Whether the invitee accepted and then canceled their invite * **invite\_type** — `EVENT_SIGNUP` if the listed Customer signed up for an Event; `COACH` if the listed Customer is a Coach in an Event; `GUEST` if the listed Customer is a guest of the Reservation Owner * **Invitee Is Member** — Indicates whether the invitee holds a Membership * **Invitee Membership Name** — The name of the invitee's Membership * **Invitee Email** — The invitee's email address * **invitee\_DUPR** — DUPR ID for the invitee * **invitee\_current\_DUPR\_rating\_singles** — Numerical value for the invitee's singles DUPR rating * **invitee\_current\_DUPR\_rating\_doubles** — Numerical value for the invitee's doubles DUPR rating --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podplay.app/owners-playbook/analytics/analytics+-package/basic-report-customer-activity-and-events.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.