Adoption
Adoption in the OTA Updates area (Manage) — route /ota/adoption.
Adoption lives in the OTA Updates area of the dashboard, under Manage.
At a glance#
| Dashboard route | /ota/adoption |
| Area | OTA Updates (ota) |
| Group | Manage |
| Platforms | Available for every app platform. |
| Note | This entry points outside its area's usual /{area}/{slug} pattern. |
What it does#
Adoption answers one question for a release: how many devices actually took it. Over a 30-day window it tracks three counts — downloads (the bundle reached the device), installs (the device applied it), and rollbacks (the device reverted) — and the install rate, installs divided by downloads, which is the number that tells you whether an update is landing or getting stuck between download and apply.
Reading the page#
KPI cards summarise downloads, installs and rollbacks for the window, with the install rate derived from the first two.
The day-by-day timeline breaks the same counts out per day and adds a success percentage, so you can see an update roll out and spot the day a rollback spike began.
Patch efficiency shows how much bandwidth binary patches saved versus full downloads — total patches, the patch ratio, average patch size, and total bytes saved. Patches are the reason an OTA update is usually a fraction of the full bundle size.
Rollback analysis lists rollbacks per bundle so a single bad version stands out instead of hiding in an aggregate.
When to use it#
Right after you publish, to watch a release propagate, and any time the install rate diverges from the download count — that gap is devices that fetched the bundle but did not apply it, which usually points at the install mode or a guard.
Where the numbers come from#
Each device emits update-lifecycle events — checked, download started, download complete, installed, apply failed, and rolled back (automatically or manually) — and this page aggregates them. A device that downloads but never installs shows up as the difference between the two counts, not as a missing row.
Limits#
The window is the last 30 days. Counts are per device and per bundle, so a user who upgrades twice contributes to two releases. Very recent releases will still be climbing — read the timeline, not just the totals, before concluding an update has stalled.
Where the data comes from#
Served by
Ota