3 ms·
Record how many opens the form and compare to how many actually submit the form?
by Moru 5y ago
Record how many opens the form and compare to how many actually submit the form?
- capableweb 5y agoYeah, I'm not saying this is a silver-bullet that works in all cases, but some use cases do work better with it. For example, if said form shows one question at a time without any backend requests being done between questions, you could do one last try to log which question the user dropped off at. But again, no silver-bullet.
- vntok 5y agoHow many users submitted the form vs how many users reached the form's page won't tell you anything about why they left or how long they struggled before submitting. A beacon sent for each click on links on the form's page will tell you how many users left for this or that other page, which is very useful to know and optimize by removing the link and/or bringing its contents to the page itself. A beacon sent for each form submission attempt will tell you how many users make mistakes while filling in the form, how good the error messages are, and whether the users tend to fix their input or leave. Bonus points for incrementing an "attempt" hidden field on each submit button click so that you can see how many attempts it takes for all fields to be filled correctly. Tracking what works and what doesn't can drive a lot of UX improvements, for the immediate and measurable benefit of the user.