Google Analytics for apps: set up GA4 and the metrics to watch
Short answer Google Analytics tracks apps through Firebase. Add an iOS or Android data stream in GA4, and your developer adds the free Firebase SDK, which counts first opens, screens, sessions and in-app purchases on its own. Then watch active users, retention, crash-free users and your key events. For downloads alone, App Store Connect and Play Console need no code.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callWhat Google Analytics for apps is, and what it costs
Google Analytics 4 (GA4) measures apps through Firebase, Google's toolkit for app developers. Your developer adds the Firebase SDK (a code library) to the app, and it sends what people do inside the app to your GA4 property. One property can hold your website, your iPhone app and your Android app, each as its own data stream (Analytics Help: Set up Analytics for a website and/or app).
For a small business it costs nothing:
"Google Analytics is an app measurement solution, available at no charge, that provides insight on app usage and user engagement." (Firebase documentation: Google Analytics)
| Tool | What it does for an app | Price, November 2026 |
|---|---|---|
| GA4 property with the Firebase SDK | Reports on users, screens, events and retention; up to 500 kinds of events | No charge |
| Firebase Crashlytics | Crash reports, also sent into GA4 | No-cost for mobile apps |
| Firebase A/B Testing | Tests two versions of a screen or a message | No-cost; Remote Config, which it runs on, is free up to 100,000 fetch requests a day per project |
| Analytics 360 | Enterprise version with higher limits and longer history | No published price; Google's page says "Talk to Sales" |
Google aims 360 at large companies: it "is tailored for the unique measurement needs of large enterprises" (Google Marketing Platform: Analytics 360). Any 360 price you read elsewhere did not come from Google's page.
Do you need it? Start with the free store reports
For downloads, store visits and crashes, no. Both app stores report those with no code. Apple's app analytics give "information only Apple provides and no technical implementation is required" (Apple Developer Program), included in the US$99 yearly membership you already pay to publish.
| Question | Where to look | Code needed |
|---|---|---|
| How many people downloaded the app? | App Store Connect: Sales and Trends, App Analytics. Play Console: Statistics, Store analysis | No |
| Which sources send people to your App Store page? | App Store Connect: App Analytics | No |
| How often does it crash? | Play Console: Android vitals. Firebase Crashlytics for both platforms | Play: no. Crashlytics: yes |
| Which screens do people use, and do they book or order? | GA4 | Yes, the Firebase SDK |
| Do new users come back in their first weeks? | GA4 retention cards | Yes, the Firebase SDK |
Apple's usage numbers cover only people who agreed to share diagnostics with developers (App Store Connect Help: Overview of reporting tools).
GA4 earns its place when customers book, order or pay inside the app and you want to see where they give up. If a vendor built and runs your app (a branded booking app from your scheduling software, say), you may not be able to add the SDK. Ask the vendor what reports it offers, or whether it can send events to your GA4 property.
Setting up Google Analytics for an app, step by step
These steps follow Google's Analytics Help and Firebase documentation as of November 2026. You can do steps 1 and 2; steps 3 to 6 change the app's code, so your developer does them.
- Create the account and property. Go to analytics.google.com and click Start measuring. Name the account and the property, and pick your time zone, currency, industry and business size.
- Add an app data stream. In Admin, under Data collection and modification, click Data streams, then Add stream, then iOS app or Android app. Enter the iOS bundle ID or Android package name (your developer has it), the app name and, for iOS, the App Store ID. Add a second stream for the other platform. Google says it "creates a corresponding Firebase project and app data stream" for you (Analytics Help: Set up Analytics for a website and/or app).
- Add the SDK. The developer downloads the config file GA4 offers and adds the Firebase SDK for Google Analytics (Swift Package Manager on iPhone, Gradle on Android; Flutter, Unity and C++ also work). Collection starts once the updated app runs.
- On iPhone, decide on the advertising ID. Firebase offers its library with or without IDFA, Apple's advertising identifier, and says audiences and campaign attribution need Apple's AdSupport framework. If you don't advertise the app, ask your developer whether the version without IDFA is enough.
- Test before release. The SDK normally uploads events in batches about once an hour to save battery. Debug mode on a test phone sends them almost at once, so you can watch them arrive in GA4's DebugView. Then add a developer-traffic filter so test taps stay out of your reports.
- Add the events that make you money. Log an event for each action that matters, such as a booking, an order or a sign-up, using Google's recommended event names where one fits. Mark each as a key event, up to 30 per property; GA4 key events for a small business shows how. iPhone apps built with SwiftUI need screen names set in code.
On the advertising ID in step 4, Apple's rule:
"In iOS 14.5, iPadOS 14.5, and tvOS 14.5 or later, you need to receive the user's permission through the App Tracking Transparency (ATT) framework in order to track them or access their device's advertising identifier." (Apple Developer: User privacy and data use)
What GA4 counts in an app without extra code
Once the SDK is in, these events arrive on their own (Analytics Help: Automatically collected events):
| Event | When it fires | Catch |
|---|---|---|
| first_open | First launch after an install or reinstall | Not a download count |
| screen_view | The user moves to a new screen | SwiftUI screens need names set in code |
| user_engagement | The app is in the foreground for at least one second | Feeds engagement time |
| in_app_purchase | A purchase or first subscription through the App Store or Google Play | Payments outside the stores need logging in code; revenue can differ from Play Console |
| app_remove | The app is uninstalled | Android only |
| notification_open | A user opens a push notification | Only notifications sent with Firebase Cloud Messaging |
| app_exception | A crash or error | Only with Crashlytics added |
Downloads and first opens are different numbers:
"This event is not triggered when a user downloads the app onto a device, but instead when he or she first uses it." (Analytics Help: Automatically collected events)
The app metrics to watch in GA4
Open Reports, then Firebase in the App developer collection. The same Firebase overview report is the Dashboard in the Firebase console; Firebase says the app reports in both places are identical (Firebase documentation: Analytics reports).
| Metric | What it tells you | Where |
|---|---|---|
| Active users, last 30, 7 and 1 days | Whether use is growing or fading | Firebase overview: User activity over time |
| User retention | Share of new users who return on each of their first 42 days | Firebase overview: User retention |
| Average engagement time | Time the app was in the foreground, per active user | Firebase overview |
| Crash-free users | Share of daily active users with no crash | Latest releases report |
| App version adoption | How many users run your newest version | Latest releases report |
| Key events | How many users booked, ordered or paid, by the channel that brought them | Key events column in the User acquisition report |
Read crashes per release. The Latest releases report labels a version "Successful" when fewer than 1% of sessions crash and more than 10% of daily active users run it. It flags "Needs investigation" when 1% of sessions crashed today and yesterday, in red at 10% (Analytics Help: Latest releases report). Crash data comes from Crashlytics, so add it with the SDK.
Judge a change by cohort. The User activity by cohort card compares how well groups of new users from different dates come back. Ship a new first screen, then compare users who joined before and after it.
Limits that catch app owners out
- Data retention. You choose 2 or 14 months for user-level data. Google says "The data retention setting only affects explorations and funnel reports" (Analytics Help: Data retention), so standard reports keep their history. Pick 14 months anyway.
- Sampling. Explorations sample once a query passes 10 million events in a standard property, and "Standard queries are not affected by this limit" (Analytics Help: Configuration limits). A small app rarely gets near it.
- Predictions. GA4 can predict likely buyers and likely quitters only once, over a seven-day stretch in the last 28 days, at least 1,000 returning users did the thing and 1,000 didn't (Analytics Help: Predictive metrics). Most small apps never qualify.
- Old tools. Google Optimize ended on September 30, 2023 (Optimize Resource Hub); app tests now run in Firebase A/B Testing. Universal Analytics stopped processing standard properties on July 1, 2023 (Analytics Help: Google Analytics 4 has replaced Universal Analytics).
Privacy: update your store labels
The Firebase SDK changes what your app collects, and both stores make you declare it:
"You need to identify all of the data you or your third-party partners collect, unless the data meets all of the criteria for optional disclosure listed below." (Apple Developer: App privacy details on the App Store)
Apple's list of third-party partners starts with "analytics tools". Google Play:
"You must reflect data collection or sharing carried out by such third-party code in the Data safety form for your app." (Play Console Help: Provide information for Google Play's Data safety section)
The Google Analytics app for your phone
Separately, Google's free Google Analytics app (App Store and Google Play, 10M+ Play downloads in November 2026) lets you read reports, real-time data and AI-generated insights on your phone. The iPhone version needs iOS 15 or later.
Example
Illustrative cases. Numbers are invented.
A yoga studio with a class-booking app
The stores show 1,000 downloads in a quarter; GA4 shows 800 first opens. The studio logs a class_booked key event: 240 users booked. The retention card shows most new users gone by day 10, so the studio sends a first-week reminder through Firebase Cloud Messaging and watches notification_open.
A restaurant with an app from its ordering platform
The app is the platform's code, so the owner can't add Firebase. The owner uses the platform's order reports plus the store download counts.
A two-person software company shipping version 3.2
Two days after release, the Latest releases report flags 3.2 "Needs investigation": over 1% of sessions crashed both days. Crashlytics points to the payment screen, and version 3.2.1 fixes it.
FAQ
Is Google Analytics for apps free?
Yes. GA4, the Firebase SDK and Crashlytics cost nothing for mobile apps. Only Analytics 360, the enterprise version, is paid, with no published price.
Is Firebase Analytics the same as Google Analytics?
For app data, yes. Firebase is the code in the app plus a developer console; its app reports match your GA4 property's.
Why does GA4 show fewer users than my downloads?
GA4 counts first launches, not downloads, and only from app versions with the SDK. Installs never opened appear only in store numbers.
Different for you?
- You also want website leads counted: GA4 key events for a small business.
- You want a monthly report built on customers, not downloads: the report to ask for.
- Your app handles patient information: tracking tools on a clinic website and HIPAA.
- People visit your website but don't book or download: website not getting leads.
- You want every booking and inquiry answered and tracked: Conversion Agent.