Version Adoption
Version adoption analytics show which package versions are currently active in tenant environments. Publishers use this data to understand upgrade rates, identify legacy version usage, and make informed decisions about when to end support for older versions.
What Version Adoption Shows
| Metric | Definition |
|---|---|
| Active tenants per version | Count of tenants currently running each published version, based on last usage in the 30-day window |
| Version share (%) | Each version's percentage of total active tenants |
| Upgrade rate | Percentage of tenants who upgraded to a new version within 30 days of the version's release |
| Legacy alert threshold | Versions flagged as "legacy" when they are more than 2 major versions behind the current release and still have active tenants |
Version Adoption Chart
The version adoption view presents a stacked bar chart where each bar represents a point in time (week or month) and the bar segments show how the active tenant base was distributed across versions. This chart reveals:
- How quickly tenants adopted a new version after release
- Whether old versions are dying down or persisting stubbornly
- Whether a version release caused a split in the tenant base (some upgraded, others stayed)
Legacy Version Alerts
The system automatically flags packages where a significant portion of active tenants are still on legacy versions. A "legacy version alert" is triggered when:
- A version is more than 2 major versions behind the latest release, AND
- That version still has more than 10% of active tenants on it
Legacy alerts appear in the Version Adoption page and also in the Publisher Dashboard summary. They serve as a prompt to communicate with tenants on old versions — a targeted announcement encouraging upgrade before support ends.
If a significant portion of tenants are running a legacy version that has known vulnerabilities (discovered after the package was certified), the package may be flagged for a Certified certification review. The Version Adoption analytics help publishers stay ahead of this by proactively managing the upgrade cycle.
Upgrade Rate Analysis
The upgrade rate for each version release is calculated as:
Upgrade rate = (tenants on new version 30 days after release) / (total active tenants at release date) × 100
A high upgrade rate (above 60% in 30 days) indicates tenants trust the publisher's releases and maintain up-to-date installations. A low upgrade rate may indicate:
- A breaking change in the new version that tenants are hesitant to adopt
- Insufficient communication about what the new version includes and why upgrading is beneficial
- Enterprise tenants with change management processes that delay upgrades