> For the complete documentation index, see [llms.txt](https://docs.ixkio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixkio.com/features/stats.md).

# Stats

Statistics can be downloaded at the Active Folder, Tag Group, Batch and the individual Tag level. Navigate to your chosen level e.g. <mark style="color:orange;">Folder Data / Tag Group Data / Batch Data / Tag Data Panel > Stats Tab.</mark>

From here, select a date or a range of dates you're wanting to download. Then select Download Stats. This download will be in a CSV file.

### CSV Download

Statistics include:

| Column          | Explanation                                                      |
| --------------- | ---------------------------------------------------------------- |
| Date & Time     | The date and time an action occurred                             |
| Tag Code (XUID) | Which Tag Code was scanned                                       |
| Tag Name        | Your Tag Name                                                    |
| Location        | Which Active Folder, Tag Group and Batch the Tag code belongs to |
| Response Type   | Redirect, Direct Response or API                                 |
| Method          | NFC Tag or QR Code                                               |
| User            | User name if scan made by registered user                        |


---

# 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.ixkio.com/features/stats.md?ask=<question>&goal=<user_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.