# Common Area

## Overview

This document covers the top common area visible when entering the A/B Test detail view.\
The content of the common area differs depending on the A/B Test status. The general layout is explained first using the Running state as an example, followed by differences per status.

## Components

### Production Environment

![](/files/PbT8qAUTKu5dlbPtQfWU)

1. You can view the Experiment Key information and the A/B Test's name and description (if entered).
2. Several features related to the A/B Test are provided. See the **`Additional Features`** section below for more details.
3. You can receive email alerts when there are anomalies in the running A/B Test data.
4. You can see the current status of the A/B Test, along with the date and time the status was last changed.
5. You can check whether the A/B Test is running correctly.
6. You can see the Targeting settings for the A/B Test. When in Draft, you can create a new setting or modify an existing one.
7. You can see the User Identifier, which is the criterion used to assign users to each group in the A/B Test.
8. You can set the Traffic Allocation value for the A/B Test or view the currently set value. Traffic Allocation can only be configured while the A/B Test is in the Running state.
9. You can see the total number of users exposed to the A/B Test. This appears once the test enters the Running state.

#### Additional Features

Clicking the **`...`** button to the right of the A/B Test name displays up to 4 menu items.

![](/files/Oi85ijnxlWIBEmyrdBi2)

1. **Edit A/B Test Name**: Edit the name or description of the A/B Test.
2. **Duplicate A/B Test**: Creates a copy of the A/B Test.
3. **Export Data**: Available only on paid plans (Pro plan or higher). Provides Variation Distribution data and event data for the A/B Test.
4. **Archive A/B Test**: Changes the A/B Test to Archived status. This menu only appears when the A/B Test is in the Stopped state and in the Production Environment.
5. **Version**: Add a new version of the A/B Test or review previous versions. This feature preserves the Experiment Key and reverts the status to Draft, minimizing code changes when restarting an A/B Test.

### Development Environment

![](/files/B45gssoYetSLdkAD41va)

In the Development Environment, the Experiment Key information and the A/B Test's name and description (if entered) are always visible regardless of the A/B Test status. Clicking the **`...`** button on the right reveals additional features, and you can configure **Targeting** conditions and Traffic Allocation levels.

{% hint style="warning" %}
Targeting conditions in the Development Environment and Production Environment operate independently.

Targeting conditions set in the Production Environment apply only to the Production Environment. After starting a test in the Production Environment, you cannot change Targeting conditions in the Development Environment.

Traffic Allocation settings in the Production and Development Environments also apply independently to their respective environments.
{% endhint %}

## Differences by Status

The components of the common area differ somewhat depending on the A/B Test status.\
This section explains the differences per status.

### 1. Draft

Common items in Draft state are as follows:

* Traffic Allocation cannot be configured.
* Total exposed user count does not appear.

#### SDK not integrated and no goal set

![](/files/If5Atl8O7BBEjO5bHD5M)

* Message 1: A prompt to integrate the SDK appears when the SDK has not been integrated. This prompt disappears once Hackle confirms the SDK integration.
* Message 2: When in Draft state and no goal has been set, a goal setup prompt appears. This prompt disappears once the goal is configured. The \[Start] button does not appear until a goal is set.

### 2. Running

![](/files/Vn8rWxAOEa9QjHY0MTKo)

* Buttons to pause or stop the A/B Test appear.
* The Health Check is displayed. If there is an issue, refer to the [Health Check](/en/ab-test/status/health-check.md) document for resolution steps.
* A Traffic Allocation button appears. You can use this button to change the Traffic Allocation value.
* You can see the total number of exposed users.

### 3. Stopped

![](/files/NTVeXn1oA3aVGJ15M7mC)

* The Traffic Allocation area disappears, and you can see the Winner group selected at stopping, as well as the reason and account for stopping the test.
* You can see the total number of exposed users.

### 4. Archived

![](/files/S6NovaHXmrBayw6GJxBU)

* No status change buttons appear.
* The Traffic Allocation area disappears, and you can see the Winner group selected at stopping.
* You can see the total number of exposed users.


---

# Agent Instructions: 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:

```
GET https://docs.hackle.io/en/ab-test/management/ab-detail-top.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.