> 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/flagship-deprecated/faq/can-i-make-a-comparison-for-each-reporting.md).

# Can I make a comparison for each reporting?

### What is a reporting comparison?

A reporting comparison is used to analyze different variations of a feature. It allows our Bayesian algorithms to accurately determine which variation will perform best in terms of earnings, conversion rate and so on.

### Which use case is it available for?

Being able to compare several variations is only applicable for **A/B tests**.\
In **Feature toggling**, there is no variation to compare when doing feature management, as we are evaluating the individual performance of the feature itself.\
For **personalization**, we are mainly looking to create several scenarios for specific audiences, and separately analyze their performances.\
For **progressive rollout,** we are looking to deploy a feature gradually to your users and want to measure the effectiveness of the feature deployment.


---

# 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/flagship-deprecated/faq/can-i-make-a-comparison-for-each-reporting.md?ask=<question>&goal=<endgoal>
```

`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.