Skip to content

Commit bb2163a

Browse files
authored
Merge pull request #5886 from segmentio/prigiattiperrut-patch-2
Add a note about Chrome third-party cookie restrictions.md
2 parents 47f9514 + 7b867f9 commit bb2163a

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

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

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -193,10 +193,16 @@ Some destinations accept properties only. As a result, custom context fields you
193193

194194
The AJS cookies being set under segment.com are first-party cookies. They are part of Segment's own implementation as well as the destination Segment uses. These cookies are not related to your implementation of Segment, and you only see them because you've visited Segment's domain using the same browser. They are sent to the writekey connected to Segment's own workspace, and are associated with the events Segment tracks when you visit segment.com.
195195

196+
## Will Google Chrome's third-party cookie changes impact Segment Analytics.js?
197+
198+
No, Analytics.js isn't affected by this change. This is because Analytics.js only creates first-party cookies. Unlike third-party cookies, which are set by external services and blocked by the [new Chrome update](https://developers.google.com/privacy-sandbox/3pcd){:target="_blank"}.
199+
200+
Regarding cookies set by [device-mode destinations](/docs/connections/destinations/#connection-modes), it's important to note that Segment's primary function is to load third-party SDKs and forward events to them. As a result, the usage and management of cookies are entirely at the discretion of each individual SDK. For instance, if you have concerns about destinations setting third-party cookies, it's best to consult directly with the destination providers for detailed information. For example, Amplitude, one of the destinations in the Segment catalog, offers [more information on this topic](https://www.docs.developers.amplitude.com/guides/cookies-consent-mgmt-guide/#frequently-asked-questions){:target="_blank"}.
201+
196202
## How is the referrer value set?
197203

198204
The Analytics.js library sets the `context.page.referrer` value from the `window.document.referrer` [property](https://developer.mozilla.org/en-US/docs/Web/API/Document/referrer){:target="_blank"} set in the browser. If you notice unexpected referrer values reaching Segment, check how this value is being set on your website.
199205

200206
## Known issues:
201207

202-
[Review and contribute to these on GitHub](https://github.com/segmentio/analytics.js/issues)
208+
[Review and contribute to these on GitHub](https://github.com/segmentio/analytics.js/issues).

0 commit comments

Comments
 (0)