> 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/connections/integrations/connecting-a-destination/meta-ads.md).

# Meta Ads

Sync an audience to Meta (Facebook and Instagram) as a Custom Audience — and accepting Meta's Custom Audiences terms.

Meta Ads is generally available. Connect your Meta account, then sync a [Ready](https://support.sayprimer.com/primer/audiences/audience-statuses.md#ready) audience to it. Primer syncs it as a **Custom Audience**, which serves across Facebook and Instagram. Meta also needs a minimum number of *matched* records before it delivers — see [Audience size limits](https://support.sayprimer.com/primer/audiences/audience-size-limits.md#minimum-size-per-destination).

## "Terms not accepted" when connecting

Meta requires you to accept its **Custom Audiences terms** per ad account before Primer can push a list to it. When you pick an ad account that hasn't accepted them, Primer shows *"Terms not accepted — Accept Facebook Custom Audiences Terms to continue for this ad account"* with an **Accept on Facebook** button. Accept the terms in Meta for that account, then click **Re-check** in Primer. Accepting on one ad account doesn't cover another.

## Sync errors

Meta's own refusals — missing permissions, an ad account outside a business, the 500 Custom Audience cap, integrity restrictions — are covered in [A sync halted with an error](https://support.sayprimer.com/primer/troubleshooting/sync-halted.md).


---

# 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/connections/integrations/connecting-a-destination/meta-ads.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.
