Send/create $session_id on $snapshot events #96
Conversation
This will be used by the BE to aggregate recordings nanoid package used adds ~1kb to the bundle. (Current) semantics of session id: - Two tabs will share the same session id - Incognito/not incognito/different browser will not share session_id This is to be improved later
Turns out it was sort of already rolled into this package
|
Is there any reason we shouldn't be doing this for all events? |
I don't think we have a usecase for it right now. We can't use $session_id (directly) in sessions view for grouping sessions because current solution (awesomely) groups events from different posthog libraries, including server-side ones which would not have access to $session_id. It makes much more sense for session replay since you don't want two sessions in different browsers be interlinked. I'll also be making use of $session_id when deleting old snapshots/storing them in S3. Note long-term we probably can make $session_id tab-dependent as well, so it would capture two recordings instead of one. |
|
Ah yep, that makes sense to me. 🚢 |
Semantics of session id:
These may change long-term.
Checklist