Send query results 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.

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.

Important

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.

This topic describes the steps that are required to send customer data to DV360 from Amperity.

  1. Build a query

  2. Add orchestration

  3. Run orchestration

Caution

This destination is available for sending query results to DV360 after it is configured by a Datagrid Operator or your Amperity representative.

If this destintion cannot be selected from the campaigns editor or activations canvas ask your Datagrid Operator or Amperity representative to configure a destination for sending sending query results to DV360.

Build query

You will need to build a query that outputs fields that can be mapped to Google Audience Partner API matching keys, one of:

  1. Contact information, including personally identifiable information (PII) matching

  2. Mobile device matching

Note

DV360 has specific requirements. Define a query, and then export it as a CSV file to profile the data.

  • Add and normalize the country code when states are US and Canada, but the country is NULL.

  • Phone numbers are required to have a +11231234567 format.

  • First name, last name, zip code, and country are all required for the “Contact Info” upload key. If any are missing, none are passed.

Example

 1SELECT
 2  Email AS email,
 3  concat('+',regexp_replace(Phone, '(\s*)([^a-zA-Z0-9])', '')) AS phone,
 4  LastName AS lastname,
 5  FirstName AS firstname,
 6  PostalCode AS zip,
 7  'US' AS country
 8FROM Customer360
 9
10WHERE
11  email IS NOT NULL AND
12  Phone IS NOT NULL AND
13  FirstName IS NOT NULL AND
14  LastName IS NOT NULL AND
15  PostalCode IS NOT NULL
16
17LIMIT 1000

Add orchestration

An orchestration defines the relationship between query results and a destination, including the destination and the frequency at which an orchestration runs.

To add an orchestration

  1. Open the Activations page, select the Orchestrations tab, and then click the Add orchestration button. This opens the Add orchestration dialog box.

  2. From the Object type dropdown, select Query.

  3. From the Object dropdown, select the query for which results will be sent to DV360.

  4. From the Destination dropdown, select a destination that is configured for sending data to DV360.

  5. Verify all settings.

  6. Set the workflow to Manual. (You can change this to automatic later, after verifying the end-to-end workflow.)

  7. Click Save.

Run orchestration

Run the orchestration manually to validate that it works.

To run the orchestration

  1. Open the Activations page, select the Orchestrations tab, and then open the    menu for the DV360 orchestration. Select Run.

  2. The Status column for the orchestration will update to say “Waiting to start…”, after which the notifications pane will update to include a notification that shows the current status.

  3. When the orchestration has run successfully, the status is updated to “Completed”.

Google Audience Partner API Matching

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

Contact Info Matching

Personally identifiable information (PII) is any data that could identify a specific individual. PII data includes details like names, addresses, email addresses, and other profile attributes. PII data sometimes includes attributes like a loyalty number, customer relationship management (CRM) system identifiers, or 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

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

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

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