Firebase Analytics in Flutter - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

Tracking a Custom Event in Firebase Analytics

You want to track a custom event named purchase_complete with a parameter item_id in your Flutter app using Firebase Analytics. Which code snippet correctly logs this event?

Flutter

final FirebaseAnalytics analytics = FirebaseAnalytics.instance;

// Your code here to log event

A await analytics.logEvent(name: 'purchase_complete', parameters: {'item_id': '12345'});

B analytics.logEvent(name: 'purchaseComplete', params: {'item_id': '12345'});

C await analytics.log('purchase_complete', {'item_id': '12345'});

D analytics.logEvent('purchase_complete', {'item_id': '12345'});

💡 Hint

Check the method name and parameter names carefully. Firebase Analytics expects specific argument names.

The correct method to log an event is logEvent with named parameters 'name' and 'parameters'. Option A uses the correct syntax and awaits the async call. Option A misses named parameters, causing a syntax error. Option A uses a non-existent method 'log'. Option A uses wrong parameter names and event name casing.

❓ lifecycle

intermediate

When to Initialize Firebase Analytics in Flutter

At which point in a Flutter app's lifecycle should you initialize Firebase Analytics to ensure it tracks user events correctly?

A Inside the build() method of the first widget

B Inside the main() function before runApp() is called

C Inside the dispose() method of the root widget

D After the app has been running for 10 seconds

💡 Hint

Think about when Firebase services should be ready before the UI loads.

Firebase Analytics should be initialized early, typically in main() before runApp(), so it can track all events from app start. Initializing in build() or dispose() is too late or inappropriate. Waiting 10 seconds delays tracking important early events.

🔧 Debug

advanced

Debugging Missing Analytics Events in Flutter

You notice that your custom Firebase Analytics events are not appearing in the Firebase console. Which of the following is the most likely cause?

A You forgot to call Firebase.initializeApp() before logging events

B You used await when calling logEvent, which is not allowed

C You logged events with names longer than 100 characters

D You called logEvent inside a StatelessWidget's build method

💡 Hint

Firebase services must be ready before usage.

If Firebase.initializeApp() is not called before logging events, Firebase Analytics won't work properly and events won't be sent. Using await is correct and allowed. Event names longer than 40 characters (not 100) are invalid but less common cause. Logging inside build() is not recommended but does not prevent events from sending.

🧠 Conceptual

advanced

Understanding Firebase Analytics User Properties

Which statement about Firebase Analytics user properties in Flutter is true?

A User properties must be set before Firebase.initializeApp() is called

B User properties are automatically collected and cannot be set manually

C User properties can be set multiple times and are used to segment users in reports

D User properties are only available on iOS devices

💡 Hint

Think about how user properties help analyze user behavior.

User properties are custom attributes you set to describe segments of your user base. They can be set multiple times and help in filtering analytics reports. They are not automatically collected and can be set anytime after initialization. They work on both Android and iOS.

❓ navigation

expert

Tracking Screen Views with Firebase Analytics in Flutter

You want to track screen views in your Flutter app using Firebase Analytics. Which approach correctly sets the current screen name for analytics when navigating between screens?

Flutter

import 'package:firebase_analytics/firebase_analytics.dart';

final FirebaseAnalytics analytics = FirebaseAnalytics.instance;

// Inside your screen widget's lifecycle or navigation callback

A await analytics.setScreenName('HomeScreen');

B analytics.logEvent(name: 'screen_view', parameters: {'screen_name': 'HomeScreen'});

C analytics.setCurrentScreen('HomeScreen');

D await analytics.setCurrentScreen(screenName: 'HomeScreen');

💡 Hint

Check the exact method name and parameter names in the Firebase Analytics Flutter API.

The correct method to set the current screen is setCurrentScreen with a named parameter screenName. Option D uses the correct syntax and awaits the async call. Option D logs a generic event but does not set the screen properly. Options A and C use incorrect method names or syntax causing errors.