Maximize your data resources by using Arm Treasure Data with Google DoubleClick Bid Manager .
You can create audience lists in your Google DoubleClick Bid Manager (DBM) using data held in Treasure Data. Follow these steps to move cookies and Mobile Advertising Identifiers to new or existing audience lists within Google DBM.
Google has rebranded DoubleClick Bid Manager to Display & Video 360, as part of the Google Marketing Platform.
For sample workflows on how to export to Google DoubleClick Bid Manager, view Treasure Boxes.
- Basic knowledge of Treasure Data, including the TD Toolbelt
- A Google DBM Account
- Authorized Treasure Data DMP access to your Google DBM Account
Grant access for Treasure Data
Treasure Data’s DDP (DoubleClick Data Platform) connector requires permissions to create audience segments in your Google DBM account. Use the Google
Contact Us form to reach the DoubleClick Bid Manager Support team and request that Treasure Data be granted access to your DBM account. Provide the following information in the form:
- Request: Grant Treasure Data permissions
- Your DoubleClick Bid Manager account ID (referred to by Google as the Partner ID or Advertiser ID)
- Treasure Data DMP:
- Customer-ID: 140-996-0635
- NID: treasuredata_dmp
You are sending information so that Google recognizes Treasure Data and connects your Google DBM 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” FROM “google_dbm_ddp”
Create or select an existing DBM on DDP connection
|Create a connector||
Go to Integrations Hub > Catalog and search and select DoubleClick Bid Manager.
- Complete the required fields on the first pane.
|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 Choose Saved Connection dialog opens.
- 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 Bid Manager DDP 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:
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 DoubleClick Bid Manager.
Additional connector configuration information
The manner in which Google handles your data from Treasure Data affects how you configure the connector.
The Google DBM (via DDP) 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 DDP will use 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 DBM audience. If the list name does not exist in DBM, 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, Google DDP side adds it automatically. If you rely on the value, we highly recommend specifying the column explicitly.
- 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 cookie_idfa or cookie_adid.
Supported cookie types are cookie_encrypted, cookie_idfa, and cookie_adid.
Limitations from Google DoubleClick Bid Manager
It may take up to 24 hours for updates to audience lists to be visible in DBM. Expect to wait up to 24 hours from the time of the query completion for changes to be reflected in DBM.