> 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/reporting-and-performances.md). # Reporting & Performances Key features include: * [Visual Campaign Results](/reporting-and-performances/reporting.md): Easily interpret campaign outcomes using dynamic data visualizations and color-coded indicators to highlight top-performing variations. * [Performance Center](/reporting-and-performances/performance-center.md): Monitor the size of the AB Tasty tag with guidelines to optimize performance. * [Experiments ROI dashboard](/reporting-and-performances/impact-dashboard/experiments-roi-dashboard.md): AB Tasty's strategic planning tool for measuring and projecting the financial impact of your experimentation campaigns. * [Data Explorer](/reporting-and-performances/data-explorer.md): Access and analyze detailed hit-level data, retrieve raw data, and create integrations with data warehouses. * [Learnings](/learnings.md): Create a library to collect campaign knowledge, including experiment results, insights, and subsequent actions. Get a better understanding of your website and visitor behavior. --- # 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.abtasty.com/reporting-and-performances.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.