What does the “(not set)” row mean in Google Analytics (GA4) and Firebase reports?
Applies to
- CapiraMobile
Answer
The “(not set)” row appears when GA4/Firebase receives an event but cannot associate it with a screen/page. This typically happens when events are collected while the app is running in the background, where there is no active screen to attribute.
What’s happening
Some app activity continues even when the app is not open on-screen (for example, background sync or update checks). If those background processes send analytics events, GA4/Firebase records the event but leaves the screen/page dimension as “(not set)” because no screen is currently in view.
Why it stands out
Background processes can generate a large number of events. When those events are included in screen-based reporting, the “(not set)” row can appear unusually high compared to user-driven screen activity.
What to do with it
If your goal is to understand patron in-app behavior, excluding “(not set)” from screen/page reports will provide a more accurate view of how users navigate and engage with the app.