On this page
App analytics appears in the console once the project has a registered app. The header filters by platform or by single app, and the choice carries over as you move between reports.
What each menu answers
| Menu | Question |
|---|---|
| Overview, Real-time | How many people are using it today; did the release we just shipped break anything |
| User analysis | New and active users per day, and how well they stay |
| Versions | Share of each version, and how many have upgraded |
| Channels | Which install channel brings the most users who stick around |
| Screens & paths | Which screens people use most, and where they go next |
| Custom events | Counts, people and properties of your business events |
| Device properties | Models, OS versions, networks and regions |
| Stability | Crashes, freezes and launch times |
What Real-time is for
Real-time windows are short: online users cover the last 30 seconds, launches and active users the last 5 minutes, launches per minute the last 30 minutes. Use it for two things — confirming data arrives after setup, and watching the crash count for a while after a release.
"vs. same time yesterday" compares the same five minutes yesterday, not the whole day.
New users count once
If someone installs on both iOS and Android, or uses the mini program before installing the app, the cross-platform view counts them as active on each platform but as new only on the platform where they first appeared. New users across platforms therefore add up to the de-duplicated total.
Channels are whatever you set
Channels in Channels come from the channel value you set and persist in the SDK — for example the store name written in at build time. Without one, users fall under "no channel". This isn't the media source an ad network reports back.
The channel matrix plots average daily new users against day-1 retention; the top right is where large channels that keep users sit. A brand-new channel shows an empty matrix until its first day-1 retention has matured.
Reading stability
- Crash-free users = 1 − crashed users ÷ active users.
- ANR — the Android main thread blocked for 5 seconds or more.
- UI freeze — the iOS or HarmonyOS main thread blocked for 2 seconds or more.
- Median cold-start time, warm-start time and memory.
Errors are grouped by message and can be marked resolved or ignored. Business failures (a failed payment callback, say) go in as custom exception events; they are summarised on their own tab and don't affect the crash-free share.
Not every platform captures crashes automatically in the same way; follow the setup wizard rather than assuming each one does.
Reports look empty right after setup
Stability and some summaries wait for the first launches to enter the daily roll-up. A teammate with edit rights can click Recalculate (last 7 days) on the stability page instead of waiting for the next day.
All platforms together
When a project has a website, an app and a mini program, the first item in Product analytics › Overview shows them side by side — active users, new users and retention per platform, plus one de-duplicated row across all of them.