> 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/finish-an-ab-test.md). # Finish an A/B Test When the A/B test has enough data for a statistically complete picture, Umbraco Engage will notify you. You can also end the test at any time. You can decide to finish an A/B test at any time. Normally, you would end a test if it has been running long enough and enough data to gain enough confidence is collected. Umbraco Engage lets you know when the collected data is statistically significant. The same applies to when not enough data is collected. Even if not enough data is collected you can always decide whether a running A/B Test is complete. In the overview you can see all tests and their performance:

To end a test, click **End test**. This will open a confirmation dialog asking if you want to pick a winner directly. You might want to discuss the results with a colleague or client. In that case, it makes sense to stop the A/B test, but complete it by picking a winner at a later point.

If you select **Stop and complete now** the A/B Test is stopped and you can select which variant was the winner:

Completing the test removes all variants and their content from the page. Select the winning variant and then **Confirm**, or select **End without a winner**. For a Single page test, also choose what happens to the winner's content: * **Replace the page content and publish** * **Replace the page content and save as draft** * **Keep the page as it is** After you confirm, the test is listed as **Completed**, with the winning variant marked:

The overview of the A/B tests will also show that the A/B Test is stopped and a winner was selected:

--- # 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/finish-an-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.