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:
Note
DV360 must be enabled before you can configure an orchestration to send query results.
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:
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
SELECT
Email AS email,
concat('+',regexp_replace(Phone, '(\s*)([^a-zA-Z0-9])', '')) AS phone,
LastName AS lastname,
FirstName AS firstname,
PostalCode AS zip,
'US' AS country
FROM Customer360
WHERE
email IS NOT NULL AND
Phone IS NOT NULL AND
FirstName IS NOT NULL AND
LastName IS NOT NULL AND
PostalCode IS NOT NULL
LIMIT 1000
Add orchestration¶
An orchestration defines the relationship between query results and a destination, including the location to which those query results will be sent and the frequency at which the orchestration will be run.
To add an orchestration
From the Destinations tab, click Add Orchestration. This opens the Add Orchestration dialog box.
From the Object Type drop-down, select Query.
From the Object drop-down, select the query for which results will be sent to DV360.
From the Destination drop-down, select a destination that is configured for sending data to DV360.
From the Data Template drop-down, select a data template.
Verify all settings.
Set the workflow to Manual. (You can change this to automatic later, after verifying the end-to-end workflow.)
Click Save.
Run orchestration¶
Run the orchestration manually to validate that it works.
To run the orchestration
From the Destinations tab, under Orchestrations, open the menu for the DV360 orchestration, and then select Run.
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.
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 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 |
Google API Key |
Description |
|---|---|---|
Email Address |
For this key, the connector:
|
|
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:
|
Last Name |
lastname |
For this key, the connector:
|
First Name |
firstname |
For this key, the connector:
|
Zip Code |
zip |
For this key, the connector:
|
Country Code |
country |
A two-letter country code in ISO 3166-1 alpha-2 format. For this key, the connector:
|
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. Not including these signals may result in lower match rates.
Required Column |
Description |
|
|---|---|---|
ad-personalization |
Sets consent for ad personalization. Possible values: GRANTED, UNSPECIFIED, or DENIED. Default value: UNSPECIFIED. 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. Default value: UNSPECIFIED. 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 |
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:
|