> 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/metrics.md).

# Goal

> 🚧 The Goals tab is only available in the Production Environment.

## Goals tab

The Goals tab is the default tab displayed when you enter the A/B Test details in the **Production Environment**.\
Here you can see the goals configured for the A/B Test. After the test starts, collected data can also be viewed here.

> 📘 Data is updated every 1 hour.
>
> Please check at least 1 hour after starting the test.

## About goals

A goal is the means to measure the performance of an A/B Test — it is the measurement criterion (metric) used to determine whether the Treatment (Group B, C, D, ...) achieves better results than the Control (Group A).

For example, suppose a company is considering changing the color of the purchase button. The reason for the change is to get users to click the purchase button more.\
In this case, to verify whether the color change is effective and which color is more effective, they can run an A/B Test on the purchase button's color. So, how should the goal be configured?

First, since the change is only meaningful if the purchase button is clicked more, you can set 'purchase button click count' as a goal. Also, getting users to click the purchase button more is ultimately about increasing the purchase conversion rate, so 'purchase conversion rate' can also be set as a goal.

## More details

For how to set goals, refer to the following document:

* [Set Metrics →](/en/ab-test/create-and-configure/set-metrics.md)

For the meaning of items visible in the test results and how to interpret the data, refer to the following document:

* [Interpret Results →](/en/ab-test/data-analysis.md)


---

# 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.hackle.io/en/ab-test/metrics.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.