Maximize your data resources by using Treasure Data with Google Ad Manager.
You can create audience lists in your Google Ad Manager using data held in Treasure Data. Follow these steps to move cookies and Mobile Advertising Identifiers to new or existing audience lists within Google Ad Manager.
- Basic knowledge of Treasure Data
- A DFP Account
- Authorized Treasure Data DMP access to your Google Ad Manager Account
- Pre-configuration on Treasure Data
- It may take up to 24 hours for updates to audience lists to be visible to Ad Manager. Expect to wait up to 24 hours from the query completion for changes to be reflected in Ad Manager.
- Google Data Platform Policy (Identifying Users and Obtaining User Consent) requires that each segment identifies at least 100 users.
Treasure Data's data connector requires permission to create audience segments in your Google Ad Manager account. Use the Google Contact Us form to reach the Google Ad Manager Support team and request that Treasure Data be granted access to your Google Ad Manager account. Provide the following information in the form:
- Request: Grant Treasure Data permissions
- Your Google Ad Manager account ID (referred to by Google as the Audience Link ID)
- Treasure Data DMP:
- Customer ID: 140-996-0635
- NID: treasuredata_dmp
Instructions on how to find your Audience link ID:
- Open Google Ad Manager.
- Select Admin > Global settings > All network settings.
- Find the Audience link ID.
You send information so that Google recognizes Treasure Data and connects your Google Ad Manager account to Treasure Data.
To export data, you create or select an existing connection, create or reuse a query, and then run the query to export your audience lists.
Certain configurations must be set up within your TD environment. Since this setup requires specific configurations, please consult your assigned Customer Success Manager if you are setting up this integration for the first time.
You must create and configure the data connection in Treasure Data before running your query. 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 Google Ad Manager via Audience Partner API.
- Select Create Authentication.
- Type the credentials to authenticate.
- In the Audience Link ID field, enter the ID you use in your DFP.
- Type a name for your connection.
- Select Done.
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 AdWords.
The Google Ad Manager 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 Google Ad Manager 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 Ad Manager audience. A new list is created if the list name does not exist in Google Ad Manager. If the list name exists, the existing inventory is updated.
- timestamp (optional): The timestamp (seconds since EPOCH). If this column does not exist or is missing, the Google Display and Video 360 side adds it automatically. We highly recommend specifying the column explicitly if you rely on the value.
- 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 string is recommended. View https://support.google.com/admanager/answer/4349785?hl=en for more details.
- Define the mapping between Google Ad Manager column names and the output column names you specify in your query.
- Specify the target column.
- Specify 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
PPID (Publisher-provided identifier) is only available in Google Ad Manager 360.
SELECT
DISTINCT "cookie", "list_name", "time", "process_consent"
FROM
"google_dfp_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 specify using this data connector to export data within Treasure Workflow.
Learn more at Using Workflows to Export Data with the TD Toolbelt.