> For the complete documentation index, see [llms.txt](https://docs.adalysis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adalysis.com/tools/ad-testing/multi-ad-group-testing/testing-by-label.md).

# Testing by label

Multi ad group testing using labels helps you to split-test **sets of ads** across multiple ad groups or campaigns. Labels allow you to include and exclude ads as needed.

This approach can be **useful for low-volume accounts** that don’t accrue enough data to reach statistical significance with [single ad group testing](/tools/ad-testing/single-ad-group-testing.md). 

### **How to run multi ad group tests with labels**

<figure><img src="/files/yT1VENnPHzFAeS3HfSXl" alt="" width="563"><figcaption></figcaption></figure>

Go to **Ad testing** > **Multi ad group** > **By label**

1. Select your campaigns and the date range for this test. A common date range means Adalysis will calculate a date range during which all ads within the test were active.
2. Specify the ad labels you want to use or exclude for comparing your ad performance.
3. Click **Find current winners**. &#x20;
4. If you want Adalysis to run this test automatically, click **Save & run this test daily**.  The test definition will then appear in the **Automated test definitions** tab and the daily test results will appear in the **Automated test results** tab.

{% hint style="warning" %}
When using a **common test date range**, if one matching ad out of many was enabled only a few days ago, it will cause the whole test to run using only the last few days of data.&#x20;
{% endhint %}

#### **Bulk actions**

You can pause all ads with the losing label(s) for a specific metric. Once you pause the ads, the test results will be saved under the **Archived test results** tab.&#x20;

<figure><img src="/files/UigHpYZNWwHLZnNafbAX" alt="" width="483"><figcaption></figcaption></figure>


---

# 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.adalysis.com/tools/ad-testing/multi-ad-group-testing/testing-by-label.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.