Firebase Analytics Data Not Showing? What to Check First

You shipped the app, someone used it, and the dashboard is empty. Before assuming the data is lost, work through these four checks in order. They are arranged by how often each one turns out to be the cause, not by how hard they are.

1. Is the SDK actually running?

The most common cause is the simplest: the Analytics SDK never starts. A dependency in the manifest is not the same as an initialised SDK. Firebase has to be configured at launch, and the config file has to match the app you are running.

• The Firebase config file is in the build — GoogleService-Info.plist for iOS, google-services.json for Android
• The bundle ID or package name in that file matches the app you are actually running
• Firebase initialises on startup, before you expect any event to be recorded
• You are testing a build that includes the Analytics SDK, not a stripped variant

2. Is Firebase linked to a GA4 property?

Firebase Analytics and Google Analytics 4 are two halves of the same pipeline, but the link between them is a setting, not a given. A Firebase project created without Analytics enabled will collect nothing, and a project whose link was never completed will show data in Firebase while GA4 stays empty.

1. 1

   Open the Firebase console

   Go to the project you are debugging, then Project settings.

2. 2

   Open Integrations

   Find the Google Analytics entry and check whether it is enabled.

3. 3

   Confirm the linked property

   An enabled integration names the GA4 property it feeds. If no property is named, the link is not finished.

3. Are you reading a report that has data yet?

Realtime and the standard reports are produced differently and on different schedules. Realtime reflects recent activity within a short window. The standard reports are processed in batches, and a day that has not finished processing can look empty or incomplete even though the events arrived.

4. Can this Google account see the property?

Analytics access is per Google account. It is easy to build an app under one account and then open Analytics — or connect a tool like Appnaly — signed in as another. The data is fine; you simply are not looking at it.

• The account you are signed in with has access to that GA4 property
• The property you are checking is the one the Firebase project feeds
• If someone else set up Analytics, they have granted your account read access

How this looks in Appnaly

Appnaly reads your existing Google Analytics data — it does not collect any of its own. That has one practical consequence worth stating plainly: if GA4 has no data for an app, Appnaly has nothing to show for it either, and an empty card in Appnaly is a symptom rather than a fault. It also means the fix is always upstream, in Firebase or GA4, never in Appnaly.

If your apps do not appear in Appnaly at all, the cause is usually the fourth check above: the connected Google account cannot read the property. If the apps appear but their numbers are zero, the cause is usually the first or second.

Common misconceptions

• Adding the Firebase dependency is enough — it is not; the SDK still has to initialise
• Enabling Analytics in Firebase creates historical data — it does not; collection starts when it starts
• Empty realtime means the SDK is broken — not necessarily; nobody may simply be using the app right now
• GA4 and Firebase should always agree exactly — they will not, because they process on different schedules