Google DoubleClick and AdWords Cookie Matching: Setting Up iQ Tag Management

[#1]

This article is part of the series: DoubleClick and AdWords Cookie Matching

---

This article describes the Tealium iQ requirements for enabling the DoubleClick and AdWords Data Platform (DDP) cookie matching between Google and AudienceStream. Cookie matching is a basic pixel call configured in iQ Tag Management.  

In this article:

Table of Contents Placeholder

Variables

By design, the Google Cookie Matching Service for Doubleclick tag will cause a series of redirects to another tracking pixels. As part of the redirection, AudienceStream eventually receives the Google ID from Google in the form of a parameter called google_gid. You will also need a cookie variable named trace_id to use for verification in AudienceStream.

The visitor attribute Google ID, created in AudienceStream, will later be used to create a load rule.

The Google ID is a device ID, not a visitor ID.

Use the following steps add the required variables:

1. In your iQ account, click the Data Layer tab.
2. Click +Add Variable.
3. In the Source field, enter google_gid .
4. In the Type field, ensure  UDO Variable is selected.
5. Click Apply.
6. Click +Add Variable.
7. In the Source field, enter trace_id .
8. In the Type field, select First Party Cookie.
9. Click Apply.
10. Click +Add Variable.
11. In the Source field, enter utag_main_dcsyncran .
12. In the Type field, select First Party Cookie.
13. Click Apply.

Cookie Sync Tag

Use the following steps to add the Google Cookie matching tag:

1. From the Tags tab, click Add Tag.
2. Add the Google Cookie Matching Service for Doubleclick tag and set the following fields:
   • Network ID: tealium_dmp
   • Tealium Account: [YOUR ACCOUNT NAME]
   • Tealium Profile: [YOUR PROFILE NAME]
     

     

3. Click Next.
   The Load Rules dialog displays.
4. Using the visitor attribute Google ID, created in AudienceStream, create a load rule with the following condition:
    Google ID is not defined and cookie utag_main_dcsyncran is not defined
5. This step ensures that the tag stops loading once cookie matching has occurred, and only loads once per session.  The latter is important especially if the user's browser does not allow DoubleClick to set its 3rd party cookie.  In that case, we wish to try again next session in case the user has changed their browser preferences.
   

   Without this load rule, your billable traffic to AudienceStream will double.

6. Click Next.
   The Data Mappings dialog displays.
7. Add a data mapping from trace_id to tealium_trace_id.
   
8. Click Apply.
9. Go to the Extension tab, and add a Persist Data Value extension scoped to the DoubleClick cookie sync tag you added above.
10. Store the value "1" in the cookie you added above to the Data Layer, for this session only;

Tealium Collect Tag

In the Tealium Collect tag, use the drop-down list to set Data Enrichment to Frequent.