> 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.md).

# Connecting a destination

The ad platforms Primer syncs audiences to, which are generally available, plan-gated or in beta, and how connecting one works.

Once an audience is [Ready](https://support.sayprimer.com/primer/audiences/audience-statuses.md#ready), you sync it to an ad destination — an ad platform where your campaigns run. Primer matches the audience against that platform and makes the matched records available to target.

## Available destinations

| Destination                                                                                                              | Availability                                      |
| ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------- |
| [Google Ads](https://support.sayprimer.com/primer/connections/integrations/connecting-a-destination/google-ads.md)       | Generally available                               |
| [Meta Ads](https://support.sayprimer.com/primer/connections/integrations/connecting-a-destination/meta-ads.md)           | Generally available                               |
| [LinkedIn Ads](https://support.sayprimer.com/primer/connections/integrations/connecting-a-destination/linkedin-ads.md)   | Generally available                               |
| [Reddit Ads](https://support.sayprimer.com/primer/connections/integrations/connecting-a-destination/reddit-ads.md)       | Generally available                               |
| [DV360](https://support.sayprimer.com/primer/connections/integrations/connecting-a-destination/dv360.md)                 | Generally available — requires the **Scale** plan |
| [Microsoft Ads](https://support.sayprimer.com/primer/connections/integrations/connecting-a-destination/microsoft-ads.md) | Generally available                               |
| [TikTok Ads](https://support.sayprimer.com/primer/connections/integrations/connecting-a-destination/tiktok-ads.md)       | **Beta** — request access                         |
| [X Ads](https://support.sayprimer.com/primer/connections/integrations/connecting-a-destination/x-ads.md)                 | **Beta** — request access                         |

## Getting access to a beta destination

A beta destination carries a **Beta** badge on the **Connections** page. Click it to open **Join the Beta Program**, then click **Request Access**; the card shows **Joined Beta** while support follows up. If you don't see the card, use **Request** on the Connections page or contact <support@sayprimer.com>. Once a beta is enabled for your organization, you connect it like any other destination.

## Choosing which ad account to sync to

When you authorize a platform, Primer lists the ad accounts your login can reach and you pick one, then click **Continue**. If you run more than one ad account on a platform, pick the one your campaigns actually use. Google manager accounts work differently — see [Google Ads](https://support.sayprimer.com/primer/connections/integrations/connecting-a-destination/google-ads.md#manager-mcc-accounts).

## One connection per platform

Each organization connects **one account per platform**. Once a platform is connected, its **Connect** button is disabled (*"Account is Connected"*), so you can't add a second account to the same platform. To switch accounts, disconnect the current one first, then connect the new one.

A plan belongs to a single organization, so if you need to run a **second** account on the same platform in parallel, set it up under a **separate Primer organization** with its own plan.

## Disconnecting a destination

On the **Connections** page, click **Remove account** (✕) on the connection's row and confirm with **Yes, disconnect**. Primer won't remove a connection that running audiences are using — it shows **Removing Not Allowed** — so wait for those audiences to finish, then try again.

## Before you sync

Each destination has its own minimum audience size, typical match rate and matching time. Check [Audience size limits](https://support.sayprimer.com/primer/audiences/audience-size-limits.md), [Match rates](https://support.sayprimer.com/primer/audiences/match-rates.md) and [How long matching takes](https://support.sayprimer.com/primer/audiences/match-timing.md) so you know what to expect after you sync.

## Platforms that aren't listed

If the platform you want isn't in the table above — Pinterest, Amazon Ads or Rollworks, for example — it isn't a Primer destination. Tell us you need it through **Request** on the **Connections** page (it also takes a free-text **Other** entry), or email <support@sayprimer.com>, so we can weigh the demand.


---

# 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.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.
