> 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/troubleshooting-connections/google-troubleshooting/trouble-understanding-google-match-rate-vs.-audience-size.md).
# Trouble Understanding Google Match Rate vs. Audience Size
The match rate in Google indicates the percentage of the list that Primer sends that Google can match to an associated user they have information on. Since Primer provides a lot of personal emails, and Google has seen many of these emails before, match rates can sometimes be quite high.
However, it's important to note that the match rate only tells us how many users Google can identify, not how many users are available to be served an ad.
What really matters in Google is the actual matched audience size. You will see a significant difference between the stated Google match rate and the available audience sizes for Search, Youtube, Display, etc.
A similar situation occurs on LinkedIn. For example, LinkedIn might report a 90% match rate, but the actual audience size can vary. In some cases, the audience size may even exceed 100% because one email address might be associated with two different LinkedIn profiles.
This discrepancy occurs because the match rate measures identification, while audience size measures the number of users who can actually be targeted with ads.
When we show match rates inside of Primer, we use the actual matched size reported by the ad platform (in this case Google) divide by total number of people synced through to the destination.
```
Primer Match Rate = Audience size in google / # of people in Primer audience
```
---
# 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/troubleshooting-connections/google-troubleshooting/trouble-understanding-google-match-rate-vs.-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.
