> 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/audience-validation.md). # Audience validation Run a quality check on an audience before you launch it, and apply suggested fixes. > **Beta** — opened on request. Contact to request access. Audience validation checks an audience's quality before you launch it. It runs automatically as a precursor to the audience sync. ## What it checks Validation runs a set of rules over the audience and flags the ones that don't pass. The checks fall into a few groups: * **Filter completeness** — job title or department is set, revenue or headcount is set, and filters like job title, keywords or industry have enough entries to be meaningful. * **Destination fit** — the audience clears each destination's [minimum](/primer/primer-support-review/section-audiences/audience-size-limits.md), isn't too small, and is a reasonable fit for the destination. * **ICP fit** — how much of the audience falls inside your ICP. * **Overlaps** — overlap with your other audiences, exclusion lists, customers, competitors and open opportunities. Each check comes back as a warning or an informational note, with an explanation of why it matters. Validation is a set of pass/fail checks, not a single quality score. ## Applying fixes For issues that can be fixed automatically, **Suggest fixes** proposes a change to the audience's filters. Review the suggestion and accept it to apply the change to the audience shape, then rerun. You stay in control — nothing is changed until you accept 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 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/audience-validation.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.