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

# Labels

Adalysis supports labels at the **account, campaign, ad group,** and **ad** level. You can apply them manually or automatically, based on your [alert settings](/tools/audit/how-to-customize-prebuilt-alerts.md). Labels also play a key role in [multi-ad group testing](/tools/ad-testing/multi-ad-group-testing.md).

Update your labels under **Manage** > **Labels** within an individual account.

{% hint style="info" %}
Adalysis doesn't support MCC labels, but you can use [account tags ](/onboarding/getting-started/core-account-settings/account-tags.md)instead.
{% endhint %}

### Adding, refreshing, and deleting labels

<figure><img src="/files/HdimnTx2ubfuSjtH0hEw" alt=""><figcaption></figcaption></figure>

You'll also see options for adding labels across the platform, including:

1. **Audit alert settings**<br>

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

2. **Labels menu**<br>

   <figure><img src="/files/x7cmUOsqBy3RPOW1qV8f" alt="" width="413"><figcaption></figcaption></figure>

### Filtering by label

Look out for the **Filters** menu across the platform. Click **Create filter** and search for 'labels'.

<figure><img src="/files/fF6GAlW6kZxQetLh2ni2" alt="" width="400"><figcaption></figcaption></figure>

<figure><img src="/files/2JWgwLcvvMg2S7xZiYZL" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
You can use labels when defining budgets, performance monitors, multi ad group tests, as well as in the Performance Analyzer.
{% endhint %}


---

# 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/manage/labels.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.