Analytics for apps

This help center article is part of the App + Web Property Beta.

App + Web properties are not currently supported in the Analytics app.

Data collection

After you integrate the Firebase SDK with your app, basic app-usage data is collected automatically and is available in Google Analytics. You don't need to add any additional code to enable automatically collected events like first_open, session_start, and in_app_purchase. User properties are also collected automatically.

Your app should log these general events and the events for your app type (e.g., retail and ecommerce, travel, or games). Logging events along with their prescribed parameters ensures maximum available detail in reports and lets you benefit from the latest Firebase features and integrations as they become available. To log events beyond the ones collected automatically, you need to add additional code snippets to your app (iOS) | Android.

Verify data collection

After you've configured your app to collect data, you can use the Real-Time report to verify that your app is actually sending data to Analytics.

Events, conversions, user properties, and audiences

There are four building blocks to app analytics: events, conversions, user properties, and audiences.

  • Events are triggered when users take actions in your app. Several events are captured automatically by the Firebase SDK. However, you need to add code to log the events for your app type. Logging these events along with their prescribed parameters ensures maximum available detail in reports and lets you benefit from the latest features and integrations as they become available.
  • Conversions are the events that matter the most to your business. Think of them as your key performance indicators (KPIs). Marking events as conversions lets you send them to the ad networks you already work with, including Google and external networks.
  • User properties are characteristics of your users. Firebase captures several default user properties. You can also create your own. For example, if you want to track your users' favorite sports teams, create a team preference user property, and filter reports by team preference.
  • Audiences are groups of users defined by a combination of events and user properties. For example, you might want to see metrics for just your users from a specific country.
Was this helpful?
How can we improve it?