How to Use Analytics Features to Track Your FlutterFlow App Performance

In FlutterFlow, open Settings (gear icon, top-left) > Firebase > Firebase Config. Confirm your google-services.json (Android) and GoogleService-Info.plist (iOS) are connected — these files contain your Firebase project credentials including the Analytics measurement ID. Next, go to Settings > App Details and enable the Firebase Analytics toggle if present. In most FlutterFlow projects Firebase Analytics is included automatically once Firebase is connected. To verify it is working, run your app on a real device or Android emulator, navigate between pages, then open Firebase console > Analytics > DebugView. Within 30 seconds you should see events appearing in real time with the device listed in the debug devices panel. Note that Analytics data in the main dashboard has a 24-hour delay — DebugView is the only place to see real-time events.

Before adding any Log Event actions in FlutterFlow, write down the 5-10 most important user actions in your app. These are the moments that indicate value delivery or conversion: completing signup, publishing a post, making a purchase, inviting a friend, reaching a key feature for the first time. Map each to an event name. Use Firebase's recommended event names when they match (e.g., sign_up, purchase, share, tutorial_complete) because they automatically populate pre-built Firebase reports and audience segments. For custom events, use snake_case, keep names under 40 characters, and make them verb-noun pairs (e.g., document_created, export_completed, paywall_viewed). Document your event taxonomy in a shared spreadsheet before implementing — retrofitting event names after launch requires a new app version.

In FlutterFlow, select a widget that represents a key conversion action — for example, a Publish button on a post creation page. Open its Action Flow and add a Log Event action (found under Firebase Analytics). Set the Event Name to your chosen event name (e.g., post_published). Add Event Parameters by clicking the + icon: add parameters like post_type (string, from a page state variable), word_count (integer, from a Custom Function that counts characters), and has_image (boolean). Parameters let you filter and segment events in Firebase. Each event can have up to 25 parameters, each with a name under 40 characters and a value under 100 characters. Repeat this for each event in your taxonomy.

User properties are attributes that describe the user rather than a single event — subscription tier, account type, preferred language, or onboarding cohort. In FlutterFlow, use the Set User Property action (also under Firebase Analytics). Call this action once after sign-in and whenever the property changes: e.g., set plan_type to 'free' after signup, then set it to 'pro' after a successful purchase. In Firebase console > Analytics > Audiences, you can create audience segments filtered by user properties. These audiences sync to Google Ads and Firebase A/B Testing. User properties are capped at 25 per project. Common properties: plan_type, onboarding_completed (true/false), app_language, signup_source.

In Firebase console, open Crashlytics and click Enable Crashlytics for your project. In FlutterFlow, go to Settings > Firebase > enable the Crashlytics toggle (if available), or add firebase_crashlytics to pubspec.yaml in the exported project. Crashlytics auto-captures all uncaught Flutter errors and Dart exceptions. To log non-fatal errors (caught exceptions you still want to track), add a Custom Action that calls FirebaseCrashlytics.instance.recordError(error, stackTrace, fatal: false). In FlutterFlow Action Flows, place this call in the error branch of API calls and database operations. Crashlytics reports appear in Firebase console within minutes of a crash, grouped by issue, showing the exact stack trace and the events that led up to the crash.

Firebase's built-in dashboards cover standard reports, but for custom SQL queries, cohort analysis, or connecting to data warehouses, link BigQuery. In Firebase console > Project Settings > Integrations > BigQuery, click Link. This requires a Google Cloud project (usually the same project as Firebase). Enabling the link starts a daily export of all raw events to BigQuery tables named events_YYYYMMDD. In BigQuery, query total events per day, time-to-conversion funnels, or retention curves using standard SQL. The daily export is free up to 10GB/month. For real-time streaming export (events appear within seconds in BigQuery), enable Streaming Export in the same panel — this has per-row BigQuery streaming insert costs.