You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This relates to #2907 . We noticed that _dd_s cookie is being written multiple times per second. Considering the main purpose of this cookie is tag the session id, it should change when the session id changes.
We have found that out because for some reason chrome is having trouble with _dd_s cookie when the front end application is running inside an iframe added to another website. The following message shows up around 8 times per second:
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies.
Notice that only show cookie with an issue is checked:
The text was updated successfully, but these errors were encountered:
Session cookie is indeed being written frequently. We are looking at issues regard this behavior lately, but we do not have an ETA for it yet.
That's said, we require first-party cookies(use of cookies docs) to be enabled and you need to collect consent before initializing the SDK(user tracking consent).
This relates to #2907 . We noticed that _dd_s cookie is being written multiple times per second. Considering the main purpose of this cookie is tag the session id, it should change when the session id changes.
We have found that out because for some reason chrome is having trouble with _dd_s cookie when the front end application is running inside an iframe added to another website. The following message shows up around 8 times per second:
Notice that only show cookie with an issue is checked:
The text was updated successfully, but these errors were encountered: