: Should I track the login page? I've recently started using Google Analytics on a B2B ecommerce site with authentication. Users must login and are redirected to the login page if they try to
I've recently started using Google Analytics on a B2B ecommerce site with authentication. Users must login and are redirected to the login page if they try to access an internal page without first logging in. The login page is clever enough to forward them to the original page once logged in.
Tracking is installed on the login page (/login.aspx), but this means that EVERY session includes at least two page views, which I suspect will affect the bounce rate (?), and every session starts at /login.aspx, which is skewing analysis.
I am considering removing the tracking from the login page, and wondered if anyone had any advice for why I should keep it there?
TIA
More posts by @Speyer207
2 Comments
Sorted by latest first Latest Oldest Best
Keep the login page tracking, you can use it in multiple ways -
You can look at how many people are dropping if their login fails
You can setup a Register Now CTA and check how many folks sign-up from the login page
Upon submitting the login details, you can mark which user is signing in and track user-wise activity tied to your registered users within GA (the prerequisite is the new UA script though).
If you don't track the login page there would be no way to know the drop off rate from it. I'd imagine that a very important question for you would be what percentage of your visitors don't log in or sign up.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.