> 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-review/section-audiences/finding-your-synced-audience.md).

# Finding your synced audience

Where an audience you synced from Primer shows up inside each ad platform.

Once an audience is [Live](/primer/primer-support-review/section-audiences/audience-statuses.md), Primer has pushed it to the ad platform as a **customer list / custom audience**. It appears in that platform's own audience library, under the name it has in Primer. Use it in a campaign the same way you'd use any list you built there directly.

> The exact menu names below are the ad platforms' own and can change — these are the areas to look in, not Primer screens.

## It's Live in Primer but I don't see it yet

**Live** in Primer means Primer has pushed the list to the platform — the platform then takes its own time to build and match it before it appears and shows a size. That lag is normal and varies by destination (Microsoft, for instance, can take up to 48 hours). If the list still hasn't appeared well past the destination's [matching time](/primer/primer-support-review/section-audiences/match-timing.md), check the [connection](/primer/primer-support-review/section-troubleshooting/fixing-a-connection.md) and then [why an audience won't sync](/primer/primer-support-review/section-troubleshooting/audience-wont-sync.md). To push a filter change you made *after* syncing, use **Rerun** — until you do, the platform keeps the previously built version.

## Google Ads

Open **Tools → Shared library → Audience manager → Your data segments**. The list appears as a **Customer list**. Newly synced lists show a processing state until Google finishes building them; see Google Ads for eligibility to serve.

## Meta Ads

Open **Audiences** in Ads Manager (or Meta Business Suite). The list appears as a **Custom Audience** with source *Customer list*. See Meta Ads for the matched-size minimum before it can deliver.

## LinkedIn Ads

In Campaign Manager, open **Plan → Audiences** (or the **Matched audiences** section when building a campaign). The list appears as a **List upload** audience.

## Reddit Ads

In the Reddit Ads dashboard, open **Audiences**. The list appears as a **Customer list** custom audience.

## DV360

In Display & Video 360, open **Resources → Audiences → My audiences**. The list appears as a first-party **Customer Match** audience on the partner/advertiser Primer synced to. See DV360 — it's a direct destination, not shared from Google Ads.

## Microsoft Ads

In Microsoft Advertising, open **Tools → Audiences**. The list appears as a **Customer List** audience. You must accept Microsoft's Customer List terms before it will build — see Microsoft Ads.


---

# 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-review/section-audiences/finding-your-synced-audience.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.