> 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 to, and which are generally available, plan-gated, or in beta. Once an audience is [Ready](/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](/primer/connections/integrations/connecting-a-destination/google-ads.md) | Generally available | | [Meta Ads](/primer/connections/integrations/connecting-a-destination/meta-ads.md) | Generally available | | [LinkedIn Ads](/primer/connections/integrations/connecting-a-destination/linkedin-ads.md) | Generally available | | [Reddit Ads](/primer/connections/integrations/connecting-a-destination/reddit-ads.md) | Generally available | | [DV360](/primer/connections/integrations/connecting-a-destination/dv360.md) | Generally available — requires the **Scale** plan | | [Microsoft Ads](/primer/connections/integrations/connecting-a-destination/microsoft-ads.md) | **Beta** — request access | | [TikTok Ads](/primer/connections/integrations/connecting-a-destination/tiktok-ads.md) | **Beta** — request access | | [X Ads](/primer/connections/integrations/connecting-a-destination/x-ads.md) | **Beta** — request access | The three **Beta** destinations open on request — connecting one prompts you to request access, and once it's enabled for your account you authorize it like any other. Don't see your platform? See [Platforms that aren't listed](#platforms-that-arent-listed). ## Choosing which ad account to sync to When you authorize a platform, Primer lists the ad accounts your login can reach and you pick which one to sync to — so if you run more than one ad account on a platform, connect the one your campaigns actually use. For Google, a **Manager account (MCC)** is marked with an **MCC** badge and you select the **child (client) account** underneath it, not the manager — see [Google Ads](/primer/connections/integrations/connecting-a-destination/google-ads.md#manager-mcc-accounts). ## One connection per platform Each organization connects **one account per platform** — one Google Ads, one Meta, one Reddit, and so on. Once a platform is connected, its **Connect** button is replaced by the connected account and a **Disconnect** option, so there's no way to add a second account to the same platform. To switch to a different account, 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. ## Before you sync Each destination has a minimum audience size and a matching time. Check [Audience size limits](/primer/audiences/audience-size-limits.md), [Match rates](/primer/audiences/match-rates.md) and [How long matching takes](/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, one of three things is true. **It's a beta destination.** [Microsoft Ads](/primer/connections/integrations/connecting-a-destination/microsoft-ads.md), [TikTok Ads](/primer/connections/integrations/connecting-a-destination/tiktok-ads.md) and [X Ads](/primer/connections/integrations/connecting-a-destination/x-ads.md) are **beta** — they appear in the destination picker with a **Beta** badge, and connecting one prompts you to request access. Once it's enabled for your account you authorize it like any other destination. Contact to have one turned on. **It runs through a connection you already have.** Some platforms people ask for by name aren't separate connections — they're served by a destination Primer already supports: * **Bing / Microsoft Search** is [Microsoft Ads](/primer/connections/integrations/connecting-a-destination/microsoft-ads.md) (currently beta). * **YouTube** and **Gmail** are Google inventory: a list synced to [Google Ads](/primer/connections/integrations/connecting-a-destination/google-ads.md) as Customer Match can serve there, subject to Google's own placement rules (Google-side, not something Primer sets). **It isn't supported.** Pinterest, for example, is **not a Primer destination** — there's no self-serve Pinterest sync. If you need Pinterest or another platform that isn't listed, let know 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=&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.