Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Conversion Rate Optimisation › Troubleshooting

Form Abandonment Too High

Why visitors start a form and never submit it: too many fields, confusing errors, mobile input problems, privacy worries, an early ask and silent failures.
Troubleshootingintermediate8 min readUpdated

First, instrument the form so abandonment can be located

"The form converts badly" cannot be diagnosed; "people stop at the phone field on mobile" can. Set up events for the first input in any field, for interaction with each field, for every submit attempt, for every validation error with the field that triggered it, and for the confirmed submission, as the measuring section of the forms guide describes. Read starts over page views separately from completions over starts: the first is a page problem, the second is a form problem, and only the second belongs here. The tutorial on tracking forms with Tag Manager builds these events step by step, including the negative tests that keep failed attempts out of the count. If the inbox or CRM holds more completed enquiries than analytics records, rule out a measurement fault first with the page on GA4 not tracking form submissions, because missing completions make abandonment look worse than it is.

With the events in place, build a field-by-field view for the last few weeks, split by device. Look for a field where the share of starters still present falls sharply, for a field that produces most of the errors, and for a gap between submit attempts and confirmed submissions. Each pattern points at a different cause in the table below. If very few visitors start the form at all, the problem sits earlier on the page, and the conversion rate troubleshooting hub routes to the bounce and landing page diagnoses instead.

Diagnosis table

Diagnosis

SymptomCheckLikely causeFix
Starters fall away steadily as the form goes on, with a sharp loss at qualifying questionsField count against what the next step needs; where the last interaction happensMore fields than the offer justifiesCut or defer every field the next step does not need
Many submit attempts fail, mostly on one or two fieldsErrors by field and message; whether validation runs on leaving the field or only on submitUnclear or late validationValidate on leaving the field; accept real-world formats
Abandonment is far higher on phones at text-heavy fieldsKeyboard type, autofill and layout per field on a mid-range phoneInputs awkward on mobileCorrect input types, autofill names and single column
Visitors stop at the email or phone field and recordings show hesitationWhat the page says about data use, contact and spam near the formPrivacy or spam worriesState what happens next and how details are used
Visitors stop at the button, or at budget and timeline questionsThe size of the commitment the form asks for against the traffic's stageAn ask the visitor is not ready forOffer a lighter first step; capture contact first
Submit attempts are high but few submissions arrive in the inbox or CRMAttempts against confirmed submissions and records receivedSilent submission failureFix the handler; confirm receipt on screen and by email

Fix, verify and prevent each cause

More fields than the offer is worth

Every field costs effort, and every request for information raises the question of why it is wanted. When the form asks for budget, company size and timeline before a simple quote, visitors weigh the cost and leave. Nielsen Norman Group's form usability recommendations begin with keeping forms short.

Fix: work backwards from what the next step genuinely needs, as the forms guide sets out, cut everything else, and move qualifying questions to an optional later step or to the first call.

Verify: completions over starts rise, and the field where most people stopped no longer stands out in the field view.

Prevent: require any new field to be argued for against the completions it will cost, with the person requesting it named.

Errors that confuse or arrive too late

A form that waits until submission to report several errors, clears what was typed, or rejects phone numbers with spaces and names with apostrophes turns committed visitors away at the last moment.

Fix: validate each field when the visitor leaves it, keep everything entered on error, place a specific message beside the field that explains how to fix it, and loosen rules to accept what people actually type, following the errors section of the forms guide.

Verify: the share of submit attempts that fail validation falls, and the field that produced most errors drops down the list.

Prevent: review the error log monthly and test the form with the unusual but valid inputs real customers use.

Inputs that fight the phone

On a phone, a field that opens the wrong keyboard, blocks autofill, sits in a two-column layout or hides its label under the keyboard multiplies the effort of every entry.

Fix: set the input type for each field so the right keyboard appears, name fields in the standard way so autofill works, stack fields in a single column with labels above, and keep the button reachable when the keyboard is open, as the phone-form section of the speed and mobile guide explains.

Verify: completion on phones closes much of the gap with desktop, and time spent per field on phones falls.

Prevent: fill in every form on a mid-range phone, with autofill, before each release.

Doubt about what happens to the details

The moment of typing an email address or phone number is when visitors wonder whether they will be spammed, called repeatedly or have their details shared. A form that says nothing at that moment loses the cautious.

Fix: beside the form, say what happens next and how soon, why a phone number is asked for if it is, and how the details will be used, with a link to the privacy notice; add a testimonial about the experience after enquiring, as the placement advice in the trust and proof guide recommends.

Verify: fewer starters stop at the contact fields, and recordings show less hesitation there.

Prevent: keep the reassurance next to the form in the page template so it survives redesigns.

An ask the visitor is not ready to make

A form that demands a sales call, a site survey or a budget from someone who wanted a price or an example asks for a decision the visitor has not reached.

Fix: offer a lighter first step that suits the traffic's stage, such as a price guide, a short quiz or a callback at a chosen time, and capture contact details before any qualifying questions; test the change with the design in the lead form length experiment, which reads qualified leads alongside completions.

Verify: completions rise without the share of leads reaching the next sales stage falling.

Prevent: match each form's call to action to the intent of the traffic the page receives, and review it when campaigns change.

Forms that fail without anyone noticing

Some abandonment is not abandonment at all: the visitor pressed send, the form spun, nothing arrived. A broken handler, a spam filter rejecting real entries, an expired integration or a missing confirmation message can lose leads that look like drop-offs.

Fix: compare submit attempts with records received in the inbox or CRM, test the full path end to end, and confirm receipt on screen and by email, using the tracking verification checklist to check that the submission event fires only on real success.

Verify: attempts, confirmed submissions and records received agree for a full week.

Prevent: send a test submission through every live form on a schedule and alert the owner if it does not arrive.

A prevention routine for forms

Forms decay quietly: a field is added for a campaign, an integration expires, a validation rule is tightened, and completion slides without anyone deciding it should. Keep a short record for each form of its fields, the reason for each and the person who asked for it. Weekly, read completions over starts by device and the gap between submit attempts and records received, and investigate any form where either moved. Monthly, review the field view and the error log, and remove or defer the field that loses the most starters if it is not essential. After every release, fill in each live form on a phone and a desktop, with autofill, and check that the entry arrived. Quarterly, ask sales which fields they used and drop the rest, and check that each form's ask still suits the traffic the Landing Page now receives. Read form completion beside lead quality throughout, because a form's conversion rate (CVR) can rise while the leads it produces get worse. When a customer says they sent a form and the enquiry did not reach the business, the diagnosis of website form submissions not arriving follows a marked test submission from the form to the person who has to respond.

Illustrative example — not a real result

A software company's demo form

A scheduling-software company's demo request form had 11 fields, and 640 people a month started it, of whom 118 submitted. Field events showed 38% of starters leaving at "number of employees" and "budget", and on phones another group leaving at the phone field, which opened the full keyboard and rejected numbers with spaces. Comparing submit attempts with CRM records found 21 a month lost to a spam filter that blocked company email domains it did not recognise. The team cut the form to 5 fields, moved company size and budget to the booking call, fixed the phone input, and whitelisted the blocked domains. Submissions rose to 247 a month, and the share of demos that sales accepted held at 64%.

Common mistakes

Redesigning the form before measuring where people stop. Treating every field request from colleagues as free. Showing errors only after submission. Testing forms only on desktop. Assuming every missing lead was abandoned rather than lost in transit. Celebrating more submissions without checking lead quality.

Frequently asked questions

How do I measure form abandonment?

Record a form start when the first field receives input, record each field interaction, record every submit attempt and every validation error with the field that caused it, and record the successful submission separately from the attempt. Abandonment is starts that never become successful submissions, and the last field touched before leaving shows where it happens. Read all of it by device.

Will a multi-step form reduce abandonment?

It can, particularly on phones, when the first step asks for the essentials and captures contact details early, so that someone who leaves a later step is still a lead. It does not help if every step is as demanding as the original form, or if progress is hidden. Test it against the single-page version with lead quality as a guardrail.

Should we remove fields that sales uses to qualify leads?

Not without measuring what they cost and what they are worth. Ask sales which fields they actually use before the first conversation, move the rest to a later step or to the call, and test the shorter form with the share of leads that reach the next sales stage as a guardrail. A form that produces more leads nobody can work has not improved.

Terms used on this page

Where this page is used

Also related

Sources

  1. Website Forms Usability: Top 10 Recommendations — Nielsen Norman Group

Related