Overview

App Analytics is an in-builder dashboard that reports how a published app is actually being used. Opened from the Analytics item in the builder's left navigation, it shows usage and engagement for the current app — which screens people reach, where they drop off, and how they move through the experience — so you can see the health of what you shipped without leaving the builder.

The dashboard is itself a live UnifyApps app scoped to your app, and its charts are clickable: selecting a data point jumps you straight to the block, data source, or function it describes.

Note: The Analytics view collects and reports nothing until you enable analytics in the app's settings. A brand-new app has no usage data and its dashboard is empty until you turn on Enable Analytics.

Enabling Analytics

Analytics is off until you enable it. Turn it on in the builder's settings panel:

Open the builder for your app: From the Applications manager, open the app and enter the builder.
Go to Settings → Advanced Settings → Analytics: Find the Analytics panel under Advanced Settings in the Settings area.
Flip the Enable Analytics toggle: The toggle is described as gaining insight into user behavior, monitoring engagement across screens, and identifying drop-off points. Saving and republishing activates collection for all new user sessions.

Warning: Analytics only collects data from the moment it is enabled. Usage from before the toggle was turned on is not captured and will never appear in the dashboard.

The In-Builder Analytics View

After enabling analytics, the Analytics item appears in the builder's left navigation. Selecting it renders the analytics dashboard inside the builder — a live app pointed at your app's identifier so every chart is specific to your app and no other.

Dashboard Content

The dashboard presents:

Usage over time — sessions, page views, and active users across the selected period.
Screen-level engagement — which pages are reached most, time spent per page, and where users leave the app.
Drop-off analysis — which pages users exit from, revealing where flows break down.
Custom event tracking — named signals you define, plotted alongside standard metrics.

The dashboard's data points are interactive. Selecting a data point navigates you directly to whatever it represents:

Data point type	Where you're taken
A block	Opens in the component hierarchy with that block selected and active.
A data source	Opens in the data view with that resource selected.
A function or variable	Opens in the data view with that resource highlighted.
A block on another page	Navigates to that page first, then opens the block.

Warning: Selecting a data point moves you — it changes both the page you're on and the panel that's open. Treat the charts as navigation, not as read-only figures, and save your work before clicking.

Custom Events

Beyond the standard screen and navigation tracking, you can define custom events — named signals for moments that matter to your app and that automatic tracking wouldn't capture on its own. Custom events are only configurable after analytics is turned on.

Defining a Custom Event

Open Settings → Advanced Settings → Analytics: Navigate to the Analytics panel. The Custom Events catalog appears after enabling analytics.
Add a new custom event: Give the event a descriptive name (e.g. form_submitted, report_exported, search_performed). The name is how the event appears in the analytics dashboard.
Fire the event from an interaction: In the page builder, add the Track Analytics Event action to an event (e.g. button click, form submit). Select the custom event name you defined. When a user performs that interaction in the published app, the event is recorded.

Example — Tracking a key conversion action

You have an approval form. You want to know how many users actually click Submit Approval vs. how many just view the form.

In Analytics settings, create a custom event named approval_submitted.
On the Submit button's On Click event, add a Track Analytics Event action and select approval_submitted.
In the analytics dashboard, the approval_submitted event chart shows you submission frequency and lets you correlate it with the form page's view count — revealing the conversion rate.

Analytics Not Available for Template Components

The Analytics item is removed from the builder's left navigation when you are editing a template component rather than a full app. Template components are building blocks reused across apps, not standalone experiences with their own audience — there is no per-component usage view. Check analytics on the app that uses the component instead.

Web App Only

The in-builder Analytics view is available for web apps. On a web app, analytics only tracks signed-in users — visits by signed-out users of a public app are not counted. The mobile SDK analytics (e.g. Microsoft Clarity for session recording) are configured separately via Settings → Apps & Integrations.

Gotchas & Edge Cases

Nothing is collected until analytics is on

A brand-new app gathers no data and its dashboard is empty until you flip the toggle. If you expect a launched app to already have numbers, check whether analytics was enabled before launch — data only accrues from the switch-on point, never retroactively.

Insights tab on the detail page is also gated

The Insights tab on the app's detail page (outside the builder) appears only when analytics is enabled. If a teammate can't find the Insights tab, the toggle is likely still off. See App Insights.

Chart clicks navigate away

Selecting a data point is a jump, not a tooltip. It moves you to the block or resource, and if that thing lives on a different page it switches you to that page first. Treat charts as navigation, not as read-only figures.

App Insights — the Insights tab on the app detail page; when it appears and what it shows.
App Settings & Privacy — where analytics is enabled in the builder settings panel.

App Analytics