# Mobile app analytics for beginners: what to measure

> Start mobile app analytics by tracking a handful of metrics tied to your goals: installs, activation, retention, engagement, and revenue. Use an analytics tool such as Firebase or Mixpanel, define key events, and review the data regularly to guide improvements.

Source: https://keepwarning.com/blog/mobile-app-analytics-for-beginners/  
Publisher: KeepWarning (Columbia, MD)  
Topic: App marketing and growth  
Updated: October 12, 2026

## Key takeaways

- Track few metrics well rather than everything poorly.
- Core metrics: acquisition, activation, retention, engagement, and revenue.
- Define a small set of key events (sign-up, first purchase) from day one.
- Respect privacy: collect only what you need and disclose it.

You cannot improve what you cannot see. Analytics shows how people actually use your app, which is often different from what you assume.

## The metrics that matter

| Stage | Question | Metrics |
| --- | --- | --- |
| **Acquisition** | Where do users come from? | Installs by source, cost per install |
| **Activation** | Do they reach value? | % completing sign-up or first key action |
| **Retention** | Do they come back? | Day 1, 7, 30 retention |
| **Engagement** | How do they use it? | Daily and monthly active users, sessions, key feature use |
| **Revenue** | Does it pay? | Conversion to paid, average revenue per user, lifetime value |
| **Quality** | Does it work? | Crash-free sessions, load times, ratings |

## Set up tracking the right way

1. **Define goals** in plain words ("Users book their first appointment within a week").
2. **Choose events** that show progress toward those goals: sign-up, onboarding complete, first purchase, subscription start.
3. **Name events consistently** and document them.
4. **Add properties** (plan type, source) that help you segment.
5. **Test tracking** before launch.

## Tools

- **Google Analytics for Firebase** for general usage, free.
- **Mixpanel** or **Amplitude** for deeper product analytics.
- **Crash reporting tools** such as Firebase Crashlytics or Sentry.
- **App store dashboards** for impressions and installs, which help with [ASO](/blog/app-store-optimization-guide/).

## Turn data into decisions

Every month, review the numbers and ask: where do most users drop off, which feature drives return visits, which channel brings users who stay? Fix the biggest problem first, ship, and measure again. This is how you improve [retention](/blog/reduce-app-uninstalls-and-boost-retention/) and [revenue](/blog/app-monetization-models/).

## A starter measurement plan

Write this down before you build, so tracking is part of the product.

| Goal | Key event(s) | Metric | Target example |
| --- | --- | --- | --- |
| Get new users | `install`, `sign_up_completed` | Sign-up rate from install | 40% |
| Reach value quickly | `first_booking_completed` | % of new users completing it in week one | 30% |
| Keep users | App opens by cohort | Day 7 and day 30 retention | Improve each release |
| Earn revenue | `purchase`, `subscription_started` | Conversion to paid, revenue per user | 3% |
| Stay stable | Crashes, slow screens | Crash-free sessions | 99.5% |

Keep the list short. Five to ten events are plenty at the start.

## Funnels: finding where people give up

A **funnel** shows the percentage of users who complete each step of a process.

Example: Install (100%) then Open (85%) then Sign-up started (55%) then Sign-up completed (35%) then First booking (18%).

The biggest drop (sign-up started to completed, 20 points) is where to focus first. A shorter form or a social login might raise the whole funnel.

## Cohorts and segments

- **Cohorts** group users by when they joined, so you can see if new releases improve retention.
- **Segments** group users by traits such as source, plan, device, or country, so you can see who behaves differently and why.

## Common analytics mistakes

1. **Tracking everything and learning nothing.** Choose events tied to decisions.
2. **Inconsistent naming,** which makes reports unreliable.
3. **Ignoring data quality.** Test events before launch and after each release.
4. **Vanity metrics.** Downloads alone do not mean success.
5. **Collecting personal data you do not need,** which raises privacy and compliance risk.
6. **Never looking.** Schedule a monthly review with decisions and owners.

## Privacy basics

Disclose analytics in your privacy policy, answer the store privacy questions accurately, respect user choices such as the iOS tracking prompt where it applies, and prefer aggregated data. Treat privacy as part of [security](/blog/mobile-app-security-checklist/).

## Privacy and trust

Collect only what you need, explain it in your privacy policy, and complete the store privacy disclosures accurately. Good data practice builds trust.

## Frequently asked questions

### What metrics should I track for a mobile app?

Installs, activation (users completing the first key action), retention at day 1, 7, and 30, active users, session behavior, conversion, revenue, and crash rate.

### What are the best free analytics tools for apps?

Google Analytics for Firebase is a widely used free option. Others, such as Mixpanel and Amplitude, offer free tiers for product analytics.

### Do I need consent to track users?

Privacy rules apply. Disclose your data collection in your privacy policy and the store privacy forms, and follow platform rules such as Apple's App Tracking Transparency where relevant.