Screens

App analytics calls them screens. Mini program analytics calls them pages. It is the same report.

ConsoleApp analyticsBehaviorScreens & paths

The mini program entry is ConsoleMini program analyticsPages & eventsPages. See Pages & sharing.

What the report shows

Apps group by $screen_name, in a Screen column. Mini programs group by page path, in a Page path column. Each row has views, share, people, and average time on screen.

• Views are screen or page event counts. People are distinct subjects. Share uses total views under the current filter as the denominator.
• Time comes from the duration on the leave event: $screen_leave on apps, $mp_page_leave on mini programs. Without a leave event, time is empty. Do not read empty as zero seconds.
• Paths are neighboring screens (or pages) inside one session, keeping only the heavier flows. Long chains are cut, so this is not a replay.

How many screens fit in one session is in Engagement. Event names are in Preset events & properties.

FAQ

Why is the table empty? The app is not sending screen events. Current Android and iOS builds both need an explicit screen call. What is automatic is in SDK overview. Mini programs record paths after the page lifecycle is wrapped.

Is there a click heatmap? No. Apps and mini programs have no web-style click heatmap. Custom clicks are in Events.

Events

This is a catalog of event names, not a funnel or a path. For trends, breakdowns, and formulas on counts, unique users, or properties, use Event analysis.

ConsoleApp analyticsBehaviorCustom events

Mini programs use ConsoleMini program analyticsPages & eventsCustom events. The header filter limits the shell's platforms. If nothing has arrived yet, the page shows a track sample for that shell.

What the report shows

The summary is total events, people, distinct names, and interactive events. Each row is an event name. Expand it for property keys and value distribution. When there are many properties, only the more common values show.

Names that start with $ and are on the preset list show as preset events. See Preset events & properties. A $ name that is not on the list loses the prefix and is treated as an ordinary name. Preset and custom events share one list, told apart by name.

Limits

• Realtime's top events leave out preset names, so the leader there can differ. See Realtime.
• This catalog cannot be saved as an analysis or drilled into a person. To drill down, use Dig deeper on the overview to reach all-platform analytics.
• The property dictionary and validation are edited under data management in all-platform analytics, not here. Naming rules are in Events & properties.

Sharing

It applies only when the project has a mini program source. If it does not, the page says so. Register the app id first.

ConsoleMini program analyticsScenes & sharingSharing

What the report shows

Metric	Source	Meaning
Shares	$mp_share	How many forwards
Share returns	A start that carries $share_distinct_id	Opens that came back through a share
Sharers	People who shared	Distinct people, not share count
Return rate	Share returns ÷ shares	Average reopens per share
Depth	$share_depth	How many hops the chain has reached

The daily trend plots shares, returns, and sharers together, so you can see whether returns keep up when forwards rise. Depth shows which hop most shares stop on. The chain table lists shares and returns by page path.

How to read the result

Returns depend on $share_distinct_id arriving with the open. A forward that is never opened with that id produces no return. Depth is hops, not time on page. Scene values are the platform's entry code, while sharing is your own forward chain. See Scenes. Page paths are in Pages & sharing.