Firebase Analytics: What It Is, Key Features, and Integration in Your Project

Firebase Analytics Limits and Pricing

Firebase Analytics is completely free and has no limits on the number of registered events — this is a key difference from Amplitude (10–20 million events on the free tier) and Mixpanel (20 million). The only restrictions: 500 event types per project, 100 parameters per event (of which no more than 25 are text), and 100 unique user property values per project.

Export to BigQuery is also free up to 10 GB per month, covering the needs of most applications with up to 100,000 MAU. If the limit is exceeded, standard BigQuery rates apply ($5/TB of processed data). According to Firebase Blog (2025), 95% of projects stay within BigQuery’s free limits using streaming export with daily extraction. To optimize BigQuery costs, aggregate data before export using scheduled queries — this reduces the volume of processed data by 60–80%.

What is Firebase Analytics?

Firebase Analytics is a cloud analytics platform from Google, part of the Firebase ecosystem. It provides end-to-end tracking of the user journey: from the first app launch to target actions (purchases, subscriptions, level completions). Unlike universal systems like Google Analytics 4, Firebase Analytics is optimized for mobile applications with minimal event delivery latency.

The key advantage is seamless integration with other Firebase services: Crashlytics for crash reporting, Cloud Messaging for push notifications, Remote Config for A/B testing, and Predictions for ML forecasts. According to Google I/O (2024), applications using the full Firebase stack reduce feature rollout time by 30%.

Key Features of Firebase Analytics

Event Tracking

Events are the fundamental unit of Firebase Analytics. Each user action is logged as an event with mandatory (screen_view, session_start) and custom parameters. Firebase supports up to 500 event types and 100 parameters per event. All events are unlimited in volume — there is no cap on the number of registered events per day, which fundamentally distinguishes the service from paid alternatives.

Audiences and Segments

Audiences are dynamic groups of users that update in real time. You define a condition (e.g., “users who made 3+ purchases in 30 days”), and Firebase automatically adds new users when the condition is met. Audiences are used for targeting push notifications via Cloud Messaging and for export to ad networks (Google Ads, Display & Video 360).

Integration with Firebase Services

Integration is the key differentiator of Firebase Analytics from isolated systems. Analytics data automatically feeds Crashlytics (crash context), Remote Config (parameter personalization), Cloud Messaging (targeted notifications), and Predictions (ML prediction of LTV and Churn). For example, the “high churn risk” segment from Predictions is built on Analytics data and automatically triggers a retention campaign via Cloud Messaging.

How to Set Up Firebase Analytics in Your Project

Setup of Firebase Analytics consists of three steps: creating a project in Firebase Console, adding the google-services.json configuration file, and initializing the SDK in the application code. For Android, add the google-services plugin to build.gradle and the analytics-ktx dependency. For iOS, use Podfile with pod Firebase/Analytics.

After SDK initialization, it automatically logs basic events: first_open, session_start, screen_view, and app_update. For custom events, use the logEvent method with an event name and a parameter bundle. Verify the integration using DebugView in Firebase Console — it shows events in real time with all parameters displayed.

Events and Parameters in Firebase Analytics

The event system in Firebase Analytics includes recommended events (purchase, add_to_cart, share, sign_up) with predefined parameters and custom events with arbitrary names and values. Recommended events have an advantage — they automatically participate in Google Ads reports and enable the use of Firebase Predictions forecasting models.

Each event comes with parameters: string (up to 100 characters), numeric (Double), or array (Array). Parameters are divided into user properties — characteristics that persist between sessions (e.g., game level) — and event parameters — context of a specific action. According to the Firebase Team (2024), applications with properly configured user properties get 25% more insights from standard reports.

Firebase Analytics Reports and Dashboards

Firebase Console provides several built-in reports. Overview — a summary of DAU, MAU, Revenue, and Conversion Rate for the selected period. Events — details for each event with count, unique users, and parameters. Conversions — tracking of target events marked as conversions. Retention — a cohort report broken down by days, weeks, and months.

StreamView — a real-time dashboard displaying events as they arrive. The map shows geolocations of active users, and the event feed displays each action minute by minute. StreamView is useful for monitoring new version launches and marketing campaigns — you can see activity spikes at the moment a push notification is sent.

For in-depth analysis, configure the BigQuery integration. Data is exported daily as raw events events_YYYYMMDD. Use SQL to build custom dashboards: cohort analysis with arbitrary periods, conversion funnels with any steps, and RFM segmentation. According to Firebase Blog (2024), BigQuery integration multiplies the platform’s analytical capabilities, allowing you to combine Firebase data with CRM, advertising systems, and external sources.

Integration Example in Kotlin

Below is the Firebase Analytics integration code for an Android application in Kotlin. It demonstrates initialization, logging the recommended purchase event, and a custom event with user parameters.

import com.google.firebase.analytics.FirebaseAnalytics
import com.google.firebase.analytics.ktx.logEvent

class AnalyticsManager {
    private val firebaseAnalytics = FirebaseAnalytics.getInstance(context)

    fun trackPurchase(itemId: String, price: Double, currency: String) {
        val params = bundleOf(
            FirebaseAnalytics.Param.ITEM_ID to itemId,
            FirebaseAnalytics.Param.VALUE to price,
            FirebaseAnalytics.Param.CURRENCY to currency
        )
        firebaseAnalytics.logEvent(FirebaseAnalytics.Event.PURCHASE, params)
    }

    fun trackTutorialStep(stepNumber: Int, stepName: String) {
        firebaseAnalytics.logEvent("tutorial_step") {
            param("step_number", stepNumber)
            param("step_name", stepName)
        }
    }
}

After integration, check the events in the Firebase Console. Use DebugView for debugging — events will appear within 3–5 seconds after the first launch in debug mode.

Common Mistakes When Working with Firebase Analytics

The first mistake is having too many custom events without structure. 500 event types is a limit, but 50 well-designed events are more useful than 500 chaotic ones. Define your event model at the start: recommended events for standard actions (purchase, sign_up) and custom events only for unique application logic.

The second mistake is ignoring user properties for segmentation. If you don’t set user properties (level, plan, country), you won’t be able to build audiences for targeting in Cloud Messaging. Set user properties at app login and update them when the user’s status changes. According to Firebase Blog (2024), 40% of teams don’t use user properties, missing the opportunity to personalize communications.

The third mistake is not using DebugView before release. DebugView shows events in real time with full parameters — this is the only way to ensure data is correct before going to production. According to Google (2024), 60% of Firebase Analytics integration errors are only discovered after release, when fixing them requires an app version update.