We have noticed some issues with the way the `hubspotutk` cookie is set, depending on the domain.
When the first page the user visits is `welcome.whatever.**bleep**`, the cookie is set directly on that domain.
When the user then gets to `app.whatever.**bleep**`, the cookie is not accessible. (It is not on the .whatever.**bleep** top level domain.)
When the first the user visits is `www.whatever.**bleep**` the cookie is indeed set on the top level domain, so it is accessible to `app.whatever.**bleep**` and `welcome.whatever.**bleep**`.
Interestingly, when we use our .com domain, it does seems to work properly, even if the first page is `welcome.whatever.com`.
Any idea what this happens? We have found ourselves being required to set the cookie to the top level domain oursleves, just to be sure.
Are you still seeking insight into this question? Per our discussion here, it sounds like you were able to force the cookie to be placed on your top level domain but the root of the issue was interference from the Contacts API.
Yes, we still would love to get some information about why this happens. Why isn't the cookie placed on the Top Level Domain automatically, in some sub-domains?
In some, it does work as expected. What explains this behavior?
.png "HubSpot Employee"){kind=icon}
