Why analytics drive product decisions in Firebase - Why It Works

Introduction

Analytics help you understand how users interact with your app. This information guides you to improve features that users like and fix problems they face. Without analytics, decisions are guesses instead of facts.

When you want to know which app features users use the most to focus development efforts.

When you need to track if a new feature increases user engagement or causes confusion.

When you want to measure how many users complete a purchase or sign-up process.

When you want to find out where users drop off in a multi-step process to improve it.

When you want to test different versions of your app to see which performs better.

Config File - firebase.json

firebase.json

{
  "hosting": {
    "public": "public",
    "ignore": ["firebase.json", "**/.*", "**/node_modules/**"],
    "rewrites": [
      {
        "source": "/**",
        "destination": "/index.html"
      }
    ]
  },
  "firestore": {
    "rules": "firestore.rules",
    "indexes": "firestore.indexes.json"
  },
  "functions": {
    "source": "functions"
  }
}

This file configures Firebase services for your project.

hosting: Defines where your app files are and how to serve them.

firestore: Points to security rules and indexes for your database.

functions: Specifies the folder for backend code that can process analytics events or other logic.

Commands

This command sets up Firebase Analytics in your project, enabling tracking of user behavior.

Terminal

firebase init analytics

Expected Output

=== Project Setup

✔ Firebase Analytics has been enabled for your project.

✔ Analytics SDK added to your app.

Initialization complete.

Deploys the analytics configuration and SDK setup to Firebase so your app can start collecting data.

Terminal

firebase deploy --only analytics

Expected Output

=== Deploying to 'your-project-id'

✔  Deploy complete!

Project Console: https://console.firebase.google.com/project/your-project-id/analytics/app/android:com.example.app

→

--only - Deploy only the specified Firebase service, here analytics.

Lists the analytics events collected from your app to see what user actions are tracked.

Terminal

firebase analytics:events:list

Expected Output

Event Name           Count

app_open             1500

purchase             300

sign_up              450

screen_view          2000

Manually logs a purchase event with details, useful for testing or custom tracking.

Terminal

firebase analytics:events:log --event_name=purchase --param=item=book --param=price=15

Expected Output

Event 'purchase' logged with parameters: item=book, price=15

Key Concept

If you remember nothing else from this pattern, remember: analytics data shows what users really do, so you can make smart product decisions based on facts, not guesses.

Common Mistakes

Not enabling analytics before deploying the app

Without enabling analytics, no user data is collected, so you have no insights.

Always run 'firebase init analytics' before deploying your app to start tracking.

Ignoring event parameters when logging custom events

Missing parameters means losing important details about user actions.

Include all relevant parameters with each event to get full context.

Not verifying events after deployment

You might think events are tracked but they may not be, leading to wrong decisions.

Use 'firebase analytics:events:list' to confirm events are received.

Summary

Initialize Firebase Analytics to start collecting user behavior data.

Deploy analytics configuration to your Firebase project.

Check collected events to understand user actions.

Log custom events with parameters for detailed insights.