Mobile App Analytics: Key Metrics, Tools and Privacy (2026)
Updated October 2026 by the Cliffex team.
Mobile app analytics means measuring how people find, use and pay for your app, and how well the app itself performs. In practice you need two kinds of tools: a product analytics SDK (such as Google Analytics for Firebase, Mixpanel or Amplitude) for user behavior, and a crash and performance tool (such as Firebase Crashlytics or Sentry) for stability. Track a short list of metrics tied to your business goals, and collect data in a way that respects Apple’s App Tracking Transparency rules and user consent.
The mobile app analytics metrics that matter
Most teams track too much and act on too little. Group your metrics by the stage of the user journey and pick one or two per stage.
| Stage | Metrics | What it tells you |
|---|---|---|
| Acquisition | Installs by source, cost per install, store listing conversion | Which channels bring users, and at what cost |
| Activation | Sign-up and onboarding completion, time to first key action | Whether new users reach the point where the app becomes useful |
| Engagement | Daily and monthly active users (DAU, MAU), DAU/MAU ratio, sessions per user, feature usage | How often people come back and what they use |
| Retention | Day 1, Day 7 and Day 30 retention by install cohort; churn | Whether the app keeps its users over time |
| Monetization | Conversion to paid, average revenue per user (ARPU), lifetime value, subscription renewals | Whether the business model works |
| Performance | Crash-free users and sessions, ANR rate (Android), app start time, API response times | Whether technical problems are costing you users |
Be careful with published “average retention” or “ideal session length” benchmarks. They vary widely by category and method, and many circulating figures have no clear source. Your own cohort trends over time are a more reliable guide than an industry average.
App performance analytics: stability and speed
Performance problems show up in ratings and in store visibility. Google publishes hard thresholds: in Android vitals, the bad behavior threshold for user-perceived crash rate is 1.09% overall and 8% on any single phone model, and for user-perceived ANR (app not responding) rate it is 0.47% overall and 8% per phone model. Apps above these thresholds may see reduced visibility on Google Play and warnings on their store listing.
To analyze app performance properly, track:
- Crash-free users and sessions, broken down by app version, OS version and device model.
- ANRs and freezes, which users experience as a broken app even when nothing crashes.
- App start time (cold and warm starts) and screen render times.
- Network performance: API latency, error rates and payload sizes, ideally matched with your backend monitoring.
- Release health: compare each new version against the previous one in the first days after release, and halt a staged rollout if crash rates jump.
Google Play Console and App Store Connect both show crash and performance data for free, but the detail is limited. A dedicated tool adds stack traces, breadcrumbs and alerts.
Mobile app analytics tools compared
Free allowances and prices below were checked on each vendor’s pricing page in October 2026. They change often, so confirm before you commit.
| Tool | Best for | Free allowance (Oct 2026) |
|---|---|---|
| Google Analytics for Firebase | Core usage and event analytics, especially alongside other Firebase services | No charge; collection limits of 500 distinct named events and 25 parameters per event |
| Mixpanel | Product analytics: funnels, retention, cohorts | Up to 1M events per month on the Free plan |
| Amplitude | Product analytics, experiments, session replay | 2 million events per month on the Free plan |
| Firebase Crashlytics and Performance Monitoring | Crash reporting, app start and network traces | No charge |
| Sentry | Errors, crashes and tracing across app and backend | Developer plan: 1 user, 5,000 errors; Team plan from $26/month billed annually |
A common, low-cost setup for a new app is Google Analytics for Firebase plus Crashlytics. Teams that run lots of funnel and retention analysis often add Mixpanel or Amplitude. If you already use Sentry for your backend, using it in the app as well lets you trace a failing screen to the failing API call.
How to set up app tracking analytics properly
Good analytics is planned before anyone adds an SDK. The steps we follow:
- Write down the questions. For example: where do users drop out of onboarding, and which features do paying users use?
- Create a tracking plan. List each event, its parameters and when it fires, with a consistent naming convention (for example
checkout_started,checkout_completed). - Identify users consistently. Set a user ID at login so activity links up across sessions and devices, without sending names or emails as IDs.
- Respect consent from the start. Wire analytics to the consent choices described below.
- Test before release. Use debug views to confirm every event fires once, with the right values, on both iOS and Android.
- Build a small dashboard. One screen with your chosen metrics per stage, reviewed weekly.
- Maintain the plan. Update it with every feature release, and remove events nobody uses.
Privacy, App Tracking Transparency and consent
Analytics is where many apps run into privacy problems, usually through third-party SDKs. The main rules to know:
- Apple App Tracking Transparency (ATT). Since iOS 14.5, apps must get permission through the ATT prompt to track users or access the advertising identifier (IDFA). Apple defines tracking as linking data from your app with data from other companies’ apps, websites or offline properties for targeted advertising or ad measurement, or sharing it with data brokers. Without permission, the IDFA returns all zeros.
- Consent for usage data. Apple’s App Review Guidelines (5.1.1) require apps that collect user or usage data to secure user consent, even if the data is considered anonymous, and to give users an easy way to withdraw it.
- Privacy manifests. Apple requires a privacy manifest, and a signature for binary dependencies, for commonly used third-party SDKs, a list that includes FirebaseCrashlytics.
- Google Play Data safety. Every app must complete the Data safety form, and it must include data collected by third-party SDKs.
- EU and UK users. The GDPR requires a lawful basis, such as consent, for processing personal data. Google Analytics for Firebase supports consent mode, with four settings (analytics_storage, ad_storage, ad_user_data and ad_personalization) that change what the SDK collects.
Your privacy policy, consent wording and legal basis are decisions for your business and its advisers. We build the technical side to your requirements: consent screens, SDK configuration that waits for consent, data minimization and accurate store disclosures.
App analytics best practices
- Keep the tracking plan lean. Each event should answer a question someone will act on.
- Segment by app version, platform and acquisition source before drawing conclusions.
- Look at cohorts. A rising DAU can hide falling retention if acquisition spend is growing.
- Pair numbers with qualitative input such as reviews, support tickets and session replays.
- Keep personal data out of event names and parameters.
- Set alerts for crash spikes after each release.
Cost and timeline
For new apps, we include a tracking plan, analytics SDK and crash reporting in the build, so analytics does not usually change the project tier. A typical app with standard analytics falls into our Starter/MVP tier ($4,000–$10,000, 4–6 weeks) or Business tier ($10,000–$20,000, 6–12 weeks). Custom dashboards, data warehouse exports or in-app analytics for your own customers push projects toward Business or Advanced ($20,000+, 12–16+ weeks, scoped individually).
Every project includes 30 days of post-launch support. After that, work such as adding analytics to an existing app is billed hourly at $25–$49/hr: you describe the need, we send an estimate, and work starts after your approval. See pricing and our app cost guide.
How Cliffex can help
We design tracking plans, integrate analytics and crash reporting in iOS, Android, Flutter and React Native apps, and set up consent handling and store privacy disclosures. If your existing app has gaps in its data, we can audit and fix the setup. See our mobile app development services or send us your requirements.
Frequently asked questions
What are the most important mobile app analytics metrics?
Start with activation (onboarding completion), retention by cohort (Day 1, 7 and 30), active users, conversion to paid and crash-free users. Add others only when they answer a specific business question.
How do I analyze app performance?
Use a crash and performance tool such as Firebase Crashlytics or Sentry, plus Android vitals in Google Play Console and crash data in App Store Connect. Break results down by app version and device, and compare each release with the last.
Is Google Analytics for Firebase free?
Yes. Firebase lists Analytics, Crashlytics and Performance Monitoring at no charge on both its free and pay-as-you-go plans. Collection limits apply, such as 500 distinct named events.
Do I need the App Tracking Transparency prompt for analytics?
Only if you track users as Apple defines it (linking data with other companies’ data for advertising or ad measurement, or sharing with data brokers) or need the IDFA. First-party analytics without tracking does not need the ATT prompt, but Apple still requires consent for collecting usage data.