Merge pull request #4160 from segmentio/DOC-645

Analytics.js only sets first-party cookies

Author: stayseesong

src/connections/sources/catalog/libraries/website/javascript/index.md

@@ -770,7 +770,10 @@ Segment loads the libraries required for your **enabled** Destinations. When you
 
 Using Analytics.js doesn't offer a large performance benefit, but is more performant than installing each of the destinations individually. And as more destinations move to accept data directly from Segment, you'll receive more performance benefits automatically.
 
-One option, if you don't want to use any bundled third-party tools, is to use the browserify'd [analytics-node](https://github.com/segmentio/analytics-node) package. <!-- TODO LR note: WTF does "browserified" mean-->
+One option, if you don't want to use any bundled third-party tools, is to use the [Analytics-Node](https://github.com/segmentio/analytics-node) package. 
+
+> info ""
+> Analytics.js doesn't set third-party cookies and only sets first-party cookies. 
 
 ### Bundle size
 

src/connections/sources/catalog/libraries/website/javascript/persistence.md

@@ -17,6 +17,9 @@ If a user returns to your site after the cookie expires, Analytics.js looks for
 
 Analytics.js sets some default properties when creating cookies for user or group identities. You can override the default cookie properties in code when loading Analytics.js by passing in a `cookie` object to the load method.
 
+> info ""
+> Analytics.js doesn't set third-party cookies and only sets first-party cookies. 
+
 Here is the full list of available parameters with their default values:
 
 | Parameter | Description | Default value |