From 9809926ec65471527a14e72ead4336b6621a10e4 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 26 Jan 2022 12:00:40 -0500 Subject: [PATCH 1/3] Adding admonition infrastructure --- .../catalog/libraries/website/javascript/upgrade-to-ajs2.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md b/src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md index c148ab7dc3..e2ba914e3e 100644 --- a/src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md +++ b/src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md @@ -48,6 +48,9 @@ If the source you intend to upgrade uses the in-domain instrumentation as well a Analytics.js 2.0 removes inbuilt quotes from cookie values, resulting in a different format for the `ajs_anonymous_id` value when compared to Analytics.js Classic. Though you can retrieve cookie values with [standard supported functions](/docs/connections/sources/catalog/libraries/website/javascript/identity/#retrieve-the-anonymous-id), you'll need to configure your environment to accept the new format if your implementation relies on accessing the cookie value directly. +> warning " Using the`utility` plugin" +> Users who + ### Using a strict content security policy on the page 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: From 7854ee7eed2a480f597795511e170d127aa27063 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 27 Jan 2022 16:03:41 -0500 Subject: [PATCH 2/3] DOC-393 Taking it out of an admonition format and adding it to the paragraph above it --- .../catalog/libraries/website/javascript/upgrade-to-ajs2.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md b/src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md index e2ba914e3e..f45d0acb0d 100644 --- a/src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md +++ b/src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md @@ -46,10 +46,7 @@ If the source you intend to upgrade uses the in-domain instrumentation as well a ### Relying on Analytics.js Classic's `ajs_anonymous_id` cookie format -Analytics.js 2.0 removes inbuilt quotes from cookie values, resulting in a different format for the `ajs_anonymous_id` value when compared to Analytics.js Classic. Though you can retrieve cookie values with [standard supported functions](/docs/connections/sources/catalog/libraries/website/javascript/identity/#retrieve-the-anonymous-id), you'll need to configure your environment to accept the new format if your implementation relies on accessing the cookie value directly. - -> warning " Using the`utility` plugin" -> Users who +Analytics.js 2.0 removes inbuilt quotes from cookie values, resulting in a different format for the `ajs_anonymous_id` value when compared to Analytics.js Classic. Though you can retrieve cookie values with [standard supported functions](/docs/connections/sources/catalog/libraries/website/javascript/identity/#retrieve-the-anonymous-id), you'll need to configure your environment to accept the new format if your implementation relies on accessing the cookie value directly. You can use the `utility` [plugin](docs/connections/sources/catalog/libraries/website/javascript/#example-plugins) to format your Analytics.js Classic cookies to match the Analytics.js 2.0 format. ### Using a strict content security policy on the page From b5f0aab1f9a621fef1e230e068de2295ec44bac4 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 28 Jan 2022 11:43:23 -0500 Subject: [PATCH 3/3] [DOC-393] Simplifying the information, adding it to the sentence before it --- .../catalog/libraries/website/javascript/upgrade-to-ajs2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md b/src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md index f45d0acb0d..b48df64b70 100644 --- a/src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md +++ b/src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md @@ -46,7 +46,7 @@ If the source you intend to upgrade uses the in-domain instrumentation as well a ### Relying on Analytics.js Classic's `ajs_anonymous_id` cookie format -Analytics.js 2.0 removes inbuilt quotes from cookie values, resulting in a different format for the `ajs_anonymous_id` value when compared to Analytics.js Classic. Though you can retrieve cookie values with [standard supported functions](/docs/connections/sources/catalog/libraries/website/javascript/identity/#retrieve-the-anonymous-id), you'll need to configure your environment to accept the new format if your implementation relies on accessing the cookie value directly. You can use the `utility` [plugin](docs/connections/sources/catalog/libraries/website/javascript/#example-plugins) to format your Analytics.js Classic cookies to match the Analytics.js 2.0 format. +Analytics.js 2.0 removes inbuilt quotes from cookie values, resulting in a different format for the `ajs_anonymous_id` value when compared to Analytics.js Classic. Though you can retrieve cookie values with [standard supported functions](/docs/connections/sources/catalog/libraries/website/javascript/identity/#retrieve-the-anonymous-id), you'll need to configure your environment to accept the new format using the `utility` [plugin](/docs/connections/sources/catalog/libraries/website/javascript/index/#example-plugins) if your implementation relies on accessing the cookie value directly. ### Using a strict content security policy on the page