Maximize your data resources by using Treasure Data with Google DoubleClick for Publishers (DFP) DFP. 

Google DoubleClick for Publishers is now known as Google Ad Manager

You can create audience lists in your Google DoubleClick for Publishers (DFP) using data held in Treasure Data. Follow these steps to move cookies and Mobile Advertising Identifiers to new or existing audience lists within Google DFP.


Limitations from Google Ad Manager via Audience Partner API

Grant Access for Treasure Data

Treasure Data’s data connector requires permissions to create audience segments in your Google DFP account. Use the Google Contact Us form to reach the DoubleClick for Publishers Support team and request that Treasure Data be granted access to your DFP account. Provide the following information in the form:

Instructions on how to find your Audience link ID:

  1. Open Google Ad Manager.

  2. Select Admin > Global settings > All network settings.

  3. Find the Audience link ID.

You are sending information so that Google recognizes Treasure Data and connects your Google DPF 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.

Use the TD Console to Create Your Connection

Create a New Connection

In Treasure Data, you must create and configure the data connection prior to 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 that you use in your DFP.

Type a name for your connection.
Select Done.

Define your Query

Sometimes you need to define the column mapping before writing the query.

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 AdWords.

Column Mappings

The Google DBM (via DDP) reads data source table by columns and uses the following column name mappings to process each row data:

Optionally Define the Source Column Name Mappings

  1. Define the mapping between Google DDP column names to the output column names that you specify in your query.

  2. Specify the target column.

  3. Specify 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, a cookie is the same as cookie:cookie mapping.

Integration Parameters

Cookie or Mobile Identifier Column Header

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

You must select one of the options:

Example Query

 SELECT DISTINCT "cookie", "list_name", "time"
 FROM "google_dfp_ddp"

Optionally Schedule the Query Export Jobs

You can use Scheduled Jobs with Result Export to periodically write the output result to a target destination that you specify.

Optionally Configure Export Results in Workflow

Within Treasure Workflow, you can specify the use of this data connector to export data.

Learn more at Using Workflows to Export Data with the TD Toolbelt.