Reports

[GA4] Firebase overview report

When you connect your app to Firebase through the Google Analytics for Firebase SDK, the Firebase overview report appears in your left navigation under the App developer collection in Google Analytics. The same report also appears in your Firebase console when you click "Dashboard" on the left.

The report is a pre-made overview report that summarizes important data about your connected mobile apps to help you monitor engagement, see how much revenue you're generating, and evaluate the success of your app releases.

View the report

  1. From the left menu, select Reports Reports.
  2. On the left, click Firebase in the App developer collection. The App developer collection is only available if you've successfully connected your app to Firebase.

Pre-made summary cards

The Firebase overview report includes the following summary cards by default. Administrators and editors can change the cards so you may see different ones from these.

User activity over time

User activity over time shows the number of people who used your app in the past 30 days, 7 days, and 1 day. You can use the card to see changes in activity over a shorter timeframe compared to changes over a broader timeframe. The card includes only users who engaged with your app in the device foreground.

For example, in the following chart, you would have 72K users in the past 30 days and 3.5K users in the past 1 day. If the number of users in the past 1 day were to begin to trend downwards, you could expect to see fewer users over the past 7 and 30 days in the near future.

Users in last 30 minutes

Users in last 30 minutes shows activity as it happens using data from the Realtime report. The first half of the card shows the total number of users in the last 30 minutes and the number of users in the last 30 minutes per minute.

The second half of the card includes realtime activity for a relevant dimension. For example, the Engagement overview report may show the top pages and screens users are visiting right now, while the User attributes overview report may show the top countries users are visiting from right now.

Users by App version

Users by App version shows the number of users who engage with each version of your app, including the top 5 most interacted with apps in the specified date range. You can click "View app versions" to open the Tech details report to learn more about each app version.

Latest app release overview

Latest app release overview shows the status of the latest release of each version (e.g., Android, iOS) of your app. You can select a version to open the following dashboard, where you can see insights about the app. Learn more about the report

App stability overview

App stability overview shows the percentage of users who experience crash-free sessions for each app and the change over the previous time range.

Exceptions logged on Android using Firebase Crash Reporting’s report API are counted as crashes. Update to Firebase Crashlytics to get improved accuracy in crash reporting.

Average engagement time

Average engagement time shows the average time that your website was in focus in a user's browser or a mobile app was in the foreground on a user's device. Google Analytics uses the following formula to calculate the average engagement time:
Average engagement time = (The total length of time your website was in focus or your app was in the foreground across all sessions) / (The total number of active users)
Average engagement time is calculated automatically using data from the web pages and app screens that are set up with Google Analytics.
How to interpret the chart
The average engagement time in the tab may be greater than the individual average engagement times in the chart.
This is because the average engagement time in the tab shows the sum of engagement time per user divided by the number of users in the entire time period. Each point in the chart shows the engagement time per user divided by the number of users for that day.
Example
Two users visited your website in July.
  • On July 2, user #1 visited for 3 minutes.
  • On July 3, user #2 visited for 4 minutes.
  • On July 4, user #1 visited for 5 minutes and user #2 visited for 6 minutes.

In this example, the average engagement time in the tab would be 9m 00s because user #1 visited for a total of 8 minutes and user #2 visited for a total of 10 minutes in July. The average of those two engagement times would be 9 minutes.

The average engagement time in the chart would look like the following:

  • July 2: 3m 00s
  • July 3: 4m 00s
  • July 4: 5m 30s
In this example, the average engagement time in the tab would be greater than the average engagement time each day.

Engaged sessions per user

Engaged sessions per user shows the number of sessions that were engaged per user. An engaged session is any sessions that lasted 10 seconds or longer, or had 1 or more conversion events or 2 or more page or screen views. Google Analytics uses the following formula to calculate the engaged sessions per user:
Engaged sessions per user = (The number of sessions that lasted 10 seconds or longer, or had 1 or more conversion events or 2 or more page or screen views) / (The total number of users)
Engaged sessions per user is calculated automatically using data from the web pages and app screens that are set up with Google Analytics.
How to interpret the chart
The engaged sessions per user in the tab may be greater than the individual engaged sessions per user in the chart.
This is because the engaged sessions per user in the tab shows the sum of engaged sessions per user divided by the number of users in the entire time period. Each point in the chart shows the engaged sessions per user divided by the number of users for that day.
Example
Two users visited your website in July.
  • On July 2, user #1 has 1 engaged session.
  • On July 3, user #2 has 2 engaged sessions.
  • On July 4, user #1 has 3 engaged sessions and user #2 has 2 engaged sessions.

In this example, the engaged sessions per user in the tab would be 4 because user #1 visited for a total of 4 engaged sessions and user #2 visited for a total of 4 engaged sessions in July. The average of those two engagement times would be 4 engaged sessions.

The engaged sessions per user in the chart would look like the following:

  • July 2: 1 engaged session
  • July 3: 2 engaged sessions
  • July 4: 2.5 engaged sessions
In this example, the engaged sessions per user in the tab would be greater than the engaged sessions per user each day.

Average engagement time per session

Average engagement time per session shows the time spent engaged with your website or app per session. Google Analytics uses the following formula to calculate the average engagement time per session:
Average engagement time per session = (The average time that your website was in focus in a user's browser or an app was in the foreground of a user's device) / (The total number of sessions)
Average engagement time per session is calculated automatically using data from the web pages and app screens that are set up with Google Analytics.
How to interpret the chart
The average engagement time per session in the tab may be greater than the individual average engagement time per session in the chart.
This is because the average engagement time per session in the tab shows the sum of engaged sessions per session divided by the number of sessions in the entire time period. Each point in the chart shows the average engagement time per session divided by the number of sessions for that day.
Example
Two users visited your website in July.
  • On July 2, user #1 has one engaged session of 3 minutes.
  • On July 3, user #2 has two engaged sessions of 3.5 minutes and 4.5 minutes.
  • On July 4, user #1 has one engaged session of 4 minutes and user #2 has one engaged session of 6 minutes.

In this example, the average engagement time per session in the tab would be 10m 30s because user #1 had a total of 7 minutes of engagement time and user #2 had a total of 14 minutes of engagement time in July. The average of those two engagement times would be 10.5 minutes of engagement time.

The average engagement time per session in the chart would look like the following:

  • July 2: 3 minutes of engagement time
  • July 3: 4 minutes of engagement time
  • July 4: 5 minutes of engagement time
In this example, the engaged sessions per user in the tab would be greater than the engaged sessions per user each day.

User retention

User retention shows the percentage of users who return each day in their first 42 days. The chart starts with 100% user retention when all users visit for the first time. It decreases from the first day as users drop off.

User activity by cohort

User activity by cohort shows whether users you acquire on one date return at a greater rate than users you acquire on another date. Each row represents a cohort. The bottom row represents the most recent cohort, while the top row represents the earliest cohort. Darker shading indicates that a higher percentage of users in the cohort returned. The shading becomes lighter as fewer users return. The chart includes a link to the Retention overview report.

Views by Page title and screen class

Views by Page title and screen class shows the number of times users viewed each page or screen in the specified time frame, sorted by the most frequently viewed pages and screens.

For example, in the following table, the Home and Shopping Cart pages were the most frequently viewed pages. You could click "View pages and screens" to open the Pages and screens report.

Event count by Event name

Event count by Event name shows the number of times users triggered each event in the specified time frame, sorted by the most frequently triggered event.

For example, in the following table, the screen_view and user_engagement events were the most frequently triggered events. You could click any event in the table (e.g., "screen_view") to open a report about the event, or you could click "View events" to open the Events report.

Conversions by Event name

Conversions by Event name shows the number of times users trigger each conversion event. While Analytics automatically collects some events as conversions, you can mark any event as a conversion event.

Total revenue

Total revenue shows the total amount of revenue generated from ecommerce purchases, in-app purchases, subscriptions, and advertisements, minus any refunds given.
The Total revenue tab shows the total revenue made during the time period. The chart plots the total revenue per day. For example, if your total revenue on July 2 was $153.98 and on July 3 was $739.28, the tab would show $893.26.

Purchase revenue

Purchase revenue shows the total amount of revenue generated from ecommerce and in-app purchases.
The Purchase revenue tab shows the purchase revenue made during the time period. The chart plots the purchase revenue per day. For example, if your purchase revenue on July 2 was $39.15 and on July 3 was $91.35, the tab would show $130.50.

Total ad revenue

Total ad revenue shows the sum of the advertising revenue from your users in your mobile app. Total ad revenue comes from Google AdMob, Google Ad Manager, or the ad_impression event when the data comes from a third-party integration.
The Total ad revenue tab shows the total ad revenue made during the time period. The chart plots the total ad revenue per day. For example, if your total ad revenue on July 2 was $7.25 and on July 3 was $1.45, the tab would show $8.70.

Average purchase revenue per user

Average purchase revenue per user shows the purchase revenue from in-app purchases (i.e., when the in_app_purchase event is triggered) and purchases (i.e., when the purchase event is triggered) divided by the number of users.

Publisher ad impressions by Ad unit

Publisher ad impressions by Ad unit shows the number of ad impressions per ad unit in the specified date range and the percentage change from the previous date range. You can click "View publisher ads" to open the Publisher ads report.

Users by Country

Users by Country shows the countries from which users are accessing your app, sorted by the countries with the most users. The card includes a map of the world where darker shades of blue represent more users from the country.

You can hover over a country to see the number of users from that country, or you can click "View countries" to open the Demographic details report to learn more about users from each country.

Users by Device model

Users by Device model shows the device models from which users are accessing your app, sorted by the device models with the most users. You can click "View device models" to open the Tech details report to learn more about users who use each device model.

Was this helpful?

How can we improve it?
true
Search
Clear search
Close search
Google apps
Main menu
4336792647783946903
true
Search Help Center
true
true
true
true
true
69256