> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-engage/marketers-and-editors/ab-testing/monitor-the-ab-test.md).
# Monitor the A/B Test
Umbraco Engage provides the ability to continuously monitor the A/B tests you are running on your website. It is recommended to disable tests that perform poorly.
When the A/B test is running it is advised to check the progress regularly. This can be done on the specific page or via the Engage Section.
If you go to the overview you can see all running tests. The overview includes the following information:
* For how long a test has been running?
* How many visitors are included in the test?
* For how long should the test run to produce relevant results?
You can see all test variants when you access the details on a test. You can preview the variants, or disable them. If for example, the conversion rate has decreased in a variant, it could be smart to disable that variant.
The algorithm also signals the leading variant based on the Minimal Detectable Effect (MDE) which uses the 95% confidence level.
Algorithm signaling the leading variants.
---
# 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.umbraco.com/umbraco-engage/marketers-and-editors/ab-testing/monitor-the-ab-test.md?ask=&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.
