> 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-history.md). # Audience history See past versions of an audience — who changed it, when, and what each version estimated and delivered. Every time you confirm a change to an audience's filters or destinations, Primer keeps the previous version. The history log lets you see how an audience has evolved over time. ## What each entry shows Each version in the log records: * **Who** confirmed it (name and profile image) and **when**. * The **filters** (the audience's shape) and the **destinations** it was set to sync to. * The **estimated** people and company counts, and predicted match rate, at that version. * The results of that version's most recent build — the **matched** people and company counts and achieved match rate, once it has run. ## Reading the log The log is ordered newest first. Comparing an older version's estimate and delivered counts to a newer one shows the effect of a filter change — for example, whether widening a filter raised the matched count. For what those estimate-vs-delivered numbers mean, see [Match rates](/primer/audiences/match-rates.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/audience-history.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.