> 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/audiences/audience-size-limits.md).

# Audience size limits

The maximum and minimum audience sizes Primer enforces, and how to split an audience that's too large.

## Maximum size

A regular audience is capped at **3,000,000 records**. If your filters estimate more than that, Primer cuts the audience off at the maximum and shows a message on the estimate.

[Exclusion audiences](/primer/audiences/exclusion-audiences.md) have a much higher cap of **50,000,000 records**, because they're used to remove people from targeting rather than to target them.

## Minimum size per destination

Each ad destination needs a minimum estimated audience size before you can sync to it. If your audience is below the minimum, Primer shows: *"Recommended audience size for {destination} is >{n} records. Adjust your filters."*

| Destination | Minimum audience size |
| ----------- | --------------------- |
| Google      | 100                   |
| Meta        | 100                   |
| LinkedIn    | 300                   |
| Reddit      | 1,000                 |
| DV360       | 1,000                 |
| Microsoft   | 300                   |

Matching drops records the platform can't identify, so the delivered audience is smaller than your estimate. A few destinations also enforce a minimum on the **matched** count — Meta needs at least 1,500 matched records to deliver. Aim comfortably above the minimum so you clear it after matching. See [Match rates](/primer/audiences/match-rates.md) for how much shrinkage to expect.

## How many audiences you can have active

Separate from how *big* an audience can be, your plan limits how *many* audiences you can have active at once — see [Active audience slots](/primer/settings/your-plan.md#active-audience-slots).


---

# 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/audiences/audience-size-limits.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.