> 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 delivered — and restore an earlier one.

Every time you confirm a change to an audience's filters, Primer keeps the previous version. Open the **History** tab on the audience, or **History Log** from the audience's menu on the **Audiences** page, to see how the audience has evolved.

## What each entry shows

The log is ordered newest first. Each version has:

* A **Criteria** row — the filters, the summary entered when the change was confirmed, who confirmed it and when.
* A **Matched Size** row — what that version's latest run matched at each destination, compared with the version before it. Expand it to see the match history.

Comparing versions shows the effect of a filter change — for example, whether widening a filter raised the matched count. See [Match rates](https://support.sayprimer.com/primer/audiences/match-rates.md) for what those numbers mean.

## Restoring an earlier version

Click **Restore** on a version to bring its filters back. Restoring replaces the audience's current filters with that version's; run the audience again to sync the restored version to your destinations.


---

# 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=<question>&goal=<user_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.
