Google Analytics integration in Firebase - Commands & Configuration

Introduction

Google Analytics integration helps you track how users interact with your app. It solves the problem of understanding user behavior to improve your app's experience.

When you want to see how many people open your app each day.

When you want to know which features users like the most.

When you want to track if users complete important actions like signing up.

When you want to measure the success of marketing campaigns driving users to your app.

When you want to find and fix problems by seeing where users drop off.

Config File - firebase.json

firebase.json

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

This file configures Firebase Hosting for your app. The hosting section sets up your app's public files and routing. Google Analytics is enabled via the Firebase console and SDK, not directly in this config file.

Commands

This command initializes Google Analytics in your Firebase project, setting up necessary files and linking your app to Analytics.

Terminal

firebase init analytics

Expected Output

=== Initializing Google Analytics in your Firebase project

✔ Google Analytics has been enabled for your project.

✔ Analytics configuration files have been created.

This command deploys your app to Firebase Hosting with Google Analytics enabled, making tracking active for your live app.

Terminal

firebase deploy --only hosting

Expected Output

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

✔  hosting[your-project-id]: Successful upload of public directory files.

✔  hosting[your-project-id]: Release complete.

→

--only hosting - Deploy only the hosting part without affecting other Firebase services.

This command enables debug mode for Google Analytics to test and verify events during development.

Terminal

firebase analytics:debug --app your-app-id

Expected Output

Debug mode enabled for app your-app-id. Analytics events will be logged in the console.

Key Concept

If you remember nothing else from this pattern, remember: enabling Google Analytics in Firebase lets you see real user actions to improve your app.

Common Mistakes

Not enabling Analytics in the Firebase console before running commands.

Without enabling Analytics in the console, tracking won't start even if you deploy the app.

Go to the Firebase console, select your project, and enable Google Analytics before initializing it locally.

Forgetting to deploy hosting after enabling Analytics.

Changes in configuration only take effect after deployment, so no data will be collected if not deployed.

Always run 'firebase deploy --only hosting' after changing Analytics settings.

Not using debug mode during development to verify events.

Without debug mode, you can't see if Analytics events are sent correctly, making troubleshooting hard.

Use 'firebase analytics:debug' to test events before going live.

Summary

Run 'firebase init analytics' to set up Google Analytics in your Firebase project.

Deploy your app with 'firebase deploy --only hosting' to activate Analytics tracking.

Use 'firebase analytics:debug' to test and verify Analytics events during development.

Practice

1. What is the main purpose of integrating Google Analytics with Firebase?

easy

A. To host static website files

B. To track user behavior and app usage data

C. To store user passwords securely

D. To send emails to users automatically

Solution

1. Step 1: Understand Google Analytics role

   Google Analytics collects data about how users interact with your app or website.

2. Step 2: Match with Firebase integration purpose

   Firebase uses Google Analytics to provide insights on user behavior and app performance.

3. Final Answer:

   To track user behavior and app usage data -> Option B

4. Quick Check:

   Analytics tracks user behavior = C [OK]

Hint: Analytics means tracking user actions and app usage [OK]

Common Mistakes:

• Confusing analytics with security or hosting
• Thinking analytics sends emails
• Assuming analytics stores passwords

2. Which Firebase CLI command initializes Google Analytics integration in your project?

easy

A. firebase deploy analytics

B. firebase start analytics

C. firebase init analytics

D. firebase enable analytics

Solution

1. Step 1: Recall Firebase CLI commands

   The command to start setup for analytics is 'firebase init analytics'.

2. Step 2: Differentiate from deploy and other commands

   'firebase deploy' applies changes, but does not initialize. 'start' and 'enable' are not valid commands for this.

3. Final Answer:

   firebase init analytics -> Option C

4. Quick Check:

   Initialization uses 'init' command = B [OK]

Hint: Init means start setup; deploy means apply changes [OK]

Common Mistakes:

• Using deploy instead of init to start analytics
• Assuming 'start' or 'enable' commands exist
• Confusing initialization with deployment

3. Given this Firebase Analytics setup snippet, what will be the output in the Firebase console?

firebase init analytics
firebase deploy

medium

A. Google Analytics will be enabled and data collection starts

B. An error will occur because deploy must come before init

C. No changes happen until you manually enable analytics in console

D. The app will crash due to missing configuration

Solution

1. Step 1: Understand command order

   'firebase init analytics' sets up analytics configuration, then 'firebase deploy' applies it.

2. Step 2: Effect on Firebase console

   After deploy, Google Analytics is enabled and starts collecting data visible in the console.

3. Final Answer:

   Google Analytics will be enabled and data collection starts -> Option A

4. Quick Check:

   Init then deploy enables analytics = D [OK]

Hint: Init first, then deploy to enable analytics [OK]

Common Mistakes:

• Thinking deploy must come before init
• Believing manual console enable is required after deploy
• Assuming app crashes without extra config

4. You ran firebase init analytics but forgot to run firebase deploy. What issue will you face?

medium

A. Analytics setup changes won't apply, no data collected

B. Firebase will automatically deploy changes after init

C. Your app will show errors on startup

D. Analytics will collect data but not show in console

Solution

1. Step 1: Understand init vs deploy roles

   'firebase init analytics' prepares config files locally but does not apply them to Firebase project.

2. Step 2: Effect of missing deploy

   Without 'firebase deploy', changes are not sent to Firebase servers, so analytics is not enabled and no data is collected.

3. Final Answer:

   Analytics setup changes won't apply, no data collected -> Option A

4. Quick Check:

   Deploy applies changes; missing deploy means no effect [OK]

Hint: Init prepares; deploy applies changes to Firebase [OK]

Common Mistakes:

• Assuming init auto-deploys changes
• Expecting app errors without deploy
• Thinking data collects without deploy

5. You want to track a custom event named purchase_complete in your Firebase app using Google Analytics. Which step is necessary after enabling Analytics with firebase init analytics and firebase deploy?

hard

A. No extra step needed; all events are tracked automatically

B. Manually add purchase_complete in Firebase console event list

C. Restart Firebase project to activate custom events

D. Add code in your app to log the purchase_complete event

Solution

1. Step 1: Recognize default vs custom events

   Firebase Analytics tracks some default events automatically, but custom events require explicit logging in app code.

2. Step 2: Implement custom event logging

   You must add code in your app to log the 'purchase_complete' event so Firebase can record it.

3. Final Answer:

   Add code in your app to log the purchase_complete event -> Option D

4. Quick Check:

   Custom events need app code logging = A [OK]

Hint: Custom events require explicit logging in app code [OK]

Common Mistakes:

• Expecting console to add custom events automatically
• Thinking restart activates events
• Assuming all events tracked without code