Mobile App Analytics (Firebase)

Tools and platforms that track user behavior, engagement, crashes, and conversions in mobile applications, with Firebase as the industry standard.

Definition

Mobile App Analytics is the collection, measurement, and analysis of user behavior within a mobile app. It covers install tracking, session analysis, event logging, user property tracking, crash reporting, funnel analysis, retention cohorts, and revenue attribution. Firebase, Google's mobile platform, provides the most widely adopted analytics SDK (Google Analytics for Firebase). It offers automatic event tracking (first open, in-app purchases, session start/end) alongside custom events, user properties, audience definitions, and integration with Google Ads, BigQuery, and other Firebase services.

Core Metrics

Track these metrics from day one. DAU/MAU (Daily/Monthly Active Users): Engagement scale. Retention Rate: Percentage of users who return after day 1, day 7, and day 30. The industry benchmark for day 1 retention is 30-40%; day 30 retention is 10-15%. Session Length: How long users spend per session. Screen Flow: The path users take through your app. Conversion Rate: Percentage of users who complete a goal (purchase, signup, share). Crash-Free Rate: Percentage of sessions without a crash. Target 99.9%+. LTV (Lifetime Value): Total revenue expected from a user over their lifetime.

Firebase Analytics

Firebase is the dominant analytics platform for mobile apps. It logs up to 500 distinct event types with 25 user properties per app. Key features include: Automatic events: first_open, app_remove, session_start, in_app_purchase, and more. Custom events: Log your own events with up to 100 parameters. Audiences: Define user segments based on events and properties, then target them with Firebase Remote Config, Cloud Messaging, or Google Ads. BigQuery integration: Export raw event data for custom analysis and machine learning. Real-time dashboard: Monitor active users, events, and crashes in real time.

Crash Reporting

Crash reporting is part of mobile analytics. Firebase Crashlytics is the most widely used crash reporter. It provides real-time crash alerts, stack traces with source map mapping, breadcrumb logging for tracking user actions before crashes, and analytics integration (see crash-affected user segments). However you implement it, crash reporting must be in your app before your first beta test. Shipping without crash reporting means flying blind.

In code

// Firebase Analytics: Logging a custom event (Kotlin)
firebaseAnalytics.logEvent("purchase_completed") {
    param("product_id", "prod_12345")
    param("product_name", "Premium Subscription")
    param("value", 9.99)
    param("currency", "USD")
    param("quantity", 1)
}

// Firebase Analytics: Logging a custom event (Swift)
Analytics.logEvent("purchase_completed", parameters: [
    "product_id": "prod_12345" as NSString,
    "product_name": "Premium Subscription" as NSString,
    "value": 9.99 as NSNumber,
    "currency": "USD" as NSString
])

Common questions

Q: Do I need Firebase Analytics if I already use Google Analytics for my website?

A: Google Analytics for Firebase is the mobile-native version. While they share a Google Analytics 4 property, the Firebase SDK provides mobile-specific features like automatic event tracking, offline event buffering, and seamless integration with Firebase services.

Q: Is mobile analytics different from web analytics?

A: Yes. Mobile analytics adds app install attribution, session management across app opens/closes, offline event handling, and engagement metrics unique to mobile (push notification interaction, in-app purchase tracking, screen flows).

Key takeaways:

• Track DAU/MAU, retention (D1, D7, D30), conversion rate, and crash-free rate from day one.

• Firebase Analytics is the industry standard with automatic event tracking and BigQuery export.

• Crashlytics provides real-time crash reporting with breadcrumb context.

• Custom events and user properties power audience segmentation for marketing and personalization.

• Analytics must be integrated before beta testing. You cannot retroactively capture first-session data.