> 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.md).

# Audiences

- [Building an audience](https://support.sayprimer.com/primer/audiences/building-an-audience.md): Add filters and destinations, review the estimates, then sync to match the audience and use it in a campaign.
- [Audience filters](https://support.sayprimer.com/primer/audiences/audience-filters.md): The filter sources you build an audience from — Primer data, events, CRM and datasets — with sample filters.
- [Audience estimates](https://support.sayprimer.com/primer/audiences/estimates.md): What the size, match rate, summary and preview estimates show as you build an audience.
- [Audience validation](https://support.sayprimer.com/primer/audiences/audience-validation.md): Run a quality check on an audience before you launch it, and apply suggested fixes.
- [Audience statuses](https://support.sayprimer.com/primer/audiences/audience-statuses.md): What Draft, Running, Matching, Ready, Live, Incomplete and Archived mean, and what to do at each.
- [Audience history](https://support.sayprimer.com/primer/audiences/audience-history.md): See past versions of an audience — who changed it, when, and what each version estimated and delivered.
- [Dynamic audiences](https://support.sayprimer.com/primer/audiences/dynamic-audiences.md): Audiences are dynamic — once synced, Primer re-checks your filters daily and keeps membership current in your destinations.
- [Audience size limits](https://support.sayprimer.com/primer/audiences/audience-size-limits.md): The maximum and minimum audience sizes Primer enforces, and how to split an audience that's too large.
- [Match rates](https://support.sayprimer.com/primer/audiences/match-rates.md): What a match rate is, the match rates Primer typically achieves per destination, and how it differs from audience size.
- [How long matching takes](https://support.sayprimer.com/primer/audiences/match-timing.md): How long each destination takes to fully match an audience after you sync it.
- [Finding your synced audience](https://support.sayprimer.com/primer/audiences/finding-your-synced-audience.md): Where an audience you synced from Primer shows up inside each ad platform.
- [Exclusion audiences](https://support.sayprimer.com/primer/audiences/exclusion-audiences.md): Use an exclusion (anti-ICP) audience to remove people from targeting, with a 50M cap.
- [Duplicating and archiving audiences](https://support.sayprimer.com/primer/audiences/duplicating-and-archiving.md): Copy an audience to iterate on it, or archive one to hide it from your active list.
- [Conversion metrics](https://support.sayprimer.com/primer/audiences/conversion-metrics.md): Tie website visits and form fills back to your audiences, with cost and lift metrics.
- [Conversion lift](https://support.sayprimer.com/primer/audiences/conversion-lift.md): What lift measures on a conversion report — conversions among people exposed to your ads vs. those not exposed, and when it's significant.


---

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