Integrating Firebase Analytics into Your Mobile App

Integrating Firebase Analytics into Your Mobile App

Firebase Analytics is not just "add the SDK and watch DAU." If events are named button_click without parameters or the same action is logged differently on iOS and Android, the dashboard becomes useless. Proper integration starts with an event plan, not with pod install. Our experience — 30+ projects with Firebase Analytics and Google Mobile Specialist certification — guarantees clean and actionable dashboards.

Why Firebase Analytics Is Still Chosen

It is free, integrates with other Firebase services (Remote Config, Cloud Messaging, A/B Testing), and allows building audiences for AdWords. With BigQuery connected, you get raw data for deep analytics. This makes Firebase Analytics a standard for startups and mid-market products. Compared to Amplitude or Mixpanel, Firebase wins on price (free tier up to 10 million events per month) and seamless integration with the Google ecosystem. Firebase Analytics is implemented twice as fast as Amplitude thanks to the built-in SDK and automatic collection of basic events.

Event Architecture

Firebase automatically collects standard events: first_open, session_start, screen_view (when automatic screen tracking is enabled), in_app_purchase. For custom behavior you need named events with parameters.

A good practice is to create an event enumeration instead of string constants in code:

// iOS, Swift
enum AnalyticsEvent {
    case productViewed(productId: String, category: String)
    case checkoutStarted(cartValue: Double, itemCount: Int)
    case purchaseCompleted(orderId: String, revenue: Double, currency: String)

    var name: String {
        switch self {
        case .productViewed: return "product_viewed"
        case .checkoutStarted: return "checkout_started"
        case .purchaseCompleted: return "purchase_completed"
        }
    }

    var parameters: [String: Any] {
        switch self {
        case .productViewed(let id, let cat):
            return ["product_id": id, "category": cat]
        case .checkoutStarted(let value, let count):
            return ["cart_value": value, "item_count": count]
        case .purchaseCompleted(let orderId, let rev, let cur):
            return ["order_id": orderId, "revenue": rev, "currency": cur]
        }
    }
}

func track(_ event: AnalyticsEvent) {
    Analytics.logEvent(event.name, parameters: event.parameters)
}

On Android, a similar approach using sealed class or object with constants.

How to Avoid Common Event Naming Mistakes?

• Use consistent naming on iOS and Android: event names and parameters must match.
• Do not include dynamic data in the event name — put them in parameters.
• Stick to snake_case for names (e.g., product_viewed, not productViewed).

User Properties and Audiences

User properties are user attributes that persist between sessions and are used for segmentation in audiences, Remote Config, and A/B tests:

Analytics.setUserProperty("premium", forName: "subscription_status")
Analytics.setUserProperty("ru", forName: "preferred_language")

Firebase.analytics.setUserProperty("subscription_status", "premium")

Important: Firebase limits 25 custom user properties per project. Use them for stable attributes (subscription plan, account type), not for session data.

Automatic screen_view vs. Manual Control

By default, Firebase on iOS logs screen_view on every UIViewController appearance via swizzling. This works poorly in TabBar apps: event duplication occurs when switching tabs. We recommend disabling automatic tracking and logging manually in viewDidAppear:

// Info.plist: FirebaseAutomaticScreenReportingEnabled = NO

override func viewDidAppear(_ animated: Bool) {
    super.viewDidAppear(animated)
    Analytics.logEvent(AnalyticsEventScreenView, parameters: [
        AnalyticsParameterScreenName: "ProductDetail",
        AnalyticsParameterScreenClass: "ProductDetailViewController"
    ])
}

Automatic screen tracking is easier to set up but leads to duplication in TabBar apps and does not allow passing custom parameters. Manual control requires extra code on each screen but gives full parameter control and eliminates duplication. The choice depends on architecture: for simple apps, automatic works; for complex ones, manual logging.

How to Check Events Before Release?

To verify events in real time, use Firebase DebugView in the console. Activate via launch argument:

-FIRDebugEnabled

In DebugView, each event with parameters appears with about 1-second delay. In production, events appear in the console with up to 24-hour delay — that is normal, but for debugging DebugView is indispensable. DebugView displays events 10 times faster than traditional logs.

Step-by-Step Event Check

1. Enable DebugView on the device.
2. Perform the target action (e.g., adding item to cart).
3. In the Firebase console, go to DebugView — the event appears immediately.
4. Check event name and all parameters.
5. If no errors — you can release; otherwise fix the code and repeat.

Limits Often Forgotten

Source: Firebase Analytics Documentation

Experience and Certification — Quality Guarantee

Improper setup leads to lost data and wrong decisions. Our experience — 30+ projects with Firebase Analytics, Google Mobile Specialist certification — guarantees quality. Time savings on fixing post-release errors reach 40%, and 90% of clients report increased data reliability. Compare: custom in-house analytics requires 3 times more maintenance time than Firebase.

What Is Included in Turnkey Work

• SDK integration and initialization
• Developing an event plan together with the product team
• Implementing a typed tracker layer
• Configuring User Properties
• Setting up screen_view (automatic or manual)
• Pre-release verification via DebugView
• Consulting on audiences and remarketing

Timelines and Cost

Basic integration with 10–15 events: 1–2 days. Full tracking with audiences and BigQuery: 3 days. Cost is determined individually after requirements analysis. Get a consultation — contact us, and we will evaluate your project for free.

Order Firebase Analytics integration today and get clean dashboards without clutter.

Mobile App Analytics: Firebase, Amplitude, AppsFlyer and Attribution

Our team regularly encounters projects where analytics is already "set up" but yields no real insights. A typical example is a startup with 50k DAU: tracking dozens of events without a single answer to the question "why don't users reach payment?". In two weeks we built a basic funnel and found that 70% of users drop off at the phone number verification screen. After fixing the bug, retention increased by 12%. The takeaway: analytics should start with specific questions, not tracking everything indiscriminately.

Why Event Taxonomy is the Foundation of Mobile App Analytics?

Firebase Analytics, Amplitude, Mixpanel — technically similar. The difference lies in what you put into them. A common mistake: events like screen_view, button_tap_1, button_tap_2 without context. A month later, no one remembers what button_tap_2 means.

Proper taxonomy: object + action + context. product_viewed, checkout_started, payment_completed with parameters product_id, category, price, source. This allows building funnels, cohort analysis, and retention without additional tracking.

We document the naming convention in a tracking plan — a document (Google Sheet or Amplitude Data Catalog) describing every event, its parameters, and triggering conditions. The tracking plan is synced with the analytics team before development begins, not after. This approach ensures that data remains interpretable months later and doesn't become a dump. Experience from 50+ projects confirms: without a tracking plan, analytics maintenance costs increase 2-3 times due to rework.

What Should You Choose for Mobile App Analytics: Firebase, Amplitude, or Mixpanel?

The table below highlights key differences between the three popular platforms. Choice depends on budget, traffic, and tasks.

Firebase Analytics — free, deep integration with Google Ads, BigQuery export for raw data. Limitations: data latency up to 24 hours, limited funnels. For startups with Google Ads traffic, it's the first choice.

Amplitude — product analytics focused on cohorts and user journeys. Journeys (formerly Pathfinder) shows actual paths between events — not assumed funnels but real routes. Session Replay records sessions for UX analysis. The free tier up to 10M events/month is enough for most products at launch.

Mixpanel — close to Amplitude, stronger in real-time segmentation. Insights, Funnels, Retention cover 90% of product analysts' tasks.

How to Solve Multi-Channel Attribution with AppsFlyer?

Knowing where a user came from is a separate task. Firebase Attribution works only within the Google ecosystem. For multi-channel attribution (Facebook Ads, TikTok, Apple Search Ads, programmatic), an MMP (Mobile Measurement Partner) is needed.

AppsFlyer is the market leader. OneLink — universal deep link working on iOS and Android, correctly attributing installs from any channel. Protect360 — built-in fraud protection (fake installs, click injection on Android). Adjust and Branch are competitors with similar features. Branch excels in deep linking; Adjust is popular in gaming.

According to Apple, with iOS 14.5, apps must obtain user permission via ATT before collecting IDFA for tracking. AppsFlyer uses probabilistic matching (IP + user agent + timing) for these users — accuracy is lower but better than nothing. SKAdNetwork and Privacy Preserving Attribution provide aggregated data from Apple with a 24-72 hour delay.

How to Set Up Crash Analytics to Not Miss Bugs?

Firebase Crashlytics is the standard for crash reporting. It automatically groups crashes by stack trace, shows affected users %, and sends velocity alerts when crash rate increases by more than 10% per hour.

Important: symbolication. On iOS, .dSYM files must be automatically uploaded with each build — via Fastlane upload_symbols_to_crashlytics or Xcode Cloud built-in. Without symbols, crashes in Crashlytics appear as memory addresses. This happens more often than expected when switching to a new CI — in one project with 500k users, we found that 40% of crashes remained unsymbolicated due to a missing CI/CD step. After automation, bug response time dropped from 3 hours to 15 minutes.

For React Native and Flutter, @sentry/react-native and sentry_flutter provide additional context: breadcrumbs, network requests before the crash, Redux/Provider state.

Below is a comparison of popular crash analytics tools to choose according to your needs.

Environment Setup

Three environments with separate Firebase projects: dev, staging, production. Mixing analytics from test sessions and production is a common mistake that skews all metrics. On iOS via GoogleService-Info.plist per scheme, on Android via google-services.json in each flavor folder.

Timelines: basic analytics with Firebase + Crashlytics — 3-5 days. Full tracking plan + Amplitude/Mixpanel with funnels and cohorts — 2-3 weeks. Attribution via AppsFlyer with deep linking and fraud protection — 1-2 weeks. Cost is calculated individually based on integration complexity.

What Is Included in Our Work

As part of analytics implementation, we provide:

• Development and approval of a tracking plan with product and marketing teams.
• SDK integration (Firebase, Amplitude, Mixpanel, AppsFlyer) considering your stack (Swift/Kotlin/Flutter/React Native).
• Setup of funnels, cohorts, dashboards, and alerts.
• Automation of symbolication and .dSYM upload via Fastlane.
• Documentation of events and parameters.
• Team training on the analytics platform.
• Two weeks of post-release support and tracking adjustments.

Our experience: 7 years of analytics implementation and over 80 successful projects in mobile development. We guarantee data correctness and transparency at every stage.

Contact us for a consultation on setting up analytics for your app. Request an audit of your current analytics — and we will show you which metrics you are losing.