GA4 app events
Forward Firebase app events from the server container to the GA4 property.
1. What GA4 needs for app events
Less than the ad platforms. The GA4 App client already recognises the install and the app data stream, so the tag only has to forward the event. No device information or identifier has to be added by hand.
2. What you set up on the GA4 side
An app data stream per platform, iOS and Android separately.
The server-side Tag Manager setting enabled on both streams.
Nothing else. The measurement id of the web stream plays no part here.
3. Tag configuration
Tag type
Google Analytics: GA4
Trigger
Client Name equals the App client
Event name
Inherit from the incoming event
Parameters
Inherit, unless the client wants something extra
This is a second tag next to the existing GA4 web tag, not a change to it. A GA4 tag whose trigger filters on the web client will never fire for app traffic, which is a common reason for "the event is in the container but not in GA4".
Open: confirm whether one GA4 tag with two triggers is preferable to two separate tags in containers that serve both sources.
4. Identifiers this platform accepts
Not applicable. GA4 uses the Firebase instance id. A user_id sent by the app is picked up when the property is configured for it.
5. How to test
GA4 Realtime, filtered on the app platform.
GA4 DebugView, when the app runs in debug mode.
The container's outgoing requests, see Testing and verification.
6. Known errors
Open: add the errors observed in practice. So far the pattern seen is not an error but silence, caused by a tag that is not triggered on the App client.
7. Limits
App events and web events stay separate streams within one property. Combining them into one user journey is a reporting question, not a tagging question.
Open: describe how app and web sessions relate in reporting once we have a case to point at.
Was this helpful?

