The screen_view event (apps)
screen_view is the GA4 event that records when a screen is displayed in a mobile app, the app analogue of the web's page_view. It carries firebase_screen and firebase_screen_class parameters identifying the screen. It is collected automatically by the Firebase/GA4 SDKs and is the basis for app navigation and screen-engagement analysis.
What this means
screen_view is GA4's app-side counterpart to page_view. When a screen is displayed in a mobile app, the Firebase/GA4 SDK logs a screen_view with `firebase_screen` (the screen name) and `firebase_screen_class` (the underlying class). It is collected automatically as part of the SDK's measurement, and you can also set screen names manually for clarity.
It is the unit of navigation for apps the way pageviews are for websites.
Web pages versus app screens
On the web GA4 records page_view with page_location and page_title; in an app it records screen_view with firebase_screen. They are parallel concepts but not interchangeable — a web property and an app stream count navigation differently, so combining them needs care. Use clear, stable screen names so screen-flow reports are readable rather than a list of class names.
- App analogue of the web page_view event
- Carries firebase_screen and firebase_screen_class
- Collected automatically by the Firebase/GA4 SDK
How it appears in analytics and logs
A screen_view event means an app screen was shown. Screen sequences reveal in-app navigation paths; a screen with high views but quick exits may be a dead end or a confusing step.
Diagnostic use case
Measure which app screens are viewed and how users move between them — the app equivalent of pageview-based site navigation analysis.
What WebmasterID can help detect
WebmasterID focuses on web first-party analytics; screen_view is documented here so you understand the app-side analogue of page_view when comparing web and app data.
Common mistakes
- Equating app screen_view counts directly with web pageviews.
- Leaving auto class names instead of meaningful screen names.
- Assuming screen_view fires on the web (it does not).
Privacy and accuracy notes
screen_view records the screen name and class, not the user. The firebase_screen parameters are app structure metadata, not personal data.
Related pages
- The page_view event: the base of web analytics
page_view is the event fired when a page loads. It is the base of almost every web-analytics model: sessions, pageviews, and most reports build on it. In classic sites the tracker fires it automatically on load; in single-page apps you fire it on each route change. Its properties (path, title, referrer) drive most downstream reports.
- The app_open event
app_open is a GA4 event collected automatically by the Firebase/GA4 SDK when a user opens an app or brings it to the foreground after it was in the background. It marks app launches and returns, underpinning app engagement, retention, and session analysis — but a foreground event is not the same as meaningful use.
- Enhanced measurement (auto events)
Enhanced measurement is a GA4 setting that automatically collects a set of interaction events — scrolls, outbound clicks, site search, video engagement, file downloads, and form interactions — without extra code. It is convenient but not magic: it only covers standard patterns, can over- or under-count, and each option can be toggled. This page explains what it does and its limits.
- Events documentation
Compare web and app event models.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.