> 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/locate-audience-in-ad-destinations.md).
# Locate Audience in Ad Destinations
You can locate your Primer audience in Google Ads, LinkedIn Ads, Meta Ads, and Reddit Ads using the methods below.
#### Method 1: Match Rate Estimates
As highlighted in the image below, you can directly access your audience from the Match Rate Estimates section.
**Steps:**
* Open your audience in Primer.
* In the Match Rate Estimates section, click the relevant destination icon\
(Google, LinkedIn, Meta, or Reddit).
* You will be redirected to the corresponding Ad Manager, where the audience is available.
***
#### Method 2: History Log
As highlighted in the image below, you can also locate your audience from the History Log.
**Steps:**
* Open History Log on the audience page.
* Under Matched Size, hover on the destination icon\
(Google, LinkedIn, Meta, or Reddit).
* Select **Open in ads manager** to view the 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/build-and-manage-audiences/managing-audiences/locate-audience-in-ad-destinations.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.
