You have created a good website that is becoming popular, but then you notice a fall in traffic after a while for seemingly no reason at all. The content is great, links provided are useful. What could be the reason? The most likely one is that users are unable to access their accounts or have problems logging in. Now for any product, it is the most important thing to keep track of the errors that are preventing the product from becoming more popular.
If you don’t take care of this, the user will try to log-in a couple of times and when the problem persists, will finally get bored and walk away to another, better managed website. With the cut-throat competition on the internet, you cannot afford to let errors get the better of you. So error tracking assumes high importance in website management.
Google Analytics: This extremely versatile error tracking tool can be used and manipulated effectively to track down errors. It can be found under even tracking, then click on content and go on to categories. The best way to track errors is to use Google analytics to assemble error tracking to reveal blocks faced by readers on your website. Tracking events makes error tracking more organized and effective.
Categories of errors
There are two distinct types of errors that can be encountered. The first is called form-field errors. Without getting confused with geek-speak, form-field error refers to errors the user faces while trying to access the page and fill in fields. This could be from login fields, where he has entered incorrect usernames or password right up to filling forms where he has missed out compulsory information fields. This is very common error and can be a big stumbling block to netting a sizable pool of subscribers. This error can originate from a mistake from the client as well as from the server.
High hit rates but low unique view rates ( meaning readers are coming to the web page but are unable to linger there) typically indicate form-field errors. The solution is to track an event every time an error message crops up. The specifications can be defined as:
Spec: trackEvent (category, action, opt-level, opt-value). Defining the error message as a variable instead of a fixed one helps customize error messages. For example, a login error will receive a login error message while a password error will receive a password error message. This makes the error message more relevant to the user who will understand what he has done wrong. Vague error messages are no good.
404 page error
By adding a tracking code to the 404 pages, you can figure out which URL’s the users were trying to click and which website was able to provide them with that URL. Interlinking forms a vital part of a professional website and you should be able to pinpoint where users were unable to access a link.