Cross-domain tracking and clearing of LocalStorage

[mschoenlaub]

We are seeing ajs_anonymous_id diverging between our subdomains, and as far as I know all subdomains use the default configuration with V1.46.1

When trying to reproduce the issue, we noticed that analytics-next seems to look for the ajs_anonymous_id in the following order:

Local Storage => Cookies for TLD => In-Memory

That seems to lead to breaking cross-domain tracking for users that at some point deleted their Local Storage and Cookies for our landing page subdomain, closes the window and surfs to it again.

We then end up with both subdomains having different ajs_anonymous_id in Local Storage and the cookie value for the TLD seemingly switching between these values as you navigate between the pages.

Are we doing something fundamentally wrong or is there a way to make analytics-next prefer the value in the Cookie over the Local Storage value?

[egmatwebmaster]

@chrisradek we are also facing this issue.
This is urgent, as this can break our websites tracking. Some of our subdomain apps do not have explicit logout buttons.

Please see this video - https://drive.google.com/file/d/1XGcHUDJpaKcJPAyChVSaZvjjZzHGO69O/view