Skip to content

Commit e4a476c

Browse files
committed
FAQs for upgrading to A.js 2.0 [netlify-build]
1 parent f0a5476 commit e4a476c

File tree

1 file changed

+26
-0
lines changed

1 file changed

+26
-0
lines changed

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

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -70,3 +70,29 @@ Analytics.js 2.0 asynchronously loads different pieces of the library as needed.
7070
### Using trackLink on elements that are not links
7171

7272
Previously, it was possible to attach `trackLink` to any element, and a `trackLink` call would fire for that element if it wasn't a link. Now, when you attach `trackLink` to a non-link element, an additional search of that element's children occurs for any nested links and fires track calls based on those links. If you wish to fire track calls on non-link elements that have links as children, you can use a `track` call instead.
73+
74+
## FAQs
75+
76+
### I'm already using Analytics 2.0, why am I still receiving the message to upgrade?
77+
It's possible that a different source you are using is still leveraging an older version of Analytics.js. A very easy way to see which sources are on which versions is to go to the source overview page, then filter on the Analytics.js version.
78+
79+
It's also possible that you have used a write key from another source type (like Ruby) to instrument your Javascript source.
80+
81+
### Should I expect any glitches or downtime when switching to Analytics 2.0?
82+
Segment expects no downtime or glitches when switching to A.js 2.0.
83+
84+
### How can I validate that my source is using Analytics.js 2.0?
85+
If you're using A.js 2.0, the library field will look like the code snippet below ( `next` will be part of the version field):
86+
87+
```js
88+
"library": {
89+
"name": "analytics.js",
90+
"version": "next-1.XX.X"
91+
}
92+
```
93+
94+
### Are there specific things to test from an engineering point of view?
95+
Like any software upgrade, Segment advises you to start with one source, or a development or staging source. Then you should ensure that traffic is flowing the way you expect it to and that it goes to the appropriate destinations. There is detailed upgrade information in the documentation.
96+
97+
### What happens if I don't upgrade by the end of service date?
98+
There will not be any changes to your sources on the end of service date. However, if you encounter issues or need support, the support team will advise you to upgrade to 2.0. All new features will only be available on the 2.0 versions.

0 commit comments

Comments
 (0)