Our application redirects users to a login page thats on another domain. So our bounce rate is being significantly skewed since landing on the main page initializes RUM, registers a single "visit" action and redirects immediately to the login page; and DT counts that as a bounce. We'd like to turnoff all of monitoring until the user is authenticated so that the bounce rate is calculated properly. From the dtrum documentation I see two potential candidates dtrum.setAutomaticActionDetection() and/or dtrum.enable()/disable(). However it's not clear whether either of those will actually turn off the reports related to bounce rate.
Solved! Go to Solution.
I think you're on the right track. If RUM is not enabled automatically, and you manually enable it using dtrum.enable(), then you can control when RUM starts. The downside is that you will loose visibility into the page activities prior to enabling RUM.
The definition of a bounce is a visit with a single user action. So yes I think you are right, manually report a second user action and that should eliminate the false bounces. But you will still have two sessions for that user, one from the landing page, the other from the login onwards.