Skip to content

Commit 051d894

Browse files
authored
Remove Manual Upgrade and Automatic Migration AJS
- Remove Manual Upgrade section because the flag to toggle Analytics.js on is no longer available in the customer's workspace - Remove Automatic Migration section because it mentions it in the yellow box directly above that so it seem redundant - Update section about reverting to AJS Classic to let customer know that it is no longer possible to revert to AJS Classic themselves (I intentionally didn't add anything about it being possible to revert to AJS Classic by request, because I worry this will encourage customers to use this as a temporary solution instead of upgrading to AJS 2.0 now) - Add sentence about how Cases That Require Additional intervention do not necessarily apply to every customer and remove reference to toggle
1 parent 02f7873 commit 051d894

File tree

1 file changed

+2
-20
lines changed

1 file changed

+2
-20
lines changed

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

Lines changed: 2 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -8,31 +8,13 @@ Analytics.js 2.0 is fully backward compatible with Analytics.js Classic when you
88
> warning "Deprecation of Analytics.js Classic"
99
> Analytics.js Classic was deprecated on February 28, 2023. At this time, Segment is upgrading all sources not yet upgraded to [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/). The upgrade process will complete for all users by the end of March 2023.
1010
11-
## Manual upgrade
12-
13-
To upgrade a source to Analytics.js 2.0:
14-
15-
1. In your Segment workspace, open the **Connections** page.
16-
2. Open the JavaScript source you will upgrade.
17-
3. On the **Settings** tab, open the **Analytics.js** category.
18-
4. Enable the flag for Analytics 2.0.
19-
5. Within 5 minutes, the source receives Analytics.js 2.0. No code or tag changes required.
20-
6. Open the Debugger to ensure that events are flowing as expected.
21-
22-
> info ""
23-
> If you set `'Segment.io:' false` in the integrations object, Analytics.js 2.0 drops the event before it reaches the Source Debugger.
24-
25-
## Automatic migration
26-
27-
On February 28, 2023, all Analytics.js Classic sources will automatically upgrade to Analytics.js 2.0.
28-
2911
## Revert to Analytics.js Classic
3012

31-
Once a source moves to Analytics.js 2.0, you can follow the steps above in [Manual migration](#manual-migration) to roll back to Analytics.js Classic.
13+
It is no longer possible to revert to Analytics.js Classic. If you are experiencing technical issues after the automatic upgrade to Analytics.js 2.0, please see below for cases that may require additional intervention. If you are still having issues after reading through the section below, please reach out to the Segment support team.
3214

3315
## Cases that require additional intervention
3416

35-
In some cases, upgrading to Analytics.js 2.0 requires manual effort beyond enabling the Analytics.js 2.0 toggle.
17+
In some cases, upgrading to Analytics.js 2.0 may require some additional intervention. This only applies to customers who are experiencing these specific issues and do not apply to all customers. In most cases, upgrading to Analytics.js 2.0 should not cause technical issues.
3618

3719
### Using in-domain instrumentation CDN aliasing
3820

0 commit comments

Comments
 (0)