Currently we track user id (and anonymous id), but not session id. Sessions are useful to understand the behavior of a user bouncing around in Sentry during one visit (as opposed to the user's entire history).
Currently we analyze funnels using ratio of aggregate counts between steps of the funnel, but that loses the link between steps because users can perform the steps independently. For example, a user can arrive at the configure step of the onboarding flow either via an email prompt or via the previous step in the funnel. Sessions can also help isolate these behaviors.
How hard would it be to implement this? I'm thinking of a cookie based solution where we start new session if the current session is older than 30m OR the referrer is a non-sentry URL.
cc @ehfeng
Currently we track user id (and anonymous id), but not session id. Sessions are useful to understand the behavior of a user bouncing around in Sentry during one visit (as opposed to the user's entire history).
Currently we analyze funnels using ratio of aggregate counts between steps of the funnel, but that loses the link between steps because users can perform the steps independently. For example, a user can arrive at the configure step of the onboarding flow either via an email prompt or via the previous step in the funnel. Sessions can also help isolate these behaviors.
How hard would it be to implement this? I'm thinking of a cookie based solution where we start new session if the current session is older than 30m OR the referrer is a non-sentry URL.
cc @ehfeng