The Collection tag version property shows the version of the library used to collect the data. The first digit of the version tells you which collection method sent the data.
|
Platform |
Version |
Collection method |
|---|---|---|
|
Web (JavaScript) |
|
Piano Analytics JS SDK (the current SDK-based collection) |
|
Web (JavaScript) |
|
SmartTag. It's deprecated on the Analytics side for current implementations, but can still appear in legacy setups. |
|
Web (JavaScript) |
|
Older tagging methods (legacy, deprecated) |
|
Mobile (iOS and Android) |
|
Current Piano Analytics mobile SDKs |
|
Mobile (iOS and Android) |
|
Mobile SDK v2 (deprecated) |
For example, a report broken down by Collection tag version shows 6.8.2 for most of your web traffic and 5.29.1 for a few pages. This tells you that those pages still use SmartTag.
Values that don't match an SDK release
In most SDK-based implementations, the SDK fills in Collection tag version automatically, and the value matches the SDK version (for example, 6.7.0 or 6.8.2). The property can also be filled in other ways:
-
Custom tagging: it can send its own value for the property, which can lead to unexpected or mixed values.
-
Collection API: if you send events through the Collection API, you can set the version manually, which can also give values that don't match an SDK release.
If you see inconsistent values, for example several version families on the same page or app, or a value that doesn't match what you've deployed, review your tagging implementation. Check whether something overrides the property or sets it manually.
Changelogs
For more on versions, see the changelogs:
-
Piano Analytics: changelogs are on GitHub, under the releases of each repository. For example, see the PA SDK changelogs for JavaScript.
-
SmartTag: see the SmartTag changelogs.