How is user_engagement event generated in firebase analytics?

Question

I have seen a param named firebase_screen_class (along with engagement_time_msec, firebase_event_origin and firebase_screen_id) in the user_engagement event in bigQuery, it contains the name of activity classes in my app. Please, can you explain these params and how is the user_engagement event generated?

I also wonder whether this can be useful to get the quantity of impressions or screen views of the activities in my app.

Solution

The user_engagement event is triggered when a user interacts with the app for a minimum duration.

This can be controlled using the setMinimumSessionDuration() method call, also the timeout for a session can be controlled using the setSessionTimeoutDuration() call.

For tracking screen view it is recommended to integrate Firebase with GTM. Take a look at this tutorial for implementation details.

Comments

[josue.0]

So there has to be a interaction of at least 10 seconds (default) for the user_engagement event to be triggered?

[Dan Morenus]

Yes, although that 10 seconds can be broken up over multiple intervals within the session timeout period. More details here.

[josue.0]

@Dan Morenus so, the user_engagement event that I saw in my exported-to-bigquery data is the one explained in the setCurrentScreen (firebase.google.com/docs/reference/android/com/google/fireb‌​ase/…, java.lang.String, java.lang.String) ) documentation?

[Dan Morenus]

@josue.0 Short answer, yes. Firebase Analytics generates engagement events automatically and includes the current screen information with them as the user navigates through your app. Here's a summary of the events that Firebase Analytics generates automatically.

[George]

You may implement custom parameters, related to your screen views, if needed. This is described in the “Log events” document, [1] under the “Log events” subtitle. [1] firebase.google.com/docs/analytics/ios/events

[Daniel Givoni]

these action are related to session_start event and not for user_engagement event see Doc