App Analytics
Lifecycle & quality analytics
A separate product line for Android and iOS apps: active and new users, launches, versions and channels, retention, custom events, plus crashes, ANRs and launch time — Web PV definitions are not reused.
Platforms
AndroidiOS
Capabilities
What App Analytics does
Launches & sessionsLaunches, foreground/background and usage time are collected automatically; returning after 30+ seconds in the background counts as a new launch.
ScreensActivities / UIViewControllers are recorded as screen views automatically, Fragment / Compose / SwiftUI screens manually; see views, time on screen and crashes per screen.
Versions & channelsCompare users, launches, session length and crashes by app version and install channel.
Crashes & ANRsCrashes, ANRs and main-thread hangs captured with xCrash (Android) and KSCrash (iOS), grouped by stack, with affected users, versions and devices.
Retention & activityActive users, new users, launches per user, and day 1–7, 14 and 30 retention of new users.
Launch time & eventsP50 / P75 / P90 for cold, warm and hot starts; business events and properties via Fmeng.track.
Metrics
How the core metrics are defined
An app screen view is not a Web pageview and bounce rate does not carry over; app data lives in its own tables and reports use app definitions.
Get started
Up and running in three steps
01Create an appAdd the app under "My apps" in the console to get an APP_KEY.
02Integrate the SDKAdd one Gradle dependency on Android, or Swift Package Manager / CocoaPods on iOS, and initialize it at launch.
03Explore the reportsLaunch the app once to see activity, retention, versions, crashes and launch time on the dashboard.
FAQ