Form analytics
Form analytics that finds the field that loses your leads
Form analytics measures how visitors interact with each field of a form: which field they abandon, how long they hesitate, what they retype and which errors they hit. UserExplorer reports this for signup, checkout and lead forms, with values masked and replays one click away.
- Drop-off and completion rate per field
- Hesitation time and refill count for each input
- Validation errors tied to the field that caused them
- Values masked by default, only behavior is measured
Signup form, last 30 days
| Field | Hesitation | Drop-off |
|---|---|---|
| Work email | 2.1 s | 3% |
| Password | 4.8 s | 6% |
| Phone number | 11.4 s | 31% |
| Company size | 1.9 s | 2% |
Sample data
Why fields matter
A form is a funnel with one step per field
A page level report says 1,000 people started your demo request and 410 sent it. It does not say whether they left at the company size dropdown, the phone field or the consent checkbox. Form analytics splits the form into fields and shows the path through them, the same way funnel analysis splits a journey into pages.
The answer is often a single field. A postcode input that rejects spaces, a password rule that only appears after submit, a required phone number on a B2B form. Each one is cheap to fix once you can see it.
UserExplorer records interaction with the field, never its value. Inputs are masked in the browser by default, so you learn that people retyped an email three times without ever storing the address.
Metrics
Six signals for every field
Field drop-off
The last field a visitor touched before leaving the form, ranked by how many people stop there.
Hesitation time
Time between focusing a field and starting to type, a strong hint of confusing labels.
Refills
How often a field is cleared and filled again, typical for format rules users cannot guess.
Error rate
Validation messages shown per field, linked to the attempts that triggered them.
Completion rate
Share of visitors who start and successfully submit, split by device and source.
Replays per field
Open the session replays of visitors who quit at a chosen field.
Checkout and signup
Mobile forms hide problems desktop testing never shows
On a phone, a keyboard that covers the submit button or an input that opens the wrong keyboard type is enough to lose a sale. Field reports split by device make those cases visible within a day of traffic.
Pair the form report with rage click tracking to catch disabled buttons that look active, and with surveys to ask visitors who left what stopped them.
Signup funnel, last 30 days
Sample data-
1. Landing page 100%
-
2. Start signup 62%
-
3. Verify phone 42%
31% leave here
-
4. Account created 29%
Setup
Form tracking without extra tagging
-
Step 1
Install the snippet
Forms on your pages are detected automatically, including multi step forms in single page apps.
-
Step 2
Confirm the fields
Check the detected fields, rename them and mark any extra element as private.
-
Step 3
Pick a segment
Compare devices, traffic sources or new and returning visitors.
-
Step 4
Fix the worst field
Watch replays at the field with the highest drop-off and test a change.
Reading the report
What each signal usually points to
| Signal | Common cause | Typical fix |
|---|---|---|
| High hesitation | Unclear label or unexpected question | Rewrite the label, add a short hint |
| Many refills | Hidden format rule | Accept more formats, show the rule upfront |
| Drop-off at one field | Sensitive or unnecessary data | Make it optional or remove it |
| High error rate | Strict validation | Validate inline and explain the error |
| Low mobile completion | Layout or keyboard issue | Use correct input types, keep submit visible |
-
High hesitation
- Common cause
- Unclear label or unexpected question
- Typical fix
- Rewrite the label, add a short hint
-
Many refills
- Common cause
- Hidden format rule
- Typical fix
- Accept more formats, show the rule upfront
-
Drop-off at one field
- Common cause
- Sensitive or unnecessary data
- Typical fix
- Make it optional or remove it
-
High error rate
- Common cause
- Strict validation
- Typical fix
- Validate inline and explain the error
-
Low mobile completion
- Common cause
- Layout or keyboard issue
- Typical fix
- Use correct input types, keep submit visible
FAQ
Questions teams ask before they start
What is form analytics?
Form analytics tracks how visitors interact with each field of a web form, including drop-off, hesitation, refills and errors, so you can find and fix the fields that stop people from submitting.
Does UserExplorer store what users type?
No. Inputs are masked in the browser by default. We measure focus, typing activity, clearing and errors, not the values. See privacy and security.
Do I need to tag each form?
No. Forms are detected automatically, including multi step forms in single page apps. You can rename fields and exclude any form.
Does it work with embedded and third party forms?
Forms rendered in your own page are tracked. Forms inside a cross domain iframe can only be tracked if the snippet also runs on that domain.
Which plans include form analytics?
Form analytics is part of every plan, from Startup at $99 a month. See pricing.
How is form analytics different from funnel analysis?
A funnel measures steps across pages or events. Form analytics goes inside one step and measures each field, so the two are often used together.
See the reason behind your numbers this week
Install one snippet, record real sessions with masking on by default, and let the AI researcher show you what to fix first.