Tim Leighton-Boyce of CXFocus recently blogged about one of his favorite GA reports:
"One of my favorite reports is a standard report that many people don't pay attention to: Conversion > Goals > Return Goal Path. I use it to track errors.
This requires the ability to create a goal from errors, which is not always possible for a website. However, if you can create such a goal, then the “Reverse Path to Goal” will be a great tool. It works well in cases where it is impossible to predict the steps that led to the error, unlike the checkout funnel. In fact, the steps leading to the goal in this case are what we are trying to find”:
Google Analytics
The way back to the goal
You can also use scripts to track JavaScript errors on your page and then add them to event tracking in Google Analytics. Search
Engine Watch explains how to set up event tracking to detect form submission errors:
"Set up event tracking for your form, where each event represents a specific form field. The category should identify which form has the most errors, and the label should be dynamic, pulling in the definition of the rule that caused the error and the input value that violates that rule, separated by, for example, the '|' character.
The above may require some help from a developer. However, once you have all the settings set up, you will have access to an event report that will count and sort errors when filling out your form. You will malta phone number data be able to understand the cause of the error by analyzing the values entered by users. As a result, you will decide to either simplify the logic of checking the value in the field or add explanatory text that will reduce the number of errors that affect conversion.
Want to Increase Conversions? Start With These 4 Google Analytics Metrics
Instead of a conclusion
The goal of working on error messages is to reduce user irritation when filling out a form. If the user is stressed (i.e., the hormone cortisol is produced in their body), you risk losing them and forcing them to go to your competitors.
There are a lot more enjoyable things to do than filling out stupid, complicated, and confusing forms, so conduct a usability study starting with best practices:
Don't blame the user.
Talk about the problem in human language, not like a robot.
Make sure the error is clear and the message is in the correct place.
Make sure users understand how to fix the situation.
Don't list errors at the top of the page - it's better to use line-by-line checking.