Signup form optimization: find the field that loses people
Most signup forms lose people at one or two fields, not evenly. Visiflow records which fields visitors touched, how long it took and whether they sent or left, without recording the values, so you can fix the exact point of friction.
Step 1: name the form and add it to a funnel
- Add
data-rastro-form="signup"to the form tag. - In the funnel wizard, add the page with the form and a form step.
- Let it collect for a week, then read starts and sends by device.
Step 2: read the numbers
See form tracking for how each form is recorded.
| Number | What it tells you |
|---|---|
| Visits to starts | Whether the form is noticed |
| Starts to sends | Whether the form is too long or confusing |
| Time to send | How much effort it takes |
| Mobile versus desktop | Whether the form works on a phone |
See Visiflow in action
Short demo videos on sample data (not a real customer). Each one shows a task from start to finish.
Build a funnel in 3 steps
A guided wizard: pick a starting point, add steps, check the data and finish.
- Pick a template
- Add and check each step
- Save and finish
Videos use fictional sample data.
Step 3: find the last field touched
For people who abandoned, look at the last field they touched. A pattern tells you the cause: a password rule, a phone number, a work-email requirement or a long select list.
Step 4: watch five recordings
Open recordings of people who started and did not send. Look for errors that appear only after pressing the button, a keyboard that covers the field on mobile and fields that reject valid input.
Fixes that often help
- Remove fields you do not need for the first step.
- Show password rules before the person types.
- Validate as the person goes, and show the error next to the field.
- Use the right keyboard type on mobile.
- Make the button say what happens, such as "Create my account".
Mistakes that waste a test
Do not judge a form on a handful of starts, because a few people can swing the rate. Do not compare a week with a holiday to a normal week. Do not change the form and the page headline together. And do not forget to look at mobile on its own, since a form that works well on a desktop can fail on a phone where the keyboard covers half of the screen.
What to record in a change log
Write down the date, the form, the single change you made and the starts-to-sends rate before it. Check the same rate after two full weeks, by device. A short log stops you from repeating a change that did not work and shows your team what moved the number.
Step 5: test one change
Change one thing and compare starts-to-sends before and after. For a split test, read the result with the A/B test calculator.
Questions
Does Visiflow record what people type?
No. It records field names, counts and timing only.
How do I find the field that loses people?
Look at the last field touched by people who abandoned, and watch recordings.
Does it work on single-page apps?
Yes, as long as the form is a form element with a stable name.
What if my form sends with a script?
Send an event with rastro('track', ...) when it succeeds.