Our current recommendation is to simply call the stop method once and not delay the end user any further. Dependent upon the browser, the stop message will be delivered and processed by our servers and the server reply (which is just an empty confirmation) may or may not reach the browser. This is not a fool proof way of stopping the session but the side effects of not ensuring that the stop message is delivered will mostly be a slightly inaccuracy in the sessionlength statistics.
So for now, there is no need to try to keep the user on the page, you should simply just stop the monitor and continue. Are you experiencing other issues from not stopping the monitor that we should be aware of?
Hope this helps
Monitor web applications with the new EQATEC Application Analytics JS library. Compatible with all modern browsers.
Test it today >>