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.
What this means
app_open is one of GA4's automatically collected app events. The Firebase/GA4 SDK logs it when a user opens the app or returns it to the foreground after it had moved to the background. It is the app-launch signal and a building block for session and retention measurement.
It captures presence — the app is in front of the user — rather than any specific in-app action.
Opens versus engagement
An app_open shows the app was foregrounded; it does not show the user accomplished anything. Pair it with screen_view and engagement events to distinguish habitual opens from productive sessions — an app opened often but closed immediately has a retention illusion. Because it has no clean web counterpart, avoid mapping app_open onto web session or visit metrics.
- Fires when the app opens or foregrounds
- Collected automatically by the Firebase/GA4 SDK
- Presence signal, not proof of in-app activity
How it appears in analytics and logs
An app_open event means the app came to the foreground. Frequent opens suggest habitual use, but opens alone do not prove the user did anything once inside.
Diagnostic use case
Measure how often users open or return to an app, as a foundation for retention and engagement analysis.
What WebmasterID can help detect
WebmasterID is web-focused; app_open is documented so teams comparing app and web behaviour understand the app-launch signal that has no direct web equivalent.
Common mistakes
- Treating app opens as proof of engagement.
- Mapping app_open onto web session metrics.
- Ignoring screen_view when interpreting opens.
Privacy and accuracy notes
app_open records that the app was opened, not who opened it. It is an app-lifecycle signal, not personal data.
Related pages
- 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.
- The session_start event
The session_start event marks the beginning of a visit. In GA4 it is fired automatically the first time a user is active in a new session, and it underpins every session-scoped metric. Understanding when a session begins — and the timeout that ends it — explains why session counts behave the way they do across midnight, campaigns, and idle periods.
- The first_visit event and new users
The first_visit event is fired the first time a user opens your site in a browser. It is how GA4 distinguishes new users from returning ones: the presence of a first_visit defines a new user. Because it depends on a stored marker, clearing cookies or using a fresh browser makes the same person look new — a limitation worth understanding before trusting new-user counts.
- Events documentation
Understand app lifecycle events.
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.