designcourse
designcourse copied to clipboard
leeper
💡 track sessions manually
From @scottalguire
Our clients install our widget on their website and we want to start recording a session once opened and stop once closed.
If we init on open, and stopSession on close, a new session will start again automatically when the user interacts with the webpage further, even if they never open our widget again. We really need a way to start/stop sessions manually so the surrounding website isn't polluting our data with irrelevant interactions and errors.
We could consider a dedicated configuration (similar to trackViewsManually) to let you start and stop the session manually instead of our current behaviours of starting the session on init or re-start a session on user interaction.
We'll let you know here if we make progress on this topic.
This would be a very welcome feature, especially in the context of SPA. With the pricing model being per session it is undesirable that sessions are created automatically after init has been called. It would be fantastic if the configuration could be changed on the manual start of a new session also.
I have a similar issue. I have severall apps within the same launchpad, and we want record only when we are on a specific app. Recording starts well, but it never stops, even using 'stopSessionReplayRecording' or 'stopSession'. Is there any news on this, or any know workaround?
@pedro-canelas if you think there is an issue with stopSessionReplayRecording or stopSession, please open a bug report with detailed information and context
@BenoitZugmeyer actually the problem I'm having is that if I use startView several times on the same session, they cumulate. Is there any way of 'closing' a view before starting a new one?
The Browser SDK tracks only one view at a time. When you start a new view, the previous view is closed. I'm not sure what you mean by "they cumulate".