> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/recommendations-and-merchandising/getting-started/reporting.md).

# Reporting

This section outlines the main reportings of your Recommendations & Merchandising strategies, with guidance to use each effectively.

The Reporting section gives you direct access to performance analysis for your Recommendations & Merchandising setup. through two dedicated dashboards: 

* **Merchandising reporting** – Analyse the impact of your merchandising configurations.
* **Recommendations reporting** – Track the performance of your recommendation strategies.

Each dashboard is available in its own space, with its own set of KPIs, filters, and export options. The Reporting section simply provides shortcuts to reach them quickly.

{% content-ref url="/pages/hX0UPpUzvkBs6BxnyFjI" %}
[Merchandising Reporting](/recommendations-and-merchandising/getting-started/merchandising/merchandising-reporting.md)
{% endcontent-ref %}

{% content-ref url="/pages/AQfpiCBz8CQnLeNhAgGm" %}
[Reporting Recommendation](/recommendations-and-merchandising/getting-started/recommendations/reporting-recommendation.md)
{% endcontent-ref %}


---

# 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.abtasty.com/recommendations-and-merchandising/getting-started/reporting.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.