> 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.md). # Analytics+ Package {% hint style="info" %} ### What's changing for Analytics+ packages: For years, Analytics+ delivered your data as a private Tableau workbook: a powerful set of dashboards that lived in a separate system with [its own login](https://docs.podplay.app/owners-playbook/analytics/analytics+-package/share-analytics+-credentials), its own load times, and its own learning curve. [**The Insights page**](https://docs.podplay.app/owners-playbook/analytics/insights-page) brings that same analytical depth directly into the Dashboard, one click from where you already build programming, manage Members, and run your Club. Nothing new to log into, nothing to export and reconcile. Everything you relied on in Analytics+ is here, faster and easier to find, and it now does something Analytics+ could not: it helps you decide what to do next. {% endhint %} ### Analytics+ Package Overview PodPlay's Analytics+ Package is an add-on that delivers a deeper view of Club performance than the basic Analytics page in the Dashboard. Data from your PodPlay instance syncs to a BigQuery Data Warehouse daily and is visualized through a set of Tableau dashboards built as a private workbook within the PodPlay Tableau instance, providing detailed insight into revenue and utilization trends. Availability depends on your PodPlay Plan — ask the Customer Success team for the password-protected Overview PDF for full details. {% hint style="success" %} This package is provided to all Pro and Autonomous(+) Tier Clubs. {% endhint %} #### Pricing * Monthly Fee: $100 #### Included Dashboards * Time Series: Capacity Utilization by Location * Heat Map: Capacity Utilization by Time Slot * Heat Map: Revenue by Day of the Week * Time Series: Revenues from New / Existing Customers * Pie: Total Revenue (Members vs. Non-Members) * Time Series: Average Revenue per Customer * Time Series: Spend per Type of User * Dashboard: Revenue by Coached / Non-Coached Users * Summary: Power Users * Window Series: Revenue, Utilization, and Yield * Window Series: Rolling Window Measurements * Time Series: Returning Users and Return Rate * Histogram: Time to next Reservation * Time Series: Number of Reservations * Time Series: Number of Users making Reservations * Time Series: Moving Average of Number of Users * Summary: Power Promos * Dashboard: Events and Programs * Time Series: CLTV Inputs * Summary: Performance by Window * Summary: Customer Payments and Zip Codes * Summary: Membership Dynamics * Time Series: Percentage of Reservations with Replays * Time Series: Free vs. Not Free Replays * Time Series: Average Replays in Reservations with Replays * Summary: Users, Reservations, and Revenue by Age * Basic Reports (7 different large, aggregated tables) --- # 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.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.