Confirmed users
74
edits
Loop/Session: Difference between revisions
m
s/FF/Fx/
(Bring the descriptions up to date with the 2015-08-06 update to the Session Progress algorithm.) |
Mikedeboer (talk | contribs) m (s/FF/Fx/) |
||
| Line 10: | Line 10: | ||
Sessions are, at the moment, computed differently for different metrics: | Sessions are, at the moment, computed differently for different metrics: | ||
* The [https://metrics.services.mozilla.com/loop-server-dashboard/#session_progress '''Session Progress''' graph] uses the "linkclicker theorem" (≤1 linkclicker in a room at once, ≤1 | * The [https://metrics.services.mozilla.com/loop-server-dashboard/#session_progress '''Session Progress''' graph] uses the "linkclicker theorem" (≤1 linkclicker in a room at once, ≤1 Fx user in a room at once) as an aid to deciding when 2 people are in a room. The following counts as 2 sessions: A joins, B joins, A leaves, A rejoins. A user is also considered to have left if he goes 5 minutes without network activity. | ||
* The code behind the [https://metrics.services.mozilla.com/loop-server-dashboard/#total_sessions '''Room Sessions''' graph] ("the sessionizer") doesn't use the linkclicker theorem. It's all based on uids (Hawk IDs). It currently assumes all "unknown" (linkclicker) UIDs are the same person. Previously, it assumed they are all different people. Neither assumption is accurate; they didn't have the userType data when they wrote the Lua code. ErikRose believes whd or twist are going to update it to match the Session Progress algorithm. | * The code behind the [https://metrics.services.mozilla.com/loop-server-dashboard/#total_sessions '''Room Sessions''' graph] ("the sessionizer") doesn't use the linkclicker theorem. It's all based on uids (Hawk IDs). It currently assumes all "unknown" (linkclicker) UIDs are the same person. Previously, it assumed they are all different people. Neither assumption is accurate; they didn't have the userType data when they wrote the Lua code. ErikRose believes whd or twist are going to update it to match the Session Progress algorithm. | ||
* '''Google Analytics''' should be pretty close to the Session Progress numbers, but there may be small deviations due to differences in handling timeouts and other corner cases. Upon successful connection between 2 parties and the start of a stream, we trigger an event to Google Analytics. 2 discrete conversations in 1 room count twice toward GA’s Media Connected events. | * '''Google Analytics''' should be pretty close to the Session Progress numbers, but there may be small deviations due to differences in handling timeouts and other corner cases. Upon successful connection between 2 parties and the start of a stream, we trigger an event to Google Analytics. 2 discrete conversations in 1 room count twice toward GA’s Media Connected events. | ||
* Tokbox's idea of sessions is entirely different: they care about a persistent stream allocated on their end, which is not usefully comparable to any of the above concepts. | * Tokbox's idea of sessions is entirely different: they care about a persistent stream allocated on their end, which is not usefully comparable to any of the above concepts. | ||