This article describes the Tealium iQ requirements for enabling the DoubleClick Data Platform (DDP) cookie sync between Google and AudienceStream. The cookie sync is a basic pixel call that must be initiated from the browser, therefore you can configure Tealium iQ to make the call.
The Google ID is a device ID and not a visitor ID. Therefore it is possible for a visitor to have a different ID on their desktop, laptop, tablet, and phone devices. Please discuss with your AudienceStream Solutions Engineer the best method for handling this situation.
Add the Google Cookie Matching Service for Doubleclick tag. Always enter "tealium_dmp" as the Network ID. Next, insert your Tealium account name and the UDH profile you will be sending data to.
The Google Cookie Matching Service for Doubleclick tag will cause a chain of redirects (described below) where AudienceStream will eventually receive the Google ID from Google. This will be in the form of a parameter called "google_gid". This variable needs to be added in Tealium iQ so that you can leverage it for Rules in AudienceStream.
Upon initial implementation, it is important to check that AudienceStream is receiving the Google ID. Verifying receipt of the ID is discussed in another post, however, in order to see this in action, map "trace_id (cp)" to "tealium_trace_id".
The "trace_id" is not a default variable in the list and will need to be created as a First-Pary Cookie prior to being able to map the variable.
Next, the Google Cookie Matching tag should only run when the "Google ID" Sting (p.k.a. Trait) attribute is not defined. This way no extraneous calls are made to Google.
Each time we initiate a Google cookie sync request, the resulting pixel call (vdata/i.gif) that sends the Google ID to AudienceStream will count as a hit in AudienceStream and is therefore billable. Adding this load rule is strongly suggested otherwise your site traffic will immeidately double.
If the current profile is being used across multiple domains, be sure no domain specific rules are in place for the Tealium Collect Tag and the Cookie Matching tag. This will prevent a load rule from suppressing the Tealium Collect Tag (responsible for Data Layer Enrichment which the above load rule uses) on domain B and causing the Cookie Matching tag to run on every page load of domain B.
Make certain that you set the Data Enrichment to Frequent in your DataCloud Tag's configurations. This supports the requirements of the Load Rule.
Publish to Production so that the "google_gid" is available to AudienceStream and the functionality can be tested.
If the AudienceStream Visitor ID equals 01488eea146700207606aaa753381b078001307000ac2 a sample call in the browser will look like:
ium_dmp&google_cm&tealium_account=myaccount&tealiu m_profile=myprofile&tealium_vid=01488eea1467002076 06aaa753381b078001307000ac2
The above call will hit Google's server where it will perform a redirect to AudienceStream's server. The redirect will grab the tealium_account, tealium_profile, and tealium_vid parameters and append them to the URL. The redirect will also grab the Google ID and pass it along in the google_gid parameter. Here is a sample call:
_gid=CAESEJweV00B-gtxMs41BskLu2w&google_cver=1&tea lium_vid=01488fa778cf0022bfd4412874a81b078002e0700 0ac2&tealium_account=myaccount&tealium_profile=myp rofile