> 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/destinations/google-ads.md).

# Google Ads

Sync an audience to Google Ads — minimum size, match rate and matching time.

Google Ads is generally available. Connect your Google Ads account, then sync a [Ready](/primer/primer-support-review/audiences/audience-statuses.md#ready) audience to it.

* **Minimum audience size:** 100 records.
* **Typical match rate (Google Search):** 35–45%.
* **Time to fully match:** up to 72 hours.

## Customer Match eligibility

Primer syncs your audience to Google as a **Customer Match** list. Google applies its own policy before it will *serve* ads to that list, separate from Primer's minimum audience size:

* The list must hold at least **1,000 active members** in the last 30 days.
* Your Google Ads account must be **eligible for Customer Match** at all. Google grants this based on account history — a good policy-compliance record, more than 90 days in Google Ads, and more than $50,000 in total lifetime spend (a Google policy threshold, fenced Google-side, not enforced by Primer). New or low-spend accounts may not be whitelisted yet.

If a synced list won't serve, check both in Google Ads. Build with enough headroom to clear the 1,000-member floor after matching; see [Match rates](/primer/primer-support-review/audiences/match-rates.md) for expected shrinkage.

## Manager (MCC) accounts

If you manage Google Ads through a **Manager account (MCC)**, connect Primer to the specific **child (client) account** the campaigns run in — that's where the synced Customer Match list needs to land. Primer supports syncing under a manager account, but the audience is created on the client account you select, not on the MCC itself. Make sure the account you connect is the one your campaigns use, and that it's eligible for Customer Match as above.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.sayprimer.com/primer/primer-support-review/destinations/google-ads.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.