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

oneflash
Silver Contributor
Silver Contributor oneflash

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?

4 REPLIES 4

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

Paul
Rookie Contributor
Paul

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?

Highlighted

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

Paul
Rookie Contributor
Paul

Anyone else seeing the same thing?

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

oneflash
Silver Contributor
Silver Contributor oneflash

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

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

Tealium Employee

@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.
Please remember to mark solutions as accepted for future searchers.