Realtime Session Time Calculated Wrong

On the performance tab, the total/average session time thing is very inaccurate if your experience has multiple places players can teleport to.

For the experience session time, it shouldn’t take the average of the times between the places as that is inaccurate. It should add all the players sessions throughout the places up until they leave the entire experience.

The session time for Roblox benchmarks are correctly calculated in the way I described. The real time session time should have a toggle for average/total or switch to total entirely so developers can accurately monitor realtime bugs or decline in session time due to an update.

Correct calculation:
image

Incorrect calculation:

Page URL: https://create.roblox.com/dashboard/creations/experiences/5604202962/analytics/performance?breakdown=Platform&rangeType=Last1Day&minTime=1740253992875&maxTime=1740256236000

1 Like

Session time is per place and this is an intentional product behaviour so that you’re able to see if a Place that is recently published is behaving incorrectly.

If you are looking for Experience level Session Time, as you mentioned, you can look at the Engagement page.

There is no realtime engagement. I am aware of Average Session Time, and what I am saying is that if a game like Rivals pushed out an update with a bug, they likely wouldn’t notice until atleast a day later (if purely looking at statistics) since realtime session time doesn’t accurately represent the stats that come out of the engagement page. Rivals is a good example because teleporting to a different place for matches is a very prominent part of the game.

if a game like Rivals pushed out an update with a bug, they likely wouldn’t notice until atleast a day later (if purely looking at statistics) since realtime session time doesn’t accurately represent the stats that come out of the engagement page

I understand your feature request. Calculating realtime session time across place teleports is a much harder computational problem than doing it at the place level and something we’re not able to do right now

If I understand your example, if there is a bug then you would notice that CCU is down or session time per place is down because those are the inputs into the overall session time.

If the bug is in a certain place, then the current metrics would be able to show you which place is having that bug. If it’s across all places, you would notice a session time decrease over all places.

2 Likes