Upgrade to Analytics.js 2.0
Analytics.js 2.0 is fully backward compatible with Analytics.js Classic when you use the default Segment snippet in a standard implementation. To upgrade your sources, follow the manual upgrade steps below, or see the schedule for automatic migration. As with all upgrades, Segment recommends that you start development on a non-production source to test the upgrade process and outcome, prior to upgrading your production sources.
To upgrade a source to Analytics.js 2.0:
- In your Segment workspace, open the Connections page.
- On the Settings tab, open the Analytics.js category.
- Enable the flag for Analytics 2.0.
- Within 5 minutes, the source receives Analytics.js 2.0. No code or tag changes required.
- Open the Debugger to ensure that events are flowing as expected.
Analytics.js sources will upgrade to Analytics.js 2.0 on the date below, according to the account tier. On the date listed, Segment will upgrade all Analytics.js sources within the associated account tier.
|Segment Plan||Upgrade Date|
|Free||June 15, 2021|
|Team||July 6, 2021|
The plans and dates listed above are subject to change.
Revert to Analytics.js Classic
Once a source moves to Analytics.js 2.0, you can follow the steps above in Manual migration back to roll back to Analytics.js Classic.
Cases that require additional intervention
In some cases, upgrading to Analytics.js 2.0 requires manual effort beyond enabling the Analytics.js 2.0 toggle.
When using in-domain instrumentation CDN aliasing
If the source you intend to upgrade 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 or higher) before you toggle on Analytics.js 2.0.
When 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, you’ll need to configure your environment to accept the new format if your implementation relies on accessing the cookie value directly.
When using a strict content security policy on the page
This page was last modified: 03 Sep 2021
Questions? Problems? Need more info? Contact us, and we can help!