From 7edec144b1f4620bc3cc4b572b3466930c10e523 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 8 Feb 2022 11:46:33 -0500 Subject: [PATCH 1/2] DOC-393 Updating note from Jira feedback --- .../catalog/libraries/website/javascript/upgrade-to-ajs2.md | 4 +++- 1 file changed, 3 insertions(+), 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 7d27ff659c..30f7f83cfc 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 @@ -50,7 +50,9 @@ 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 using the `utility` [plugin](/docs/connections/sources/catalog/libraries/website/javascript/index/#example-plugins) if your implementation relies on accessing the cookie value directly. +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. + +If you have configured different sources for different subdomains of your website, ensure that you switch them to Analytics 2.0 at the same time - this will guarantee that subdomain tracking will not break. In cases when you need to gradually update to Analytics 2.0, the `utility` [plugin](/docs/connections/sources/catalog/libraries/website/javascript/index/#example-plugins) will help match the ajs_anonymous_id cookie format and ensure that users are consistently identified across your subdomains. ### Using a strict content security policy on the page From 6388e98be6cbe49a84bca13cb53d25a5f9265e8a Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 8 Feb 2022 12:17:16 -0500 Subject: [PATCH 2/2] DOC-393 formatting and language changes --- .../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 30f7f83cfc..fc6814c888 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 @@ -52,7 +52,7 @@ 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. -If you have configured different sources for different subdomains of your website, ensure that you switch them to Analytics 2.0 at the same time - this will guarantee that subdomain tracking will not break. In cases when you need to gradually update to Analytics 2.0, the `utility` [plugin](/docs/connections/sources/catalog/libraries/website/javascript/index/#example-plugins) will help match the ajs_anonymous_id cookie format and ensure that users are consistently identified across your subdomains. +If you configured different sources for different subdomains of your website, switch them to Analytics 2.0 at the same time. Switching them at the same time ensures that subdomain tracking won't break. In cases when you need to gradually update to Analytics 2.0, the `utility` [plugin](/docs/connections/sources/catalog/libraries/website/javascript/index/#example-plugins) can help match the `ajs_anonymous_id` cookie format and ensure that users are consistently identified across your subdomains. ### Using a strict content security policy on the page