Reply
Highlighted
Visitor
Posts: 6
Registered: ‎03-28-2016
Accepted Solution

Why would a TRACE ID be gone when URL changes to secure?

Hi all,

 

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?

Reply
0 Kudos
New Member
Posts: 35
Registered: ‎09-15-2015

Re: Why would a TRACE ID be gone when URL changes to secure?

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?

New Member
Posts: 35
Registered: ‎09-15-2015

Re: Why would a TRACE ID be gone when URL changes to secure?

Anyone else seeing the same thing?

Reply
0 Kudos
Visitor
Posts: 6
Registered: ‎03-28-2016

Re: Why would a TRACE ID be gone when URL changes to secure?

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";

Tealium Employee
Posts: 264
Registered: ‎09-01-2015

Re: Why would a TRACE ID be gone when URL changes to secure?

[ Edited ]

@oneflash

 

I would recommend explicitly setting the domain and path using:

 

document.cookie = "trace_id=12345; domain=sometopleveldomain.com; path=/";

 

 

Adrian

Ask me anything Tealium related or Javascript, or NodeJS. But not cooking, can't do that.
Please remember to mark solutions as accepted for future searchers.
Reply
0 Kudos