# How to Run a URL Test

### Preparation

#### 1. Create a URL Test

Go to the A/B Test tab > click the **\[Create New A/B Test]** button > click **\[URL Test]** in the modal to create a new URL Test.

![](/files/SONJbdesegirlCx8Cpr8)

#### 2. Enter the hypothesis to validate

Enter the hypothesis you want to validate through the experiment and a name for the experiment to create it.

![](/files/LAuwvjxZLshriYri9Scd)

#### 3. Enter group descriptions and URLs

In the URL Test detail screen, go to the **\[URL Settings]** tab to enter a description for each group and input the URLs, then save.

![](/files/0IpwF8Vw7K4kCZL8sXFn)

Group A is where the URL Test originates, so you can enter the URL of the existing version to be tested. The following advanced features are supported for Group A to configure the target in detail:

* **\[+ Add OR Condition]** setting: If there is more than one URL to set as the experiment target, you can enter multiple URLs via **\[+ Add OR Condition]**.\
  For example, if you set Group A: URL 1 `or` URL 2, all traffic entering either url 1 or url 2 becomes the experiment target.
* **Matching condition** setting: You can select the appropriate matching condition depending on the URL structure or the experiment scope.
  * **Exactly matches**: Enter the URL that exactly matches the URL you want to test.
    * Example input URL: `http://www.example.com/category/1/product/1/display/1`
    * Not allowed example 1: `http://www.example.io/category/1/product/1/display/1`
    * Not allowed example 2: `http://www.example.com/category/1/product/1/display/1/utm=source`
  * **Starts with**: All URLs that start with the entered URL become the experiment target.
    * Example input URL: `http://www.example.com/category/1/product/1`
    * Allowed example 1: `http://www.example.com/category/1/product/1/display/10`
    * Allowed example 2: `http://www.example.com/category/1/product/1?search_keyword=example&utm..`
  * **Contains**: If you want all URLs that contain a specific segment to be the experiment target, setting this condition will include any URL regardless of what comes before or after the entered string.
    * Example input: `promotion/best-seller/product/1/display/10`
    * Allowed example 1: `www.hackle.io/promotion/best-seller/product/1/display/10`
    * Allowed example 2: `www.hackle.co.kr/promotion/best-seller/product/1/display/10/utm=source`

Tip: Even if the URL contains Korean characters, it is compared the same as the encoded value, so you can enter URLs containing Korean characters without any issues.

#### 4. Check and insert the integration code

Click the **\[View Code]** button at the top, or view the integration code at the bottom of the **\[URL Settings]** tab.

Add that code inside the `<head>` of the page at the URL you want to test.

If you entered 3 URLs to test, you must add the code inside the `<head>` of all 3 pages for the experiment to work correctly.

![](/files/W79ERkVgbjlotwslC5nM)

![](/files/nYr33LyRE4OgeM3uw6e9)

#### 5. Set Metrics

Click **\[Set Metrics]** at the top to add metrics that measure the impact and success of this experiment.

![](/files/W8Px5ka1x0LhkwWTA7vQ)

#### 6. Set Targeting

Use **\[Set Targeting]** to define which users will be exposed to this experiment.

![](/files/9B35vU2fBAkA6uVjmlXo)

#### Mutually Exclusive Settings

If multiple experiments are running simultaneously or you want to manage traffic separately, you can configure mutually exclusive settings.

Mutually Exclusive Settings can be configured by clicking the **\[Mutually Exclusive Settings]** tab as shown in the image below.

![](/files/KfBziVBWjIoxAbZDv7n5)

### Running

Once preparation is complete, click **\[Start]** at the top to begin the URL experiment.

In the modal that appears, verify the URL, integration status, and other items to ensure a successful experiment.

![](/files/Fxf423WhMdRcN3Vbsdc3)

#### 1. Health Check

Before running the experiment, check the integration status, registered event delivery status, and more.

![](/files/jsq1nN8XmmWXApssOARs)

#### 2. Traffic Allocation

The traffic percentage to allocate to the A/B Test can be set from 0(%) to 100(%), and is distributed evenly (1/N) among the configured groups.

You can change the traffic percentage after the experiment starts, but note that you cannot set a lower value than the previously configured value.

![](/files/M8JjlBSm0UhLsJotrqJi)

#### Data Analysis & Result Interpretation

Once the experiment is running, detailed data for the configured **\[Metrics]** will be displayed.

Even if you add a metric while the experiment is in progress, that metric is calculated based on data from the test start time, so you can add it at any time during the experiment.

#### Changing the Status

Even after an experiment is running, you can use **Pause** or **Version Management**.

{% hint style="info" %}
If you are using GTM, you can follow the [Google Tag Manager Integration](broken://spaces/ezh7pUfOjUmS5W8txJ85/pages/QSs2jdh7abA8iyBlv9qh) guide to complete the integration process more easily.
{% endhint %}


---

# 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/url-test/steps-of-an-url-test.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.
