> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/ab-test/create-and-configure/start-ab-test.md).

# Start A/B Test

{% hint style="info" %}
The status of an A/B Test can be configured on the A/B Test detail page.
{% endhint %}

### Start an A/B Test

Click the **`Start`** button in the upper right of the detail page for an A/B Test that is in Draft status.\
In the popup that appears, set the traffic allocation level and click the **`Start`** button again. Users will then be exposed to the A/B Test according to the traffic allocation level.

![](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-88b9704bc650fd5340f675285b8ae3f597bd2ab0%2F54964ce-test-1-start_26ecf3c6ef69aa56.png?alt=media)

### When the events set in A/B Test goals are not being received

When you try to start an A/B Test, the following 2 items are checked. If either item is not satisfied, the screen shown below will appear.

Both items must be satisfied for the A/B Test to proceed as intended.

* Whether the A/B Test code is integrated and user identifiers are being sent
* Whether events required to calculate the results of registered goals are being sent

To resolve issues, refer to [Health Check](https://docs.hackle.io/en/ab-test/status/health-check.md).

![](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-3df3133a768a4690f7654f4872be8b5392a41c56%2Fe362947-healthcheck_b7f5d169e31ec945.png?alt=media)


---

# 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.hackle.io/en/ab-test/create-and-configure/start-ab-test.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.
