Skip to content
Forms

Reading Form Analytics: What Actually Matters

DT Form Team

Completion rate is a starting point, not an answer

A completion rate tells you that something is wrong, or that nothing is, but it doesn't tell you where. A form with a 40% completion rate could be losing people at field one or field twelve, and those are two entirely different problems.

Field-level drop-off data is what actually points to a fix. If most of the loss happens right after a specific question, that question is worth scrutinizing first, whether it's poorly worded, feels invasive, or is simply misplaced.

Time-on-field is an underused signal

A field that takes people noticeably longer to fill out than similar fields is often either confusingly worded or requesting information the respondent has to go look up. Both are fixable once identified.

This is particularly useful for free-text fields, where a long pause often means someone is unsure what level of detail is expected.

Comparing across versions

When testing a change, compare against a stable baseline period rather than a single prior version, since submission volume naturally fluctuates by day of week and time of month for most forms.

Small sample sizes can be misleading. A form that only gets a handful of submissions a week needs a longer observation window before drawing conclusions from a change.

Want to try this yourself? Explore the product →