> 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-legacy/build-and-manage-audiences/managing-audiences/matched-audience-size.md).
# Matched Audience Size
Primer allows you to check the match rates of your audiences across Google, Meta, and LinkedIn—without needing to log into each platform. Follow the steps below to view your matched audience size directly within Primer.
**"Size" vs. "Matched Size":** The Size shown on your audience list or in the audience builder is your audience's total estimated size — the number of people or companies matching your filter criteria, calculated at build time. This updates as you add or remove filters. Matched Size is different: it only appears after a sync completes (via History Log, as described below), and shows how many of those records were actually matched on Google, Meta, LinkedIn, or Reddit.
#### **Steps to Check Your Audience Match Rates:**
* **Navigate to Your Audience:**
* Go to the **Audience** you want to check.
* **Click "View Runs":**
* In the top-right corner of the audience page, you’ll see a button labeled **History Log**. Click on it.
* **View Matched Audience Size:**
* After clicking **History Log**, you’ll see a detailed breakdown of your audience syncs. The **Matched Size** section will display how many users were matched across Google, Meta, LinkedIn and Reddit.
**Note:**\
Match rates may vary by platform, and syncing times differ.
It takes up to 72 hours for Google, LinkedIn and Reddit to fully match. Meta matches within 12 hours.
For more detailed information about match rates and how the audience size affects your campaigns, check out our Match Rate vs. Reach Rate Page.
---
# 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-legacy/build-and-manage-audiences/managing-audiences/matched-audience-size.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.
