> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/orchestration/how-to-exclude-an-audience-from-your-targeting.md).
# How to exclude an audience from your targeting?
You can exclude a list of users' IDs from your targeting with audiences.
### 1. Create an Audience
There are three different ways to create an [audience](https://doc.batch.com/getting-started/features/customer-engagement-platform/profiles/audiences):
* Using the [**Audience API**](https://doc.batch.com/developer/api/cep/audiences/create)
* By [uploading a .CSV or .TXT file to Batch](https://doc.batch.com/guides-and-best-practices/profiles/how-to-import-an-audience-to-target-specific-users) from the dashboard **Data → Audiences** tab.
* Via the **Audience Importer**. The importer automatically imports audiences from your data stores via (S)FTPs *(Audience Importer setup is upon request. Reach support or your CSM to know more).*
{% hint style="info" %}
An audience can contain **Customer User IDs**, **Emails**, or **Install IDs**.
{% endhint %}
The dashboard will **automatically** **display the number of IDs** that match your audience:
### 2. Exclude it from your targeting
In your campaign/automation creation form, in the **Segmentation** part, click on **Use audience**:
Choose the audience you want to exclude in the dropdown menu:
Select "**contains none of**", so that the segmentation now excludes the audience you picked:
You can exclude as many audiences as you want:
You can now exclude audiences from your campaigns targeting! :sparkles:
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://doc.batch.com/guides-and-best-practices/orchestration/how-to-exclude-an-audience-from-your-targeting.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
