Overview

App Analytics covers two things. The Enable Analytics setting turns on usage tracking for a published app: which screens people reach, where they drop off and which custom events fire. You read that usage data on the app's Insights tab; see App Insights. The Analytics item in the builder's left navigation opens App health, a report on how well the current app follows best practices.

App health is itself a live UnifyApps app scoped to your app, and its items are clickable: selecting one jumps you straight to the block, data source, or function it describes.

Note: Usage data is collected only after you turn on Enable Analytics. A brand-new app has no usage data, and its Insights tab stays hidden until analytics is on.

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.
Turn on Enable Analytics: The toggle sits under User Activity Insights. The builder saves the change automatically.
Publish the app again: Collection starts for new user sessions once the published app has analytics turned on.

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

The Analytics item is always in the builder's left navigation (keyboard shortcut Y). Selecting it opens App health inside the builder. App health checks how the app is built, not how it is used, so it does not need Enable Analytics or real-user traffic. The page score in the builder header also links to this view.

What App Health Shows

App health shows:

Health score: an overall score for the app.
Category scores: Usability, Issues, Performance and Security.
Page scores: a score for each page of the app.
Checks: the failed and passed checks, for example an empty On Click interaction.

Jumping to What a Check Describes

Items in App health are interactive. Selecting one takes you directly to whatever it describes:

Item 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 an item moves you. It changes both the page you're on and the panel that's open.

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 section appears after you turn on Enable Analytics.
Add a new custom event: Click Add Event and enter an Event Name (e.g. form_submitted, report_exported, search_performed). The name is how the event appears in your usage data. In Event Schema, declare the attributes the event carries.
Fire the event from an interaction: In the page builder, add the Send Custom Event action to an event (e.g. button click, form submit). Select the custom event you defined and fill its Event Payload. When a user performs that interaction in the published app, the event is recorded. See Send Custom Event.

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, click Add Event and create a custom event named approval_submitted.
On the Submit button's On Click event, add a Send Custom Event action and select approval_submitted.
On the app's Insights tab, compare how often approval_submitted fires with the form page's views to see 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.

Who Is Counted

Usage analytics works for web and mobile apps alike. It only counts signed-in users:

Web apps — visits by signed-out users of a public app are not counted.
Mobile apps — signed-out users are not counted, and a mobile app set to Public collects no analytics at all. Set the app's Access level to Private if you need usage data.

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 usage data until you turn on 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.

App Insights — the Insights tab on the app detail page; when it appears and what it shows.
Send Custom Event — the action that fires a custom event, with its Event Payload.
App Settings & Privacy — where analytics is enabled in the builder settings panel.

App Analytics