You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/sources/catalog/libraries/website/javascript/analytics-js-2.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,6 +42,7 @@ Once enabled, after 5 minutes or less, the updated code is delivered.
42
42
To revert back to the previous version of Analytics.js, disable the Analytics 2.0 toggle on any source you've enabled it.
43
43
44
44
## Cases that require manual upgrade
45
+
<<<<<<< HEAD
45
46
There are two cases where upgrading to Analytics.js 2.0 requires manual effort beyond enabling the Analytics.js 2.0 toggle.
46
47
47
48
### 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
51
52
### When using a strict content security policy on the page
52
53
53
54
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:
0 commit comments