Skip to main content
DV360

​
DV360

Display & Video 360 is Google’s enterprise demand-side platform for programmatic advertising across display, video, and audio.

Setup

Troubleshooting

​
Overview

Display & Video 360 (DV360) is Google’s enterprise demand-side platform for buying and optimizing programmatic media across display, video, audio and more. Our integration with DV360 enables server-side identity-based activation, allowing you to target your Permutive cohorts in DV360 campaigns. This integration is a Destination only:
  • Destination: Permutive sends cohort memberships server-to-server to DV360 via the Audience Partner API, creating and updating user lists based on Google cookie matching.
The standard integration uses cookie-based identity matching (Google cookie collected on Web), which limits live activation to Web. Extending the integration to support iOS (mobile advertising IDs), Android (mobile advertising IDs), and CTV (IP or hashed email) can be an alternative path — contact your Permutive Customer Success Manager to discuss your use case.
Use cases include:
  • Send Permutive cohorts to DV360 for activation across display campaigns
  • Keep DV360 audience lists in sync with live cohort membership changes
  • Report on targeted impressions usage in DV360 for auditing and billing
  • Optimize display campaigns using high-quality first-party cohorts

​
Environment Compatibility

The DV360 integration currently uses cookie-based identity matching (Web only). Extending it to iOS, Android, and CTV via alternative identity types is something Permutive can support, though it requires additional build work — contact your Permutive Customer Success Manager to discuss your use case.

​
Prerequisites

  • Permutive Web SDK: Must be deployed on your site to collect the Google cookie required for DV360 matching. This integration relies on cookie-based matching using identifiers collected on web.
  • DV360 account details: You will need the following information from your DV360 account:
    • Entity ID: Your DV360 Entity ID (also called Partner ID or Advertiser ID depending on your setup)
    • Product Type: Either Invite_partner or Invite_advertiser depending on your DV360 account structure
  • Seat mapping (DV360): Your DV360 seat must be linked to Permutive’s partner account before audiences can sync. You can activate this link directly in DV360 by navigating to Partner Settings → Linked Account → Link new account and searching for Permutive.
    This mapping step is critical and must be completed before cohorts can be activated. Without this mapping, audience lists will not populate in your DV360 account.
  • Permissions: You must have appropriate permissions in your DV360 account to view and manage audience lists (First & Third Party Audiences).
  • Consent: Ensure your consent configuration allows collection of Google cookies and activation of data to DV360 in applicable regions (e.g., GDPR, CCPA). If using a Consent Management Platform (CMP) with IAB’s Transparency and Consent Framework (TCF), ensure users have granted consent for Google Advertising Products (vendor ID 755). Without consent, the cookie sync will not execute and users cannot be matched.

​
Setup

1

Link your DV360 account to Permutive

Before configuring the integration in Permutive, link your DV360 seat to Permutive’s partner account:
  1. Log in to your DV360 account
  2. Navigate to Partner Settings → Linked Account
  3. Click Link new account
  4. Search for Permutive and complete the linking process

This mapping must be completed first. Without it, audience lists will not appear or populate in your DV360 account even after setup is complete.

2

Enable in Permutive Dashboard

In the Permutive Dashboard, navigate to your workspace’s integrations page. Click Add Integration and select DV360.
3

Provide DV360 account details

Enter the following details from your DV360 account:
  • Entity ID: Your DV360 Entity ID (Partner ID or Advertiser ID)
  • Product Type: Select either Invite_partner or Invite_advertiser based on your DV360 account structure

If you’re unsure which Product Type to use, check with your Google account team or your DV360 administrator.

4

Verify Web SDK and cookie collection

Confirm that the Permutive Web SDK is deployed on your site(s) and collecting data. Verify that your consent configuration allows collection of Google cookies in regions where you plan to activate.
5

Test activation

Activate a small test cohort to DV360:
  1. Navigate to your cohorts in the Permutive Dashboard
  2. Select a test cohort and choose DV360 as the activation destination
  3. Wait a few minutes for processing
  4. Check your DV360 account under Audiences → First & Third Party Audiences to confirm the audience list appears
  5. Monitor the list size over the next 24 hours to ensure it populates correctly

Audience lists may take several hours to fully populate in DV360. Initial match rates depend on your site traffic volume and consent rates.

​
Data Types

This integration exports data from Permutive to DV360.
Permutive sends cohort membership updates server-to-server to DV360 via the Audience Partner API to create and update user lists (First & Third Party Audiences) for targeting in your DV360 campaigns.
​
string
The unique ID of the cohort in Permutive that is being activated.
​
string
The human-readable name of the cohort as it appears in the Permutive Dashboard. This name will be used to identify the audience list in DV360.
​
string
The type of identifier used for matching in DV360. For this integration, the identifier type is based on Google cookies collected via the Permutive Web SDK.
​
string
The hashed identifier value (Google cookie) used to match users into DV360 audience lists.
​
string
Indicates whether the user should be added to or removed from the DV360 audience list based on cohort membership changes. Values: add or remove
​
datetime
The time when the cohort membership update was processed by Permutive.
Data Refresh Frequency: Audience lists in DV360 are updated periodically as users enter or exit cohorts in Permutive. Updates are typically processed within minutes to hours, though DV360’s own list processing may add additional latency.

​
Troubleshooting

Cause: Audiences created via the Audience Partner API (cookie-based) are classified as Third-Party data and cannot be used for YouTube & partners line items in DV360.Why: YouTube targeting requires audiences that can be matched to signed-in Google users. Cookie-based audiences from this integration cannot meet this requirement.Alternative solutions for YouTube targeting:
  1. Customer Match: Upload hashed email addresses or phone numbers from your CRM directly to DV360
  2. GAM Segments: Use Google Ad Manager (GAM) segments if you have GAM 360 integration
  3. Floodlight Audiences: Create audiences based on website activity using Floodlight tags
  4. Optimized Targeting: Use an eligible first-party list as a seed and let Google’s machine learning expand the audience
Display inventory targeting via DV360 is fully supported with this integration. Only YouTube & partners line items have this limitation.
Most Common Cause: Seat mapping has not been completed.Steps to resolve:
  1. Confirm that your DV360 account is linked to Permutive:
    • In DV360, go to Partner Settings → Linked Account
    • Verify that Permutive appears in your linked accounts
    • If not linked, click Link new account and search for Permutive
  2. Verify the integration is enabled in the Permutive Dashboard under Integrations
  3. Check that the correct Entity ID and Product Type are configured in the Permutive Dashboard
  4. Ensure you have permissions to view First & Third Party Audiences in your DV360 account
If the issue persists after confirming the above, contact Permutive Support with your workspace ID and cohort details.
Cause: This integration relies on Google cookies collected via the Permutive Web SDK on web environments.Steps to diagnose and improve:
  1. Verify the Permutive Web SDK is properly deployed on your site(s)
  2. Check that your consent configuration allows collection of Google cookies in the regions where users are located
  3. Confirm recent site traffic volume is sufficient for meaningful cohort sizes
  4. Review cohort rules to ensure they’re not too restrictive
  5. Check cookie consent rates - low consent rates will reduce match rates
  6. Allow 24-48 hours after initial activation for the audience to fully populate
Expected match rates: Typically 60-80% of cookied web traffic, but this varies significantly based on consent rates, browser mix, and user behavior.
Steps to resolve:
  1. Allow 2-4 hours for DV360 to process the audience list after initial activation
  2. Verify your DV360 account is still linked to Permutive:
    • In DV360, go to Partner Settings → Linked Account
    • Confirm Permutive appears as a linked account
  3. Check that you’re viewing the correct DV360 account (Partner vs. Advertiser level)
  4. Confirm the cohort has sufficient active members in Permutive
  5. Check that the Web SDK is collecting data and that users are entering the cohort
If the list size remains at zero after 24 hours, verify the account linking and check Permutive logs for activation errors.
Common causes:
  • Incorrect Entity ID or Product Type configuration
  • Expired or invalid API credentials (managed by Permutive)
  • DV360 API rate limiting during high-volume activations
Steps to resolve:
  1. Verify your Entity ID and Product Type are correct in the Permutive Dashboard
  2. Check that your DV360 account is active and accessible
  3. If activating many cohorts simultaneously, try spacing out activations
  4. Contact Permutive Support if API errors persist, providing your workspace ID and error timestamp
You can set up automated monthly reports in DV360 to track targeted impressions for billing purposes.Steps:
  1. Navigate to the Offline Reporting tab in DV360
  2. Set the desired date range (typically monthly)
  3. Select the following Dimensions:
    • Advertiser
    • Audience List
    • Cost
    • ID
    • Type
  4. Select the following Metrics:
    • Billable Impressions (impressions that reach a specific audience)
  5. Schedule the report to be sent to ti_usage@permutive.com on the 1st of every month
  6. Optionally, save the report to a Google Drive folder for your own records

​
Changelog

No changes listed yet. For detailed changelog information, visit our Changelog.