This integration is Deprecated.

DMP activation on Google Display Ads has been paused. Google stopped whitelisting new accounts for this feature. Therefore, new accounts can't use this feature. The Google change does not affect accounts that are already whitelisted. Existing accounts can still use the feature.

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

Limitations from Google Ads

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.

Grant Access for Treasure Data

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.

Create or Reuse a Query

  • 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" FROM "google_adwords_ddp"

Create or Select an Existing Google Ads via Audience Partner API Connection


Task Steps


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:

Configure the Connection by Specifying the Parameters

After you select your Google Ads via Audience Partner API connection, the Configuration dialog pane appears:

Source Column Name Mappings (Optional)

Define the mapping between Google DDP column names to the output column names that you specify in your the query. You specify 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, 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.

Cookie or Mobile Identifier Column Header

Specify the original source of the user cookie or mobile identifier.

You must select one of the options:


Encrypted identifier (for example, Web), a cookie hash of user id


iOS Advertising Identifier


Android Advertising Identifier


Cookie externally provided id

See additional connector configuration information for more information on how identifier names are handled.

Execute the Query

Either save the query with a name and then run the query or just run the query. When the query completes successfully, the result is automatically processed. Plan to transfer your data at least 24 hours ahead of when you need the audience lists (also referred to as segments) to be in Google Ads.

Additional Connector Configuration Information

The manner in which Google handles your data from Treasure Data affects how you configure the connector.

Column Mappings

The Google Ads via Audience Partner API reads data source table by columns and uses the following column name mappings to process each row data:


The encrypted Google ID or Mobile Advertising Identifier that DDP will use in id matching. This column contains the cookie hash or mobile identifier of your users.


This column contains the name of the audience list (segment) that you want to create in your Google Ads audience. If the list name does not exist in Google Ads, a new list is created. If the list name does exist, the existing list is updated.

timestamp (optional)

The timestamp (seconds since EPOCH). If this column does not exist or is missing, a current timestamp is used.

delete (optional)

This column contains boolean values (false or true) or number (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 if a column is not provided.

Cookie or Mobile Identifier Name

The upload process supports several different identifiers, and it is important that types of identifiers are uploaded to the segment using the correct upload file format. Generally, the 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_epidcookie_idfa, and cookie_adid.

  • No labels