> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/audiences/building-an-audience.md).

# Building an audience

Add filters and destinations, review the estimates, then run the audience to sync it to your ad platforms.

An audience is a set of people you want to target, defined by filters. Start one with **Create Audience** on the **Audiences** page.

## Adding filters and destinations

Add [filters](https://support.sayprimer.com/primer/audiences/audience-filters.md) in the **Filter Criteria** card to define who's in the audience, and pick the **destinations** — the ad platforms you want to sync it to. You can also describe who you want in the chat box under the filters: Primer drafts the filters, and you apply them or keep editing.

The [estimates](https://support.sayprimer.com/primer/audiences/estimates.md) update as you edit, so you can see the shape of the audience before you run it. Switch between the **Summary**, **Preview**, **History** and **Validation** tabs to see each view of it.

## Running the audience

When the audience looks right, click **Apply & Run** in the top-right header. Before the run starts:

1. Primer runs [audience validation](https://support.sayprimer.com/primer/audiences/audience-validation.md). If it finds issues, it shows them so you can fix them or carry on.
2. **Confirm Modifications** lists the filters you added, changed or removed, with a short summary you can edit. The summary is kept in the audience's [history](https://support.sayprimer.com/primer/audiences/audience-history.md).
3. The run starts after a short countdown. Click **Cancel** during the countdown to stop it.

An audience with no destination selected has nothing to sync, so **Apply & Run** only saves it.

## Changing an audience after it has run

Edit the filters and click **Apply** to rebuild the audience with the change. When you add a destination, the button reads **Rerun** instead. Until you apply a change, your ad platforms keep the previous version of the audience.

## From run to campaign

A new audience starts as a **Draft**, moves through **Running** while Primer builds it and **Matching** while each ad platform matches it, and becomes **Ready** once you can use it in a campaign. See [Audience statuses](https://support.sayprimer.com/primer/audiences/audience-statuses.md) and [How long matching takes](https://support.sayprimer.com/primer/audiences/match-timing.md). From then on it keeps itself up to date — see [Dynamic audiences](https://support.sayprimer.com/primer/audiences/dynamic-audiences.md).

## Building an audience beside Chat

With [Chat](https://support.sayprimer.com/primer/chat/using-chat.md) turned on, an audience opens in a panel beside your chat rather than on its own page. The panel shows the size and match size estimates, a **Destinations** card and a **Filter Criteria** card, and the same **Summary**, **Preview**, **History** and **Validation** tabs. The run button reads **Save** instead of **Apply & Run**; the steps before the run are the same. See [Audiences in Chat](https://support.sayprimer.com/primer/chat/audiences-in-chat.md) for building and changing an audience by describing it.


---

# 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://support.sayprimer.com/primer/audiences/building-an-audience.md?ask=<question>&goal=<user_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.
