> For the complete documentation index, see [llms.txt](https://docs.pulseinsights.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulseinsights.com/configuring-pulse-insights-console/reporting/on-demand.md).
# On Demand
### Export Results
On the main Results page, click on the button to generate an XLSX file.
A modal will pop to show you the status of the download.
Once your report is reading you can click “Download the report” link to download the file. A copy of the report will also be sent to your email.
The export file contains the following report sheets:
* **Survey Metadata**: Survey name, author, reporting date range, date of report generation
* **Aggregate results by day**: the following metrics aggregated by day:
* Impressions
* Viewed Impressions (if enabled)
* Submissions
* Submission Rate
* **Questions/Response Summary Report**: number of submissions per question and per response. This breakdown also shows the percentage (or share) that a particular response has in comparison to total responses.
* **Individual Rows:** Each row in this sheet is an individual response. If a survey has multiple questions, then each response will be displayed as its own row.
* **Devices**: This sheet displays similar data to the Individual Rows sheet, but responses are grouped by device. So instead of each response displaying as its own individual row, the Devices tab groups all responses made from the same device. If a survey has multiple questions, all responses to the survey will display in one row for each device.
{% hint style="info" %}
For definitions of each data point, please visit our [Data Dictionary](/configuring-pulse-insights-console/reporting/on-demand/columns-data-dictionary.md).
{% 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://docs.pulseinsights.com/configuring-pulse-insights-console/reporting/on-demand.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.
button to generate an XLSX file.
A modal will pop to show you the status of the download.
