> 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-connections/integrations/connecting-a-destination/dv360.md). # DV360 Sync an audience to Display & Video 360 — requires the Scale plan. Display & Video 360 (DV360) is generally available but **requires the Scale plan**. If you're on a lower plan, DV360 won't be selectable as a destination — contact to upgrade. * **Minimum audience size:** 1,000 records. * **Typical match rate:** 40–80%. * **Time to fully match:** up to 72 hours. DV360 also serves YouTube inventory; YouTube match rates typically run 20–45%. See Match rates. ## A direct destination, not shared from Google Ads DV360 is a **standalone** destination. Primer syncs the audience straight to your Display & Video 360 account over the DV360 API — it is **not** shared from Google Ads through account linking. Connect DV360 in its own right; a Google Ads connection doesn't make DV360 audiences appear, and vice versa. The synced list shows up under **My audiences** in DV360; see Finding your synced audience. --- # 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-connections/integrations/connecting-a-destination/dv360.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.