Skip to main content
Solved

Issue with the average session length


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?

Best answer by SheenaGreen

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, hiddeninactive, 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

View original
Did this topic help you find an answer to your question?

2 replies

SheenaGreen
Super Helper
Forum|alt.badge.img+8
  • Super Helper
  • 60 replies
  • Answer
  • August 5, 2022

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, hiddeninactive, 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
Team Member
Forum|alt.badge.img+2

Thank you @SheenaGreen 😃


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings