Improving Metrics for Content Embedded via Microapps

Overview

When embedding content via microapps, organizations sometimes notice lower reach and engagement metrics than expected, for example when comparing to overall site traffic. This is typically because only authenticated user activity is fully tracked. Anonymous interactions are not captured at all.

This article explains how metrics are captured in microapps, outlines the differences between auth modes, and provides recommendations to improve login rates and overall engagement reporting.

Looking for training on Insights? Enroll in our eLearning course in the Training Center!

Why Metrics May Look Low

In many configurations, users can view content without logging in.
Anonymous activity cannot be tied to a user profile and therefore does not count toward reached users or unique opens.
A user is considered reached only after logging in, typically via the login card or login button.
Encouraging or requiring login is the most effective way to increase reported reach and engagement.

What Counts as Activity in Microapps

Activity is recorded only when an authenticated user views content.
Anonymous views do not generate reached user data.
Metrics such as clicks, engagement rate, or activity are likewise tied to logged-in users.

Auth Modes and Their Impact

Auth Mode	Best For	Login Prompt	Content Shown	Metrics Captured
Public	Lobby displays	None	Sharable content from all user topics	No
Restricted	Kiosks	Prompt at top of feed + configurable login card between content	Sharable content; personalized if user logs in	Yes, if user is signed in
Trusted	Intranets where login is expected	Prompt at top of feed + configurable login card between content	Shareable & non-shareable untargeted content; personalized if user logs in	Yes, if user is signed in
Admin	Curated, admin-only use	None	All content from any topic, including hidden topics	No

Recommendations to Improve Metrics

1. Enable SSO Autologin (Recommended)

Automatically directs users to your SSO provider without requiring a manual sign-in click.
Applies to both web and microapps (mobile login unchanged).
Requirements for SSO Autologin:
- Must use Restricted or Trusted auth mode.
- Login button and login card must both be hidden.
- SSO must be the sole authentication method (not dual auth or username/email login).
To enable this feature, please contact Firstup Support or your Customer Success Manager (CSM).

2. Select an Auth Mode That Drives Login

Restricted mode encourages login by limiting content until authentication.
Trusted mode works well for intranets where login is expected.
Avoid Public and Admin mode unless anonymous access is intentional (e.g., lobby displays and digital signage).

3. Make Login More Visible

Show Login Button at the Top of the feed (instead of only inline).
Reduces friction by giving users an easy, consistent login path.

Key Takeaways

Reported reach and engagement metrics in microapps reflect only logged-in user activity.
Anonymous activity is not reported.
To improve metrics:
- Enable SSO Autologin if eligible.
- Ensure login options are visible.
- Use Restricted or Trusted modes to encourage authentication.