> For the complete documentation index, see [llms.txt](https://docs.saferpay.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saferpay.com/home/interfaces/backoffice/transactions/analytics.md).
# Analytics
In the Analytics area, you can view a report on your current transaction-volume. It also offers a wide range of filters, so you can analyze the activity on your account, through sorting by the time-frame, currency, terminal, the transaction state and more.
The view can either be configured, as a bar-chart or, by clicking on the respective symbol at the top right, as a pie-diagram.
## Advanced filters
The Advanced filters gives you even more control over what to display, by limiting it to a certain **Currency**, **Payment mean**, **Terminal**, or a specific State, as well a custom **Time period**.
## Export and printing
You can also either print this page, by clicking on the printer symbol, or you can export this data, to either a PNG, or a CSV-File.
### Examples
#### PNG
#### CSV
{% file src="/files/-McO4UxZXgCfjC8Ue5eZ" %}
Example CSV
{% endfile %}
---
# 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.saferpay.com/home/interfaces/backoffice/transactions/analytics.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.