You can create audience lists in your Google Display and Video 360 Export Integration using data held in Treasure Data. This integration helps you move cookies and Mobile Advertising Identifiers to new or existing audience lists within Google Display and Video 360.
- Basic knowledge of Treasure Data, including the TD Toolbelt
- A Google Display and Video 360 account
- Authorized Treasure Data Google Display and Video 360 access to your Google Display and Video 360 account
Updates to audience lists may not be visible in Google Display and Video 360 for up to 24 hours after the query is completed.
Google Data Platform Policy (Identifying Users and Obtaining User Consent) requires that each segment identifies at least 100 users.
Treasure Data's Google Display & Video 360 (DV360) connector requires permission to create audience segments in your Google Display and Video 360 account. Use the Google Contact Us form to reach the DV360 support team and request that Treasure Data be granted access to your Google Display and Video 360 account.
Follow these steps to complete your configuration.
- In the advertiser menu, go to Settings > Linked Account.
- Link New Account > External Data Management Platform.
- Select Treasure Data.
- Select Link.
- Select the checkbox next to Agree as Company representative to agree to the terms of use.
- Select Create Link.
Before running your query, you must create and configure the data connection in Treasure Data. As part of the data connection, you provide authentication to access the integration.
- Open TD Console.
- Navigate to Integrations Hub > Catalog.
- Search for and select Display & Video 360.
- Select Create Authentication.
- Type the credentials to authenticate.
- Select Continue.
- Type a name for your connection.
- Select Done.
Define the mapping between Google DDP column names and the output column names you specify in your query. You select the target column and then the source column. For example, if google_cookie is the identifier column in your TD data source, you should define the mapping as a cookie:google_cookie. If the source column in the mapping is missing, the target column name will be used. For example, a cookie is the same as a cookie:cookie mapping.
Specify the source of the user cookie or mobile identifier.
You must select one of the options:
- cookie_encrypted: Encrypted identifier (for example, Web), a cookie hash of user-id
- cookie_idfa: iOS Advertising Identifier
- cookie_adid: Android Advertising Identifier
- cookie_epid: cookie externally provided id
- ppid: Publisher provided identifiers
The Google AdWords (via DDP) reads the data source table by columns and uses the following column name mappings to process each row data:
- cookie: The encrypted Google ID or Mobile Advertising Identifier that DDP will use in ID matching. This column contains your users' cookie hash or mobile identifier.
- list_name: This column includes the name of the audience list (segment) you want to create in your Google Display and Video 360 audience. A new list is created if the list name does not exist in Google Display and Video 360. If the list name exists, the existing list is updated.
- timestamp (optional): The timestamp (seconds since EPOCH). A current timestamp is used if this column does not exist or is missing.
- delete (optional): This column contains boolean values (false or true) or numbers (0 or 1) to indicate if the cookie is to be added or removed from the given audience segment. By default, the value will be false if the value is left blank or the column is not provided.
- process_consent (required for EU region): This column contains string values (false or true). Other values will be converted to empty strings. Empty strings are recommended. View https://support.google.com/admanager/answer/4349785?hl=en for more details.
Sometimes you need to define the column mapping before writing the query.
Plan to transfer your data at least 24 hours before you need the audience lists (also called segments) to be in Google DoubleClick Bid Manager.
| Parameter | Description |
|---|---|
| Source Column Name Mappings (Optional) | Define the mapping between Google DDP column names and the output column names you specify in your query. You select the target column and then the source column. For example, if google_cookie is the identifier column in your TD data source, you should define the mapping as a cookie:google_cookie. If the source column in the mapping is missing, the target column name will be used. For example, a cookie is the same as a cookie: cookie mapping. |
| Cookie or Mobile Identifier Name | The upload process supports several identifiers, and each type must be uploaded to the segment using the correct upload file format. Generally, the identifiers fall into two categories: encrypted identifiers (anything obtained from Google systems) and raw identifiers (obtained from an external system or source). Any encrypted identifier is uploaded using the cookie_encrypted file format, and raw identifiers are uploaded in a type-specific upload file format such as Mobile Advertising Identifiers, for example, cookie_idfa or cookie_adid. Supported cookie types are cookie_encrypted, cookie_epid, cookie_idfa, cookie_adid and ppid. |
| Membership Lifespan | The number of days a user's cookie stays on the user list. |
| Temp filesize threshold | Maximum file size (in bytes) of local temp file; that temp file will be flushed to remote file when it reaches a threshold. |
SELECT DISTINCT "cookie", "list_name", "time", "process_consent" FROM "google_dbm_ddp"You can use Scheduled Jobs with Result Export to periodically write the output result to a target destination that you specify.
Treasure Data's scheduler feature supports periodic query execution to achieve high availability.
When two specifications provide conflicting schedule specifications, the specification requesting to execute more often is followed while the other schedule specification is ignored.
For example, if the cron schedule is '0 0 1 * 1', then the 'day of month' specification and 'day of week' are discordant because the former specification requires it to run every first day of each month at midnight (00:00), while the latter specification requires it to run every Monday at midnight (00:00). The latter specification is followed.
Navigate to Data Workbench > Queries
Create a new query or select an existing query.
Next to Schedule, select None.
In the drop-down, select one of the following schedule options:
Drop-down Value Description Custom cron... Review Custom cron... details. @daily (midnight) Run once a day at midnight (00:00 am) in the specified time zone. @hourly (:00) Run every hour at 00 minutes. None No schedule.
| Cron Value | Description |
|---|---|
0 * * * * | Run once an hour. |
0 0 * * * | Run once a day at midnight. |
0 0 1 * * | Run once a month at midnight on the morning of the first day of the month. |
| "" | Create a job that has no scheduled run time. |
* * * * *
- - - - -
| | | | |
| | | | +----- day of week (0 - 6) (Sunday=0)
| | | +---------- month (1 - 12)
| | +--------------- day of month (1 - 31)
| +-------------------- hour (0 - 23)
+------------------------- min (0 - 59)The following named entries can be used:
- Day of Week: sun, mon, tue, wed, thu, fri, sat.
- Month: jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec.
A single space is required between each field. The values for each field can be composed of:
| Field Value | Example | Example Description |
|---|---|---|
| A single value, within the limits displayed above for each field. | ||
A wildcard '*' to indicate no restriction based on the field. | '0 0 1 * *' | Configures the schedule to run at midnight (00:00) on the first day of each month. |
A range '2-5', indicating the range of accepted values for the field. | '0 0 1-10 * *' | Configures the schedule to run at midnight (00:00) on the first 10 days of each month. |
A list of comma-separated values '2,3,4,5', indicating the list of accepted values for the field. | 0 0 1,11,21 * *' | Configures the schedule to run at midnight (00:00) every 1st, 11th, and 21st day of each month. |
A periodicity indicator '*/5' to express how often based on the field's valid range of values a schedule is allowed to run. | '30 */2 1 * *' | Configures the schedule to run on the 1st of every month, every 2 hours starting at 00:30. '0 0 */5 * *' configures the schedule to run at midnight (00:00) every 5 days starting on the 5th of each month. |
A comma-separated list of any of the above except the '*' wildcard is also supported '2,*/5,8-10'. | '0 0 5,*/10,25 * *' | Configures the schedule to run at midnight (00:00) every 5th, 10th, 20th, and 25th day of each month. |
- (Optional) You can delay the start time of a query by enabling the Delay execution.
Save the query with a name and run, or just run the query. Upon successful completion of the query, the query result is automatically exported to the specified destination.
Scheduled jobs that continuously fail due to configuration errors may be disabled on the system side after several notifications.
(Optional) You can delay the start time of a query by enabling the Delay execution.
You can also send segment data to the target platform by creating an activation in the Audience Studio.
- Navigate to Audience Studio.
- Select a parent segment.
- Open the target segment, right-mouse click, and then select Create Activation.
- In the Details panel, enter an Activation name and configure the activation according to the previous section on Configuration Parameters.
- Customize the activation output in the Output Mapping panel.
- Attribute Columns
- Select Export All Columns to export all columns without making any changes.
- Select + Add Columns to add specific columns for the export. The Output Column Name pre-populates with the same Source column name. You can update the Output Column Name. Continue to select + Add Columnsto add new columns for your activation output.
- String Builder
- + Add string to create strings for export. Select from the following values:
- String: Choose any value; use text to create a custom value.
- Timestamp: The date and time of the export.
- Segment Id: The segment ID number.
- Segment Name: The segment name.
- Audience Id: The parent segment number.
- + Add string to create strings for export. Select from the following values:
- Set a Schedule.
- Select the values to define your schedule and optionally include email notifications.
- Select Create.
If you need to create an activation for a batch journey, review Creating a Batch Journey Activation.
You can specify using this data connector to export data within Treasure Workflow.
Learn more at Using Workflows to Export Data with the TD Toolbelt.