Cmdr analytics

Use this for true daily active installs and how fast the fleet rolls onto each new release. DAU here comes from the hourly heartbeat (distinct install ids per day), the trustworthy active-use number. The older update-check count is a weaker proxy (it only fires when the updater runs). Debug builds and anyone who opts out of analytics are excluded.

Use this for completed purchases and the revenue they brought in over the selected window. Paddle is the source of truth for money, so trust these numbers, just expect a little webhook lag near the present.

Use this to see whether paying customers stick around: the split of subscriptions by status (active, canceled, and so on). From Paddle, so it's reliable for money. It covers paid subscriptions only, not free-tier engagement (that's the Active use section and the funnel's D7).

Use this to read what people sent through in-app feedback and to see error-report bundles roll in, so you catch pain points fast. Feedback carries no install id (it's unjoinable to analytics), and error reports use a separate diagnostics id. Both are low-volume, so a short window can look empty even when things are fine.