Hi, I want to capture when a visitor comes from a digital ad link (query string value) and maintain that value to a second domain. I've followed these instructions: https://community.tealiumiq.com/t5/Tealium-iQ/Persist-Data-Value-Extension/ta-p/13623
Here's what I'm seeing: Visitor hits firstdomain.com with querystring quote=advisit. In the console I see utag_main_quote="advisit". Then the visitor clicks a link to seconddomain.com and I see utag_main_quote="undefined"
What am I doing wrong?
Persist: variable advisit
Duration: 1 Hours
Update: Allow Update on Page View (also tried Keep first value)
Store in Cookie: utag_main_quote
I appreciate your help.
The utag_main_ is a first party cookie, it is loaded on your firstdomain. Once on the seconddomain this cookie is a 'third party' cookie.
Third party cookies are also placed by advertisers and analytics, when you request a resource directly from an advertiser, like a pixel, it comes from a server on a different domain and it can place a 'cookie' when you make that request. Tealium's files are served from a CDN network on 'another' server but we do not place the cookies directly when serving those files, rather the code is loaded and run from within your code and off your webserver's domain. Hence the first party cookie.
TIQ does not have a built in third party cookie sync or matching service baked into the code. You can check with your specific analytics or advertiser vendor and see if they provide a cookie sync or matching service. You can then load that solution in tealium to process the cookies with their server/cookie/sync service.
If you have access to dev resources on your sites, then you can use a combination of placing a file on both webservers/domains and then loading that file from the 'other' domain in an iframe with the values getting passed in a query parameter. The 'other' domain requests this specific file from each other through an iframe. This file on the webserver would be blank but loading a specific utag.js file that reads the query parameters and sets them into a cookie. Since this file is requested off a server in another domain, it then writes the cookie on the other domain ( third party cookie ) . When you navigate to the second domain this same cookie becomes a first party cookie and can then be read. *source = @jason_paddock
I have the same issue mentioned above. Is this the same with subdomains? The cp_utag_main_cookie drops on siteA.example.com and then gets "undifined" on siteB.example.com.
I also checked the ut.domain and it's the same for both subdomains: ut.domain=example.com
Please note that we use the Cookie Consent Management functionality. I'm not sure if this could be related with the issue I'm facing as I don't know if it impacts the Tealium cookies.