Solved

Issue with the average session length

  • 5 August 2022
  • 2 replies
  • 142 views
P

Hello,

 

We’ve released the new app build on Android using the native Google Play staged release  functionality (50\50 split release).

 

Unfortunately, we see that the new build’s average session length has dropped by ~20-25%: https://prnt.sc/Pc6imrI6htuJ . We can’t understand how could this happen: the new build doesn’t have bugs or new features that could’ve dropped the session length so much. The most significant change we did is we’ve deleted lots of unused custom Amplitude events.

 

Tell me, please, have you ever experienced anything like that? Maybe you have any thoughts\ideas?

icon

Best answer by SheenaGreen 5 August 2022, 19:28

View original

2 replies

SheenaGreen
Rank
Userlevel 4
Badge +8

Is it possible the Amplitude events you deleted in the new build were extending session length in the old build? The below may apply to your situation:
 

Additionally, hidden, inactive, and deleted events will not be included in the session length calculation. For example, let's say you have the following series of events:

Event A --> Event B --> Event C --> Event D

If Event C and Event D are hidden, inactive, or deleted in Govern, then the max(client_event_time) is taken from Event B instead of Event D. 

 

Here’s the link to the full support article: https://help.amplitude.com/hc/en-us/articles/115002323627-Tracking-Sessions#h_408dc7ad-4919-4fa1-a506-c43174f68096

Product Release Team
Rank
Userlevel 3
Badge +2

Thank you @SheenaGreen 😃

Reply


Terms & ConditionsCookie settings