> 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-troubleshooting/audience-wont-sync.md).

# An audience won't sync

Why an audience can't run or sync to a destination, and how to apply changes or re-add it.

## It's below the destination's minimum

The most common reason a run is blocked is that the audience is too small for a destination. Primer shows: *"Recommended audience size for {destination} is >{n} records. Adjust your filters."*

Widen your filters until the estimate clears every destination's minimum — see [Audience size limits](https://support.sayprimer.com/primer/primer-support-review/section-audiences/audience-size-limits.md). Matching drops records, so build with headroom above the minimum.

## Changes haven't been applied

If you change an audience's filters after it has run, Primer shows *"Latest changes have not been applied and will not sync with your next run."* Click **Apply** (or **Rerun** on an [Incomplete](https://support.sayprimer.com/primer/primer-support-review/section-audiences/audience-statuses.md#incomplete) audience) to rebuild it with the change.

If you add a destination, Primer shows *"You have new destinations in your audience."* Click **Rerun** to sync the audience to the new platform.

## The audience disappeared from the ad platform

If an audience was removed on the ad platform's side, Primer shows *"This audience no longer exists in the ad destination(s)."* Click **Rerun** to add it again.

## A connection error or "Sync halted" message

If the audience shows a **Connection error** banner, the destination's connection needs fixing — see [Fixing a broken connection](https://support.sayprimer.com/primer/primer-support-review/section-troubleshooting/fixing-a-connection.md) — then run the audience again. A message starting *"Sync halted:"* is the ad platform's reason for refusing the sync; see [A sync halted with an error](https://support.sayprimer.com/primer/primer-support-review/section-troubleshooting/sync-halted.md).

## Still stuck

If the audience reaches [Ready](https://support.sayprimer.com/primer/primer-support-review/section-audiences/audience-statuses.md#ready) but a destination still shows no delivery well past the expected [matching time](https://support.sayprimer.com/primer/primer-support-review/section-audiences/match-timing.md), or it lands in [Incomplete](https://support.sayprimer.com/primer/primer-support-review/section-audiences/audience-statuses.md#incomplete), check the destination connection and then contact <support@sayprimer.com>.


---

# 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-troubleshooting/audience-wont-sync.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.
