> 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/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 The selected ad platform is matching the people in the audience against its members. See [How long matching takes](/primer/audiences/match-timing.md). ## Ready The audience is synced to at least one destination and available for your campaigns. ## Live The audience has been used in at least 1 live campaign in the last 24hrs. ## 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. ## Archived The audience has been archived and will be removed from the ad destination. --- # 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/audience-statuses.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.