In the current implementation, session_tick captures an event every minute. All sessions that last under 1 minute have a session length of 0, sessions that last under 2 minutes have a session length of 1, etc.

Do we need to increase the granularity of session length, particularly for shorter sessions?

Relevant uses cases:

• What's the bounce rate for editors per different dimensions (geography, Internet connection, etc.)? (We could define bounces based on session length; the cutoff would probably be closer to 0 seconds than 60 seconds)