> 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/dynamic-audiences.md).

# Dynamic audiences

Once an audience has synced, Primer rebuilds it when the data behind it changes, so your destinations stay current without a manual re-sync.

Audiences are **dynamic**, not one-time snapshots. Once one has been run and synced to a destination, Primer keeps it current on its own — you don't re-sync it by hand. Each rebuild adds the people who now match your filters and removes the ones who no longer do, and those changes flow out to each destination.

## When an audience rebuilds by itself

Primer checks synced audiences every day and rebuilds the ones whose data has changed:

* Primer's **database is refreshed** with new data.
* A **CSV dataset** the audience filters on is updated.
* A connected **CRM** the audience filters on has new data. CRMs sync every day, so Primer picks up CRM changes on a later rebuild rather than the next day.
* A destination whose connection broke has been **reconnected**.

An audience that none of these affect is still rebuilt periodically, so it never goes stale.

## When you change an audience

Applying a filter change or adding a destination rebuilds the audience straight away — it returns to **Running** while it does. See [Building an audience](https://support.sayprimer.com/primer/audiences/building-an-audience.md#changing-an-audience-after-it-has-run).

## What doesn't update

A **Draft** isn't built or synced, so nothing updates until you run it, and an **Archived** audience is no longer synced. An audience with no destinations or no filters isn't refreshed either. See [Audience statuses](https://support.sayprimer.com/primer/audiences/audience-statuses.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/dynamic-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.
