Analytics and Usage
Read activity, MAU, delivery health, delta savings, and operator payment metrics correctly.
Explore a project
Open Usage & insights inside a project. Choose Today, 7/30/90 days, This month, Last month, Last 12 months, or Custom dates (up to 366 days). Group by day, week, or month and filter device activity by environment and platform.
All buckets use UTC, with weeks starting Monday. Custom end dates are inclusive; the underlying query stops before the next UTC midnight. Edge buckets include only dates inside the chosen window. Use Refresh for fresh data, View data for a chart's accessible table, and CSV for the filtered activity series. Device identifiers and raw event metadata are not exported.
Metrics and their sources
| Metric | Meaning |
|---|---|
| Active devices · SDK reported | Unique organization/device identities with any retained SDK event received in the selected window; not people |
| Update installs | SDK install_completed events, including full and delta updates; not App Store / Play Store installs |
| Completed downloads | SDK download_completed events; these may be staged before activation |
| Monthly active devices · checks | Distinct authenticated devices observed checking for updates in each full UTC calendar month |
| Applied delta patches | SDK download_delta_applied events |
| Reported patch savings | Reconstructed changed-file bytes minus patch bytes, divided by reconstructed bytes |
| Rollbacks | SDK install_failed_rollback events |
| CDN bandwidth | Not metered until a trusted egress pipeline supplies actual transferred bytes |
Do not add daily active counts to get monthly active devices: the same device can appear on multiple days. The range headline deduplicates over the entire window. The calendar-month check counter is independent from the date-bucketed SDK trend. For a project/environment/platform breakdown, the monthly check record belongs to the device's last observed project/environment/platform for that month.
SDK events are grouped by server receipt time, so offline reports appear when received, not at the original device time. Historical data is limited by retention and account deletion. Missing telemetry is not proof of no activity.
Understand delta efficiency
NativeScript reports the patch bytes and reconstructed sizes of the files it actually patched. That is not the total application tree, and it excludes unchanged cached assets, manifests, base64 encoding, HTTP/TLS, retries and full-file fallback traffic. A single NativeScript update may successfully patch one file while falling back to another, so applied and fallback counters are not disjoint.
Manifest authorizations mean an update URL was offered, not that a download
completed. They must not be counted as actual CDN bandwidth or charged as egress.
No reliable byte data should appear as unavailable, not as a measured 0 B.
Super-admin overview
Platform operators additionally see date-filtered new accounts and organizations, previous-window account growth, renewal collections/refunds, failed renewals, and current payment-backed active/past-due subscriptions. Ordinary project users cannot access these cross-organization aggregates.
Environment/platform filters affect device activity only, not customer signup or payment totals. Subscriptions and inventory cards are current snapshots, not historical states at the selected end date.
Collections count successful renewal charges by provider event timestamp; authorization, pending and failed charges are excluded. Refunds use their own event date, including refunds of earlier charges. Net collections can be negative in a refund-heavy period. Currencies are never combined. These are provider payment records—not accounting revenue, payout settlement, or MRR.
Use the existing customer, billing and release-health pages to investigate anomalies before increasing rollout or changing a subscription.