> 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/audiences/audience-statuses.md). # Audience statuses What Draft, Running, Matching, Ready, Live, Incomplete and Archived mean, and what to do at each. Every audience shows a status that tells you where it is between being defined and delivering ads. These are the statuses you'll see. ## Draft The audience is still being defined and hasn't been built yet. You can keep editing its filters. Nothing is matched or synced while it's a draft. ## Running Primer is building the audience — resolving your filters into the actual set of people or companies. This runs after you confirm a draft, and again whenever you add a new destination. ## Matching Primer is matching the built audience against a destination so the ad platform can identify its members. See [How long matching takes](/primer/primer-support-review/audiences/match-timing.md). ## Ready The audience is built and matched and ready to sync to a destination. It isn't delivering ads yet — connect a destination to make it Live. ## Live The audience is synced to at least one destination and available for your campaigns. An audience becomes Live once a destination sync completes. ## Incomplete Something needs your attention before the audience can finish — most often a destination connection or setting that requires action on your side. Fix the flagged item and the audience returns to Running. (When the blocker is on Primer's side instead, the audience stays in Running while we work on it, so Incomplete means the ball is in your court.) ## Archived The audience has been archived and is hidden from the active list. Archiving doesn't delete 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://support.sayprimer.com/primer/primer-support-review/audiences/audience-statuses.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.