09-08-2017 08:45 AM
I'm a partner setting up AS for a client. On the home page of the site I set a new Trace as generated by UDH. When I surf from the www.domain.com to secure.domain.com the Trace ID is gone (no trace id cookie as well). What would cause the failure of the Trace to persist across the transition?
Solved! Go to Solution.
09-08-2017 02:13 PM
Hey @oneflash. I've learned that trace sets the cookie at the sub domain. That's why you aren't seeing the cookie on secure.domain.com. Crazy right?
09-08-2017 02:25 PM
I agree - a bit crazy.
For others experiencing this, you can either paste your trace ID back into the Tealium tool, or use the brute force method in console: document.cookie="trace_id=12345";
09-29-2017 02:23 AM - edited 09-29-2017 02:24 AM
I would recommend explicitly setting the domain and path using:
document.cookie = "trace_id=12345; domain=sometopleveldomain.com; path=/";