Form abandonment rate

How do you calculate form abandonment rate?

The standard formula is:

Form abandonment rate (%) = ((forms_started − forms_submitted) / forms_started) × 100

Where:

• forms_started is the count of unique sessions that focused at least one input, textarea, or select inside the form
• forms_submitted is the count of unique sessions that fired a successful submit event (or that reached the post-submit thank-you state)

Some teams prefer to use unique users instead of sessions, which gives a slightly lower number because returning users get deduplicated.

What counts as "started"?

The two competing definitions are:

• Field focus — the user focused (focusin) any input. This is the dominant definition because it captures intent.
• Field interaction — the user typed at least one character or made a selection. This is stricter and excludes accidental tabs into a field.

Pick one and stick with it; switching definitions invalidates historical comparisons. Most analytics vendors default to field focus.

How is it different from form completion rate?

Abandonment rate and completion rate are mathematical complements: they always sum to 100 percent. Form conversion rate uses page views as the denominator and is therefore always lower than completion rate, because it includes visitors who never engaged with the form at all.

What does "good" look like?

Industry benchmarks vary by form type, but widely cited ranges:

• The Baymard Institute pegs the average ecommerce checkout abandonment rate at around 70 percent.
• Long lead-gen forms (10+ fields) routinely sit between 75 and 85 percent.
• Short newsletter signups (1 to 2 fields) can hit 30 to 40 percent abandonment.
• B2B demo request forms typically land between 60 and 80 percent.

The takeaway: abandonment is normal. The goal is not zero — it is to find the specific field or step where drop-off concentrates and fix that.

What are the most common causes?

• Asking for sensitive fields (phone number, company size, credit card) too early
• Validation errors that appear only on submit instead of on blur
• Required fields not visually marked as required
• A submit button that gives no feedback during a slow API call
• Hidden errors above the fold that the user cannot see
• Mobile keyboards covering the next field
• Surprise fields revealed only after the user starts typing
• Captchas that fail silently or require multiple attempts

How do you diagnose where users drop?

A field-level funnel breaks the form into stages and reports drop-off per field:

1. Track focusin and the first input event on every field
2. Record the order in which fields are touched
3. For each field, compute the percentage of starters who reached it but never reached the next one
4. Overlay session replays on the worst-performing field to see why

This usually reveals that 60 to 80 percent of total abandonment is concentrated on one or two fields — typically phone, address, or password.

How can you reduce form abandonment?

• Cut every non-essential field (each field added increases abandonment ~5 to 10 percent)
• Use inline, on-blur validation with clear error copy
• Persist partial form state to localStorage so reloads do not lose data
• Replace text inputs with native pickers on mobile (date, tel, email)
• Use a single-column layout and avoid multi-column forms
• Show a progress indicator on multi-step forms

How it relates to CloseTrace

CloseTrace measures form abandonment per field automatically and pairs each abandoned session with the matching replay, so the team can recover the lead by email and fix the problem field at the same time.