Send data to DV360

Display & Video 360 (DV360) enables advertising on connected TVs (CTVs), such as Android TV and Chromecast, online video platforms, such as YouTube, along with providing access to a variety of third-party partner exchanges.

What is Google Customer Match?

Google Customer Match is a unified ad creation tool that you can use to create and publish search, display, and video ads across the Google-owned paid media ecosystem.

For example:

• Use Discovery campaigns to reach customers in the Promotions and Social tabs in Gmail.

• Use Google Ads to configure campaign types for search, display, video, app, local, hotel, call, smart, goal-based, and shopping.

• Run ads within search results on Google.com.

• Run ads within the Shopping tab on Google.com.

• Send audiences to DV360, and then run video advertising campaigns in YouTube Ads or on web pages using any of the available placement options. DV360 supports advertiser and partner networks.

Use Amperity to build high-value and/or product affinity segments that are based on first-party data, and then configure Amperity to use the Google Customer Match destination to send those segments to DV360.

Once uploaded, Google Customer Match hashes each record, and then matches all records against hashed user accounts that already exist in Google Customer Match to identify segments that contain records that match the ones sent from Amperity.

Google Customer Match builds audience lists that are reachable across the Google-owned paid media ecosystem.

Use these audience lists for precision cross-selling, to reach and convert new customers, and to improve the retention rate for your most loyal customers.

Note

This destination uses the Google Audience Partner API.

Changes to audiences are not immediately available in DV360. Allow for up to 48 hours after the point at which Amperity has finished sending audience updates for them to be available.

This topic describes the steps that are required to send customer profiles to DV360 from Amperity:

1. Get details

2. Add destination

3. Add data template

Get details

DV360 requires the following configuration details:

	Configuration details for DV360. The name of the product to which Amperity will send data: “Display Video Advertiser” or “Display Video Partner”. The customer ID associated with your Google Customer Match account, along with the customer ID associated with the “Display Video Advertiser” or “Display Video Partner” account. Note The customer ID must be 10 digits and may not contain dashes. A refresh token that is generated from the authentication process that authorizes Amperity to send data to the selected product. This must be a Google account with permission to access the configured customer ID and product within Google. Important Authentication for “Display Video Advertiser” and/or “Display Video Partner” must be completed within Google prior to configuring DV360 in Amperity.
	Amperity must be configured as a linked account in DV360 before audience lists can be sent from Amperity to partners or advertisers. In DV360, open Advertiser Settings, and then select Linked Accounts. Click Link New Account, and then select External Data Partner. Select “Amperity” from the drop-down menu, and then click Link. Confirm Amperity as a linked external data partner, and then click Create Link.
	The name of an audience in DV360. The description is optional. If the audience does not exist, Amperity will create it. The membership duration defines the length of time (in days) at which individual audience members will belong to the segment. The membership duration must be between 0-540 (inclusive) or 10000 for an unlimited duration. Tip Set this value to “0” to remove all audience members. The Upload key type must be set to one of Contact Info or Mobile ID. If the Upload key type is set to “Mobile ID”, use the Mobile app ID setting to provide the ID for the iOS or Android app from which the mobile ID was collected.
	Review the user consent policy for the European Union (EU) and European Economic Area (EEA), and then add the required columns to your orchestration or campaign.

Add destination

Configure Amperity to send customer profiles directly to DV360.

Warning

Amperity must be authorized to send data to your DV360 account prior to configuring the destination.

To add a destination

	Open the Destinations tab to configure a destination for DV360. Click the Add Destination button to open the Destination dialog box. Enter a name for the destination and provide a description. For example: “DV360” and “This sends customer profiles to DV360”. From the Plugin drop-down, start typing “google” to filter the list, and then select Google Customer Match.
	Credentials allow Amperity to connect to DV360. The credential type is set automatically. You may use an existing credential or you may add a new one. Select an existing credential from the Credential drop-down. – or – Select Create a new credential from the Credential drop-down. This opens the Credential dialog box. To create a new credential for DV360, generate an authorization link, and then use that link to log into your DV360 account. After you have completed that process, you will be provided a refresh token. Add the value for the refresh token to the Refresh Token setting in Amperity. Important Authentication for “Display Video Advertiser” and/or “Display Video Partner” must be completed within Google prior to configuring DV360 in Amperity. When finished, click Save.
	Each destination has settings that define how Amperity will deliver data to DV360. These settings are listed under the Settings section of the Destination dialog box. Choose “Display Video Advertiser” or “Display Video Partner”. What are advertisers? What are partners? Display & Video 360 Advertisers Display & Video 360 Advertisers represent individual businesses that run advertising campaigns. Use your Advertiser ID to identify the customer ID to which Amperity should send data. Display & Video 360 Partners Display & Video 360 Partners represent agencies, trading desks, and large individual advertisers. Multiple advertisers are often grouped under a single partner. Use your partner ID to identify the customer ID to which Amperity should send data. After choosing the type of advertising your brand will run on DV360, add your customer ID.
	Business users are assigned to the Amp360 User and/or AmpIQ User policies. (Amp360 User allows access to queries and orchestrations and AmpIQ User allows access to segments and campaigns.) A business user cannot select a destination that is not visible to them. Business users – including users assigned to the DataGrid Operator policy – may have restricted access to PII. What is restricted access to PII? Restricted PII access is enabled when the Restrict PII access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow. You can make this destination visible to orchestrations and allow users with restricted access to PII to use this destination by enabling one (or both) of the following options: Note To allow business users to use this destination with campaigns, you must enable the Available to campaigns option within the data template. This allows users to send campaign results from Amperity to DV360. The other two settings may be configured within the data template instead of the destination.
	Review all settings, and then click Save. Important You must configure a data template for this destination before you can send data to DV360.

Add data template

A data template defines how columns in Amperity data structures are sent to downstream workflows. A data template is part of the configuration for sending query and segment results from Amperity to an external location.

About paid media campaigns

Amperity provides the right set of data to support your brand’s paid media advertising with DV360.

1. Merged Customers vs. Unified Paid Media

   The Merged Customers table contains each of your customers’ best profiles.

   The Unified Paid Media table contains all your customer’s known profile data.

   Your brand will require additional data templates to use the Unified Paid Media table alongside the Merged Customers table to support paid media campaigns.

2. Enable dedicated data templates for each table.

   Use a consistent naming pattern to label data templates that use data from the Merged Customers table. For example: “Best profile”.

   Use a consistent naming pattern to label data templates that use data from the Unified Paid Media table. For example: “Full profile”.

3. After data templates are configured for both tables, use the default attributes component on the Campaigns page to configure which attributes will be associated with the destination, including the table from which those attributes will be pulled.

   The selected table will affect your brand’s downstream match rates and overall customer matches within your paid media campaigns. The decision behind which table to use depends on your brand’s downstream use case and the type and amount of customer profile data your brand wants to use to match customers.

   You brand should expect to see higher match rates when sending audiences from the Merged Customers table, but a higher number of matched customer profiles when sending audiences from the Unified Paid Media table. Use A/B testing to compare the results from each table, after which your brand can use the audience that works best for your campaigns.

To add a data template

	From the Destinations tab, open the menu for a destination that is configured for DV360, and then select Add data template. This opens the Add Data Template dialog box. Enter the name of the data template and a description. For example: “DV360” and “Send customer profiles to DV360.”.
	Verify business user access to queries and orchestrations and access to segments and campaigns. A business user may also have restricted access to PII, which prevents them from viewing and sending customer profile data. If business user access was not configured as part of the destination, you may configure access from the data template. Important To allow business users to use this destination with campaigns, you must enable the Available to campaigns option. This allows users to send campaign results from Amperity to DV360. If you enable this option, the data extension settings require using campaign name and group name template variables to associate the name of the data extension to your campaign.
	Verify all configuration settings. Note When the product name and customer ID settings were are not configured as part of the destination, you must configure them as part of the data template before making this destination available to campaigns.
	Review all settings, and then click Save. After you have saved the data template, and depending on how you configured it, business users can send query results and/or send campaigns to DV360.

Google Audience Partner API Matching

DV360 matching can be done through the following list ID types:

• Contact information, including personally identifiable information (PII) matching

• European Union user consent

• Mobile device matching

Contact Info Matching

Personally identifiable information (PII) is any data that could potentially identify a specific individual. PII data includes details like names, addresses, email addresses, and other profile attributes, but can also include attributes like a loyalty number, customer relationship management (CRM) system identifiers, and foreign keys in customer data.

A list can be matched to contact information that contains PII data. If a row contains a NULL value, it will be automatically filtered out by the connector and will be shown in the error logs. Each field should be matched to (at least) one of the following columns:

Amperity Column	Google API Key	Description
Email Address	email	For this key, the connector: Trims leading and trailing whitespace Converts to lower-case Hashes data as SHA-256
Phone Number	phone	Converts each phone number to E.164 format which represents a phone number as a number up to fifteen digits in length (without spaces) that starts with a + symbol. For example: +12061234567. For this key, the connector: Trims leading and trailing whitespace Hashes data as SHA-256
Last Name	lastname	For this key, the connector: Trims leading and trailing whitespace Removes spaces in-between Converts to lower-case Hashes data as SHA-256
First Name	firstname	For this key, the connector: Trims leading and trailing whitespace Removes spaces in-between Converts to lower-case Hashes data as SHA-256
Zip Code	zip	For this key, the connector: Trims leading and trailing whitespace Converts to lower-case
Country Code	country	A two-letter country code in ISO 3166-1 alpha-2 format. For this key, the connector: Trims leading and trailing whitespace Converts to upper-case

European Union user consent

The Google Ads API uses the Consent object to specify user consent signals for sending user data to Google for advertising purposes and for ad personalization.

Important

Customers must send the the required user consent signals when uploading data for advertising to customers in the European Economic Area (EEA) and/or to adhere to the European Union (EU) user consent policy.

Required Column		Description
ad-personalization		Sets consent for ad personalization. Possible values: GRANTED, UNSPECIFIED, or DENIED. Important This value must be set to GRANTED to indicate that your brand has received the required user consent.
ad-user-data		Sets consent for sending user data to Google for advertising purposes. Possible values: GRANTED, UNSPECIFIED, or DENIED. Important This value must be set to GRANTED to indicate that your brand has received the required user consent.

Mobile Device ID Matching

A list can be matched to mobile device IDs. These may be identifier for advertising (IDFA) or Google advertising IDs (AAID) for mobile devices. If a row contains a NULL value, it will be automatically filtered out by the connector and will be shown in the error logs.

Amperity Column	Google API Key	Description
Mobile Device ID	mobile-id	A list of mobile device IDs provided to Amperity by the customer. For this key, the connector: Trims leading and trailing whitespace Converts to lower-case Retains any hyphens in the mobile device ID