DMP Activation Notice DMP activation on Google Display Ads has been paused. Google stopped whitelisting new accounts for this feature; therefore, new accounts can't be used. That means new customers cannot use this connector for re-targeting. The Google change does not affect accounts that are already whitelisted; existing accounts can still use the feature. Customers that are currently using this connector will be able to continue using this connector until such time Google completely ends its support.
Connector Renaming Notice Google has rebranded Google AdWords to Google Ads, and DoubleClick was folded into Google Ad Manager. Therefore, this connector has been renamed from Google AdWords on the Doubleclick Data Platform to Google Ads via Audience Partner API. The name changed after Google rebranded Google AdWords to Google Ads.
Leverage your data in Treasure Data as you run marketing campaigns using Google Ads.
You can create audience lists in your Google Ads - DFP using data held in Treasure Data. Follow these steps to move cookies, IDFAs, and ADIDs to new or existing audience lists within Google Ads.
Continue to the following topics:
- Basic knowledge of Treasure Data, including the TD Toolbelt
- A Google Ads Account
- Authorized Treasure Data DMP access to your Google Ads Account
It may take up to 24 hours for updates to audience lists to be visible on Google Ads. Expect to wait up to 24 hours from the time of the query completion for changes to be reflected in Google Ads.
The Treasure Data Google Ads via Audience Partner API connector requires permissions to create audience segments in your Google Ads account. Send an email to Google Ads Support to grant Treasure Data access to your Google Ads account. Provide the following information in the email:
Request: Grant Treasure Data permissions
Treasure Data DMP:
- Customer-ID: 140-996-0635
- NID: treasuredata_dmp
You are sending information so that Google recognizes Treasure Data and identifies your TD account to your Google Ads account.
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.
- Go to the Query Editor. You can pick the query language and write your query.
- Select your database and table.
- Access the query that you plan to use to export data. Here is a sample query:
SELECT DISTINCT "cookie", "list_name", "time", "process_consent" FROM "google_adwords_ddp"| Option | Task Steps | Tip |
|---|---|---|
| Create a connector | Go to Integrations Hub > Catalog and search and select Google Ads via Audience Partner API. - Complete the required fields on the first pane. - In the AdWords Customer ID field, enter the ID that you use in Google Ads. Complete the Configuration fields. | Sometimes you need to define the column mapping before writing the query. |
| Select a connector | - Go to TD Console. - Go to Query Editor. - Access the query that you plan to use to export data. - Click Output results. The Choose Saved Connection dialog opens. - Type the connection name in the search box to filter and click the connection that you want. Complete the Configuration fields. | You can also create a new connection from here by clicking on Create New Connection. |
Creating a new connection:
Selecting an existing connection:
After you select your Google Ads via Audience Partner API connection, the Configuration dialog pane appears:
We recommend to select option Use Audience Partner APIsdue to the migration from Google APIs.
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 cookie:google_cookie. If the source column in the mapping is missing, the target column name will be used. For example, cookie is the same as cookie:cookie mapping.
See additional connector configuration information for more information about supported column names and usage.
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
See additional connector configuration information for more information on how identifier names are handled.
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.
Either save the query with a name and then run it or just run it. When the query completes successfully, the result is automatically processed. Plan to transfer your data at least 24 hours before you need the audience lists (also referred to as segments) to be in Google Ads.
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.
How Google handles your data from Treasure Data affects how you configure the connector.
The Google Ads via Audience Partner API reads the data source table by columns and uses the following column name mappings to process each row data:
| Column Name | Description |
|---|---|
| cookie | DDP will use the encrypted Google ID or Mobile Advertising Identifier in ID matching. This column contains your users' cookie hash or mobile identifier. |
| list_name | This column contains the name of the audience list (segment) you want to create in your Google Ads audience. A new list is created if the list name does not exist in Google Ads. If the list name does exist, 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 a number (0 or 1) to indicate if the cookie will be added or removed from the given audience segment. By default, the value will be false if the value is left blank or if a 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. |
The upload process supports several different identifiers, and it is important that these identifiers are uploaded to the segment using the correct upload file format. Generally, identifiers fall into one of 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 or cookie_epid 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, and cookie_adid.