> 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/primer-support-review/section-audiences/dynamic-audiences.md). # Dynamic audiences Audiences are dynamic — once synced, Primer re-checks your filters daily and keeps membership current in your destinations. Audiences are **dynamic**, not one-time snapshots. Once one is built and synced to a destination, Primer keeps it current on its own — you don't re-sync it by hand. ## What updates, and when Primer re-checks a synced audience's filters against the latest data **daily** and updates who's in it: * **People and companies that now match are added.** * **Ones that no longer match are removed.** Those membership changes flow out to each connected destination, so the ad platforms stay in step with your filters without any action from you. ## What triggers a rebuild Beyond the daily check, an audience also rebuilds when something it depends on changes: * You **edit its filters or destinations** — it returns to **Running** while it rebuilds. * Primer's **database is refreshed** with new data. * A connected **CRM or CSV** you filter on is updated. Even when nothing has changed, Primer refreshes each audience periodically so it never goes stale. ## What doesn't update A **Draft** isn't matched or synced, so it doesn't update — nothing happens until you build it. See [Audience statuses](/primer/primer-support-review/section-audiences/audience-statuses.md) for what each state means. --- # 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/primer-support-review/section-audiences/dynamic-audiences.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.