Skip to content

Commit ee876bc

Browse files
authored
device mode cookie-validity-update.md
1 parent 7b1f937 commit ee876bc

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

src/connections/sources/catalog/libraries/website/javascript/cookie-validity-update.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,10 @@ analytics.load('writeKey', {
4646
> info ""
4747
> Chrome has a maximum limit of 400 days for cookies. If a value is set beyond that, then Chrome sets the upper limit to 400 days instead of rejecting it. Visit Chrome's [docs](https://developer.chrome.com/blog/cookie-max-age-expires/){:target="blank"} to learn more.
4848
49+
###Device-mode Destination Cookies
50+
51+
Our platform does not control cookie management for device mode destinations. Our primary function involves loading third-party SDKs and forwarding events to them. Consequently, the way cookies are used and managed is solely determined by each individual SDK. For example, if you have concerns about destinations setting third-party cookies, we advise consulting directly with the destination providers for clarification. For instance, Amplitude, one of the destinations in our catalog, provides an informative article on this topic.
52+
4953
### User settings
5054

5155
Analytics.js automatically persists the user's ID and traits locally. You can override how and where the user ID and traits are stored when loading Analytics.js by passing in a `user` object to the load method.

0 commit comments

Comments
 (0)