Skip to content

Commit c5d9fe6

Browse files
authored
Apply suggestions from code review
1 parent 96da428 commit c5d9fe6

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -179,11 +179,11 @@ Some destinations accept properties only. As a result, custom context fields you
179179

180180
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.
181181

182-
## Will Google Chrome's Third-Party Cookie Changes Impact Segment Analytics.js?
182+
## Will Google Chrome's third-party cookie changes impact Segment Analytics.js?
183183

184-
The short answer is no. Analytics.js will not be affected by this change. This is because Analytics.js functions as a first-party cookie. Unlike third-party cookies, which are set by external services and blocked by the [new Chrome update](https://developers.google.com/privacy-sandbox/3pcd), Analytics.js is integrated directly into the user's website or application. It sets cookies through the user's own bundled code, thus ensuring its status as a first-party cookie and guaranteeing its operational effectiveness despite Chrome's new policy.
184+
No, Analytics.js isn't affected by this change. This is because Analytics.js functions as a first-party cookie. 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"}, Analytics.js is integrated directly into the user's website or application. It sets cookies through the user's own bundled code, thus ensuring its status as a first-party cookie and guaranteeing its operational effectiveness despite Chrome's new policy.
185185

186-
Regarding cookies set by [device-mode destinations](https://segment.com/docs/connections/destinations/#connection-modes). It's important to note, that Segment 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 would be best to consult directly with the destination providers for detailed information. For example, Amplitude, one of the destinations in our catalog, offers an informative [article on this topic](https://www.docs.developers.amplitude.com/guides/cookies-consent-mgmt-guide/#frequently-asked-questions).
186+
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 an informative [article on this topic](https://www.docs.developers.amplitude.com/guides/cookies-consent-mgmt-guide/#frequently-asked-questions){:target="_blank"}.
187187

188188
## How is the referrer value set?
189189

0 commit comments

Comments
 (0)