Skip to content

Commit 3e6314d

Browse files
authored
Update documentation on CSP (#4248)
- Add whitelisting approved domains - Add info section about support we're able to provide around CSP issues
1 parent 45cf0c9 commit 3e6314d

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,16 @@ Analytics.js 2.0 asynchronously loads different pieces of the library as needed.
5656
- `https://cdn.segment.com/analytics-next/bundles/*`
5757
- `https://cdn.segment.com/next-integrations/integrations/*`
5858

59+
Your CSP may also require whitelisting approved domains, in which case you'll want to allow the following endpoints:
60+
61+
- `api.segment.io`
62+
- `api.segment.com`
63+
- `track.segment.com`
64+
- `cdn.segment.com`
65+
66+
> info ""
67+
> Since Segment interacts with several integrations, support surrounding Content Security Policy issues is limited.
68+
5969
### Using trackLink on elements that are not links
6070

6171
Previously, it was possible to attach `trackLink` to any element, and a `trackLink` call would fire for that element if it wasn't a link. Now, when you attach `trackLink` to a non-link element, an additional search of that element's children occurs for any nested links and fires track calls based on those links. If you wish to fire track calls on non-link elements that have links as children, you can use a `track` call instead.

0 commit comments

Comments
 (0)