> 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/data-and-security/export-data.md). # Export Data ### Overview There are six (6) pages in the Dashboard the Owner/Admin role can export, and each of these pages in the Dashboard houses different information. {% hint style="warning" %} **Only a Profile with the Owner & Admin role can export from the Dashboard**. If you have the Admin role and not the Owner role, you can see everything in the Dashboard and cannot export data. {% endhint %} To export a CSV from any of these pages, click on the `Export` button at the top of the page.
A pop-up window will appear and you can select the window of time you want to download.
{% hint style="success" %} **If you are filtering the page before export, you will retain the filters. Meaning, data not included in the filters is not downloaded.** {% endhint %} ### Exporting the Events Page When exporting data from the Events page of the Dashboard, a CSV is downloaded to your computer. This CSV has information pertaining to Events and programming created at your Club. The `Export` button is available on both the List tab and the Calendar tab of this page. For any filters applied, data is excluded and only the visible data filtered-for will download.
What information is in the Events page CSV when downloaded? Name of the Event, Event type, start time, end time, day of the week, location, list of any tags added to the event, published or draft status, total capacity, total attendees, fill rate (as a % value), quantity of Non-member attendees, quantity of Member attendees, % of Member attendees, quantity of Customers in the Waitlist, names of Coaches (if any are connected to the Event), Member rate of sign-up, Non-member rate to sign-up, total revenue generated from the Event, # of courts utilized, court names, if the Event was canceled, and cancellation reason selected.
### Exporting the Customer Page When exporting data from the Customer page of the Dashboard, a CSV is downloaded to your computer. This CSV has each Customer's information by rows. If you have 100 Customers, there will be 101 rows in the spreadsheet. The top row is the headers describing what is in each cell beneath. There are two sections on the Customer page to export: 1. All Customers 2. Members #### All Customers By exporting Customer data while on the All Customers tab, you will download a CSV file with all Customer information (excluding data based on any filters applied).
#### Members By exporting Customer data while on the Members tab, you will only download a CSV with Member information. Members are Customers who are paying your Club a subscription. For any filters applied, data is excluded and only the visible data filtered-for will download.
### Exporting the Coach/Robot Page When exporting data from the Coach/Robot page of the Dashboard, a CSV will download with rows for each Clinic of private Lesson with a Coach. Coaches are added to private Lessons by the Customer when they book a Lesson. Coaches are added to a Clinic (or any Event) when they are added by an Admin in the Dashboard. {% hint style="success" %} If you are filtering the page before export, you will retain the filters. {% endhint %}
The Coach/Robot page export is helpful for understanding how much each Coach was paid or needs to be paid. To learn more, reach about [Coach payouts during revenue reconcilation](/owners-playbook/accounting-and-stripe/revenue-reconciliation.md#notes-on-coach-payouts) and [1099s for Coaches](/owners-playbook/accounting-and-stripe/revenue-reconciliation/1099s-for-coaches.md). {% hint style="info" %} **A Coach can also export from this page**. The downloaded CSV shows the Coach only the private Lessons and Clinics where they taught. {% endhint %} ### Exporting the Purchase Page With PodPlay acting as a system of record, all Customer transactions are housed and can be reviewed in the Settlements CSV downloaded to your computer when exporting the Purchase page of the Dashboard. {% hint style="success" %} If you are filtering the page before export, you will retain the filters. {% endhint %}
To learn more, read about the [Settlements CSV](/owners-playbook/accounting-and-stripe/revenue-reconciliation/settlements-csvs.md) and [revenue reconciliation](/owners-playbook/accounting-and-stripe/revenue-reconciliation.md). ### Exporting the Promo Code Page The downloaded CSV houses all of the same information that is visible on the Promo Code page, like: Status, name of Promo Code, Description, Tags used, which venues the Promo Code applies to, how many are left to be used (NA if there is no limit), how many times it has been used, the value off, and who created the Promo Code. ### Exporting the Insights Page To learn more, read about [the Insights page](https://docs.podplay.app/owners-playbook/analytics/insights-page). --- # 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/data-and-security/export-data.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.