Skip to main content

Google Display & Video 360

Overview

The Display & Video 360 (DV360) connector exports DMP audiences directly to DV360 as first-party Customer Match audiences, making them available for targeting in your DV360 line items.

Each audience selected for export is uploaded as a separate first-party audience. Members are sent through Google's Data Manager API in batches; large audiences are streamed without ever being held in memory by Decentriq.

Google's APIs do not support clearing an audience, so the connector is append-only: on each run, members are added to the matching audience, and members who are no longer in the audience age out automatically once they reach the membership duration you configure. To produce a clean snapshot per run instead, use a date-tokenized name suffix (see Step 4).

Prerequisites

Setting up the connector requires steps in Google Cloud and in Display & Video 360 before you configure the export in Decentriq. A single service account can be reused for several advertisers (and shared with the Google Ads connector).

In Google Cloud

  1. Open or create a Google Cloud project (console.cloud.google.com).
  2. Enable both the Data Manager API and the Display & Video 360 API (APIs & Services → Library).
  3. Create a service account (IAM & Admin → Service accounts). No project roles are required.
  4. On that service account, create a JSON key (Keys → Add key → Create new key → JSON) and download it. This JSON file is the credential you will paste into Decentriq. Note the service account's email (for example dmp-export@my-project.iam.gserviceaccount.com).

In Display & Video 360

  1. Note the Advertiser ID of the DV360 advertiser that will receive the audiences (shown in the advertiser's settings / in the URL when the advertiser is selected).

  2. Have a DV360 administrator add the service account as a user with access to that advertiser, using a role that permits managing audiences (for example Standard). DV360 users are managed at the partner level under Settings → Users. Access can take a few minutes to propagate.

    note

    Unlike Google Ads, DV360 does not use a manager/login account or a developer token — the service account is granted access to the advertiser directly, and the advertiser ID is the only account identifier you need.

  3. The advertiser must be eligible for Customer Match. Eligibility depends on the account's standing and policy compliance (see Google's Customer Match policy). Audiences will only become usable for targeting once the advertiser is eligible.

You must have obtained the user consent required for Customer Match for the data you upload — you confirm this when configuring the export.

The service-account credentials are encrypted and stored securely by Decentriq.

Step-by-step guide

Step 1: Select the destination

Follow the steps to create a new export and select Google Display & Video 360 from the list of connectors.

Step 2: Configure connection

Click Continue to proceed to connection configuration. Enter the required connection details:

  • Advertiser ID: Your DV360 advertiser ID.
  • Service account credentials: Paste the full contents of the service-account JSON key created in Google Cloud.

Step 3: Select audiences

Click Continue to proceed to audience selection. Select the identifier to use for matching:

  • Email (SHA256 hashed)

Emails must be pre-hashed with SHA256 by the publisher before they reach the DMP — the connector does not hash on your behalf.

Then choose the audiences to export. Multiple audiences can be selected; each will be uploaded as its own DV360 first-party audience.

Step 4: Configure the export

Click Continue to proceed to export configuration:

  • Export name: The name of this export configuration in the DMP.
  • DV360 audience names: A preview of the names the exported audiences will have in DV360, derived from each audience's name in the DMP. On each run, the connector finds the existing audience by name and appends new members to it (it does not overwrite). To create a fresh audience per run instead, set a suffix below.
  • Audience name suffix: An optional suffix appended to each audience name. Supports the date tokens {yyyy}, {mm}, {dd}, and {q}, which are replaced with the export date (for example, " - {yyyy}-{mm}-{dd}" becomes - 2026-05-04).
  • Description: An optional description applied to the audiences created in DV360.
  • Membership duration: How long (in days, 1–10000) a member remains in the audience before expiring. Because the connector is append-only, this is how members who have left the audience age out.
  • Consent: Confirm that you have obtained the user consent required for Customer Match (ad user data and ad personalization). This is required — the export cannot be saved without it.
  • Schedule settings: Define how often the export should run (run once, daily, weekly, or monthly).

Step 5: Create the export

Click Continue to create the export. Once created, the export appears in the Exports table with the export name provided in the previous step. From there, you can monitor its status, review execution history, and manage future runs.

After the first run

The audience appears in DV360 under the advertiser's audiences as soon as the first run completes. Google then processes the uploaded members before the audience becomes usable, which can take several hours, so the reported size may not reflect the upload immediately. As with Customer Match generally, small audiences may not report a size, and membership only populates for advertisers that are eligible for Customer Match.