This post is more than 2 years old.
About a month or so ago I wrote a blog post discussing how you could detect when someone left a form (Warning a user before they leave a form). The idea being that you may want to notice/warn/gently nudge a user to complete a form before they try to leave it. One of my readers, Andrew Schwabe, reached out to me and asked if I wanted to demo a new service he is working on, Formatic.
You begin by adding your form in the console:
Once you've done that, you're done and can simply wait for the data to begin rolling in. Here's where Formatic really begins to shine. About three weeks ago I asked folks on Twitter to start hitting my test form so I could start collecting data. It wasn't a terribly complex form and I made it clear that I didn't care if they finished the form or not. I just wanted people to hit it and play with it. Because I specifically said I didn't care if people finished it, I'm sure some folks intentionally did not complete the form, so the stats you see below may not be 100% realistic, but what I really want to point out is the complexity/depth of the data. First, let's look at the summary.
The Summary view shows form entries for the past three months. Since my form was just for testing there isn't a lot of data here, but you can see that there would - normally - be quite a bit of information here for the time frame. Now let's look at Failed Conversions. This is data about people who didn't successfully complete my form.
Pardon me for being too lazy to stitch the two images above into one shot. The service tells you what field was the last one worked with in failed conversions as well as which one had the most re-entries. Finally you can see just how many people are actually completing the form. To me, this detail is gold. You can immediately see which fields may be causing people to give up your form as well as which fields may be the most problematic.
The next tab, Time Spent, drills down into how much tme is being spent on the form as well as individual form fields.
Next is Form Flows, which describes how people work through your forms:
Ok - so by itself - this is an incredible amount of data - and all rather easy to use. However, Formatic actually has something that goes way beyond just stat collecting. As the amount of data it gathers becomes statistically significant, you can actually write code to listen for events within your form. What kind of events? You can notice, for example, when a user is spending more time on a field than the average user. That's freaking cool. Imagine you've got a field that you really want users to fill out but you notice a lot of people have trouble with it. You could add contextual help to that field that only shows up if the user seems to need it.
All in all, this seems like a service that will definitely be worth your attention. It isn't public yet, but check the site to register for a demo. If you end up using it, I'd love to hear what you thought about it and let me know if it helps you solve real problems.