# Labels

Labels have two main purposes:

1. **Marketing pressure limit**: You can set a specific marketing pressure limit on all the campaigns attached to the same label (e.g. no more than 1 push a week for all campaigns using the "onboarding campaigns" label).
2. **Filtering**: You can filter the list of your campaigns based on the labels attached to your campaigns (e.g. "onboarding campaigns"):

{% hint style="info" %}
Restricted to users with **App** or **Administrate** rights.
{% endhint %}

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

## Creating a Label

You can create as many labels as you want. Every label you create has: 

* **A code**: Unique id of a label. Use it as a reference in your calls to the Batch API. Avoid editing label codes. By changing a label's code, you might trigger errors on your API calls if you don't update them with the new name. This may also reset the frequency capping limits on running campaigns already using this label.
* **A name**: Used to identify your label on the dashboard.

## Managing Labels

You can edit the code and the name of existing labels or delete them if needed. Batch shows the number of orchestrations attached to each label so you can understand the impact of deleting or modifying one.

{% hint style="info" %}
Note that labels created in the Omnichannel tab can be leveraged in Email, SMS, In-app v2 and Push v2 orchestrations. Labels created in iOS, Android and Web tabs are related to Push v1, siloed by platform.
{% 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://doc.batch.com/getting-started/features/customer-engagement-platform/settings/labels.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.