> 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/reporting/troubleshooting-how-can-i-know-my-test-is-reliable-and-my-data-significant-enough-to-be-analyzed.md).

# \[Troubleshooting] How can I know my test is reliable and my data significant enough to be analyzed?

When running an experimentation on your users, you must wait until Flagship has **collected enough significant data** before analyzing the reporting of your campaign in order to **get reliable insights**.

| <p>⭐ Good to know</p><p>We recommend following three business rules before making a decision after running an experiment:<br>- waiting until you have recorded at least 5,000 unique visitors per variation;<br>- letting the test run for at least 14 days (two business cycles);<br>- waiting until you have reached 300 conversions on the primary KPI.</p> |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

Flagship’s reporting displays a statistical reliability index that enables you to know if your test is statistically reliable. We recommend reaching the ‘Reliable’ status before making any firm and definitive decision.

![Flagship\_reliability\_status.png](https://195542843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPLcJUpntQruhbI1jQ2kr%2Fuploads%2Fgit-blob-9d7e65e2ca47a7f41746dc6e07b242c0ce698f33%2F226cf2854fcb4d63263e01248c886545.png?alt=media)

If this label is not displayed, it means that one or several of the rules mentioned above have not been complied with.

We also strongly recommend leaving a test active for at least the amount of time related to your business cycle. This time may be estimated at several days for classic e-commerce websites (browsing, verification, purchasing), but may take several weeks for less traditional websites (e.g.,: B2B activities, large purchases, etc.).

Not every test gives reliable results, and sometimes, you may have to pause some of them due to low statistical reliability, because the tested hypotheses have no impact on your conversion rate.

The elements that indicate a low reliability rate are the following:

* A very small difference between the original’s conversion rate and the variation,
* A too significant gap between the 2 confidence intervals
* Results that are chaotic time-wise (the average conversion rate curves overlap regularly from the start of the test).

**Need additional information?**

Submit your request at <product.feedback@abtasty.com>

Always happy to help!


---

# 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/flagship-deprecated/reporting/troubleshooting-how-can-i-know-my-test-is-reliable-and-my-data-significant-enough-to-be-analyzed.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.
