Currently, there's no way to distinguish between the app sessions on Android. While creating funnels of events, having a unique session id would help us join and relate events that belong to the same app session. With this information, it would help us define event funnels, critical user journeys in app sessions to enable us figure out areas to work on, e.g. optimizing the performance of the most common critical user journey among our users. The `session_id` field seems to be available in the schema on BigQuery, but as Jan-Erik pointed out offline, this is a Glean.js-only thing.
Bug 1997336 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Currently, there's no way to distinguish between the app sessions on Android. While creating funnels of events, having a unique session id would help us join and relate events that belong to the same app session. With this information, we would be able to define event funnels, critical user journeys in app sessions and to figure out the areas to work on, e.g. optimizing the performance of the most common critical user journey among our users. The `session_id` field seems to be available in the schema on BigQuery, but as Jan-Erik pointed out offline, this is a Glean.js-only thing.