> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/analytics/analytics-dashboard/export.md). # Export The Spreadsheet view presents your creative's performance as a day-by-day table that you can download as a CSV. It's the quickest way to get your PLAY analytics into Excel, Google Sheets, or your own reporting tools. *** ### Opening the Spreadsheet View Open your creative's analytics and select **Spreadsheet** from the sidebar. The table uses the same **Export**, **Partners**, and **Date Range** filters as the rest of your analytics, so the numbers here always match what you see elsewhere in the dashboard. If you want the spreadsheet to cover a different window, adjust your date range or filters first. *** ### Reading the Table Each row is a single day within your selected date range, with dates running down the page. For every day, the table shows these metrics: * **Total Sessions** * **Sessions Engaged** * **Total Engagements** * **Layer Engagements** * **Other Engagements** * **Sessions Captured** * **Total Captures** **Sessions Captured** counts each session once, however many times the user clicked a CTA in it. **Total Captures** counts every capture, so it matches the Total Captures figure on the dashboard. {% hint style="info" %} The spreadsheet labels impressions as **Sessions**. **Total Sessions**, **Sessions Engaged**, and **Sessions Captured** match **Total Impressions**, **Impressions Engaged**, and **Impressions Captured** on the dashboard. {% endhint %} After the session metrics, there's a column for each layer in your creative showing that layer's interactions for the day. This makes it easy to see how individual layers performed over time, not just how the creative did overall. A **Total** row sits pinned under the header, summing every column across the whole date range so you can read the range totals without scrolling to the end. Sorting and paging never move it. For what each metric measures, see [Engagement Metrics](/analytics/analytics-dashboard/engaged/engagement-metrics.md) and [Captured](/analytics/analytics-dashboard/captured.md). *** ### Sorting and Paging * Click a column header to sort the table by that column. This is handy for surfacing your best and worst performing days, or ranking days by a specific layer's interactions. * Large date ranges are split into pages. Use the controls below the table to move between pages, and choose 25, 50, 100, or All rows per page. The default is 100. * The header row stays in place as you scroll, so you never lose track of which metric you're looking at. *** ### Downloading the CSV Click the **Download CSV** button in the header to save the table to your device. The file contains the same data shown on screen: the Total row right after the header, then one row per day with the session metrics and a column per layer, all scoped to your selected date range and filters. The file name includes the project, variant, date range, and company, so your exports stay easy to identify without opening them. {% hint style="info" %} *The CSV always reflects your current date range and filters. Set those before downloading if you need data for a specific window.* {% endhint %} --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.craftsmanplus.com/analytics/analytics-dashboard/export.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.