> 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 sync to match the audience and use it in a campaign.

An audience is a set of people or companies you want to target, defined by filters.

## Adding filters and destinations

Start by adding [filters](/primer/audiences/audience-filters.md) to define who's in the audience, and selecting the **destinations** — the ad platforms you want to sync it to. As you go, Primer shows estimates so you can see the shape of the audience before you commit to building it.

Filters and destinations sit in the left panel, the live estimates on the right, and **Sync** (labelled **Rerun** once the audience has been built) is in the top-right header:

![Audience builder: the left panel holds the filters and destinations cards, the right panel shows the size and match-rate estimates, and the Sync button is in the top-right header.](https://2005909474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyNQPXI6WokgTBADFvkpG%2Fuploads%2Fgit-blob-b15a9e8e398d4f5c1a683beecc561b342ec7ffd7%2Faudience-builder.png?alt=media)

## Reviewing the estimates

As you add filters and destinations, Primer shows estimates — **size**, **match rate**, **summary** and **preview** — so you can see the shape of the audience before you build it. See [Audience estimates](/primer/audiences/estimates.md) for what each one shows.

## Syncing and quality checks

When the audience looks right, hit **Sync**. Before it syncs, the audience goes through quality checks — see [Audience validation](/primer/audiences/audience-validation.md) for what's checked and how to apply suggested fixes.

## Matching and going live

After the checks, the audience lands in each destination and goes through **matching**, where the ad platform matches the people in it against its own members. See [How long matching takes](/primer/audiences/match-timing.md).

Once matched, the audience is available for your campaigns. Adding it to a live campaign is what makes it **Live**.

A new audience starts as a **Draft** and moves through **Running**, **Matching** and **Ready** as it builds and matches, then to **Live** once it's used in a campaign. See [Audience statuses](/primer/audiences/audience-statuses.md) for what each status means and what to do at each one.

From there the audience is **dynamic** — Primer re-checks your filters daily and updates who's in it. See [Dynamic audiences](/primer/audiences/dynamic-audiences.md).


---

# 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.