Skip to content

Commit 0b9a7fd

Browse files
committed
DOC-136 go live
2 parents 4f770ce + 40d04a9 commit 0b9a7fd

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

src/connections/sources/catalog/libraries/website/javascript/analytics-js-2.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,7 @@ Once enabled, after 5 minutes or less, the updated code is delivered.
4242
To revert back to the previous version of Analytics.js, disable the Analytics 2.0 toggle on any source you've enabled it.
4343

4444
## Cases that require manual upgrade
45+
<<<<<<< HEAD
4546
There are two cases where upgrading to Analytics.js 2.0 requires manual effort beyond enabling the Analytics.js 2.0 toggle.
4647

4748
### When using in-domain instrumentation CDN aliasing
@@ -51,11 +52,24 @@ If the source you intend to upgrade uses the in-domain instrumentation as well a
5152
### When using a strict content security policy on the page
5253

5354
Analytics.js 2.0 asynchronously loads different pieces of the library as needed. If the source you're upgrading uses a strict Content Security Policy (CSP) that allows Javascript to be downloaded from specific locations, then you need to update the CSP to account for all the pieces used for Analytics.js 2.0. Therefore, beyond allowing the main analytics.min.js script, you should allow the following paths in your CSP:
55+
=======
56+
We identified the following two cases where upgrading Analytics 2.0 requires manual effort beyond just enabling the Analytics 2.0 toggle.
57+
58+
### When using in-domain instrumentation CDN aliasing
59+
If your source uses the in-domain instrumentation as well as a custom "Alias for analytics.js", then you should update the AJS snippet to the latest version (4.13.2
60+
or higher) before toggling Analytics 2.0 on.
61+
62+
### When using a strict content security policy on the page
63+
Analytics 2.0 asynchronously loads different pieces of the library as needed, and therefore, if your source uses a strict Content Security Policy (CSP) that allows Javascript to be downloaded from specific locations, then you need to update the CSP to account for all the pieces used for Analytics 2.0. Therefore, beyond allowing the main analytics.min.js script, you should allow the following paths in your CSP:
64+
>>>>>>> master
5465
- `https://cdn.segment.com/v1/projects/<WRITE_KEY>/settings`
5566
- `https://cdn.segment.com/analytics-next/bundles/*`
5667
- `https://cdn.segment.com/next-integrations/integrations/*`
5768

69+
<<<<<<< HEAD
5870

71+
=======
72+
>>>>>>> master
5973
## Open source libraries
6074

6175
Analytics.js 2.0 includes the following open source components:

0 commit comments

Comments
 (0)