Maximize your data resources by using Treasure Data with Google DoubleClick for Publishers on 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.
- Basic knowledge of Treasure Data, including the toolbelt
- A DFP Account
- Authorized Treasure Data DMP access to your Google DFP Account
Grant access for Treasure Data
Treasure Data’s data connector requires permissions to create audience segments in your Google DFP account. Send an email to the DoubleClick for Publishers Support team (email@example.com) and request that Treasure Data be granted access to your DFP account. Provide the following information in the email:
- Request: Grant Treasure Data permissions
- Your DoubleClick for Publishers 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. Basically, in Google Bid Manager, you click Admin > Global settings > All network settings to 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.
Create or reuse a query
- Go to Treasure Data console
- Go to 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"
Create or select an existing DFP connection
|Create a connector||- Go to Connections.
- Click on the
- Complete the required fields on the first pane.
- In the Audience Link ID field, enter the ID that you use in your DFP.
Next you complete the Configuration fields.
|Sometimes you need to define the column mapping before writing the query.|
|Select a connector||- Go to Treasure Data console.
- Go to Query Editor.
- Access the query that you plan to use to export data.
- Click Output results. The
- Type the connection name in the search box to filter and click the connection that you want.
Next you 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 DoubleClick for Publishers DP 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
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:
cookie_encrypted: Encrypted identifier (for example, Web), a cookie hash of user id
cookie_idfa: iOS Advertising Identifier
cookie_adid: Android Advertising Identifier
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 AdWords.
Additional connector configuration information
The manner in which Google handles your data from Treasure Data affects how you configure the connector.
The Google DFP reads 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 is used in id matching. This column contains the cookie hash or mobile identifier of your users.
- list_name: This column contains the name of audience list (segment) that you want to create in your DFP audience. If the list name does not exist in DFP, 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 value is left blank or if 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 file format, and raw identifiers are uploaded in a type-specific upload file format such as Mobile Advertising Identifiers, for example
Supported cookie types are
Limitations from Google DoubleClick for Publishers
It may take up to 24 hours for updates to audience lists to be visible DFP. Expect to wait up to 24 hours from the time of the query completion for changes to be reflected in DFP.