Form Conversion Rate Calculator

Start rate = starts ÷ views. Completion rate = completions ÷ starts. Overall conversion = completions ÷ views.

The identity that makes this useful: overall = start rate × completion rate. If overall conversion is 12% because 60% start and 20% finish, the problem is inside the form. If it's 12% because 15% start and 80% finish, the problem is the form's placement, headline, or first impression.

Form conversion rate = completed submissions ÷ form views × 100. It is the share of people who saw the form and went on to submit it. HubSpot's form reports use exactly this: submissions divided by views of the pages the form appears on.

On its own, that number tells you something is wrong but not where. The calculator splits it into two stages with a simple identity: overall conversion = start rate × completion rate, where start rate = starts ÷ views and completion rate = completions ÷ starts. Each stage fails for different reasons, so each needs a different fix.

Illustration, using the calculator's defaults. A form gets 5,000 views, 1,400 starts and 620 submissions.

Start rate = 1,400 ÷ 5,000 = 28.0%. Completion rate = 620 ÷ 1,400 = 44.3%. Overall conversion = 620 ÷ 5,000 = 12.4%, which checks out: 0.28 × 0.443 = 0.124. Abandonment is 100% − 44.3% = 55.7%, meaning 780 people started and left, while 3,600 never started at all.

Which fix is worth more? Raise the start rate from 28% to 33% and, at the same completion rate, submissions go to about 731 (5,000 × 0.33 × 0.443). Raise the completion rate from 44.3% to 55% instead and they go to 770 (5,000 × 0.28 × 0.55). Both are hypothetical lifts, but the arithmetic shows how to compare them: multiply through the funnel rather than looking at either rate in isolation.

Definitions vary by tool, and a changed definition can move your rate more than any design change. Settle them before you compare numbers.

A view in HubSpot is a view of a page the form sits on, which counts people who never scrolled down to it. Google Analytics 4's enhanced measurement fires form_start the first time a user interacts with a form in a session and form_submit when it is submitted. Zunoform counts a view when the form loads, a start on the respondent's first answer, and a completion on submission; the form owner's own visits are left out of all three.

A completion should mean a successful submission. Counting clicks on the submit button includes attempts that failed validation.

A low start rate is a first-impression problem. People have to see the form, understand what it is for, and judge the effort as worth it. Check whether the form is below the fold on mobile, whether the first question is easy (a choice question is easier than a text box asking for their email), and whether the page says how long it takes.

A wall of fields visible at once can put people off before they begin. A one-question-at-a-time layout shows less up front; whether it helps your audience is something to test, not assume.

A low completion rate is an inside-the-form problem. The aggregate number only tells you a problem exists; per-question drop-off tells you where. Look for the one question with the biggest fall: often something people must go and look up, information they didn't expect to give, or a question that doesn't apply to them with no way to skip.

Cut questions you won't act on, hide ones that don't apply with conditional logic, and test the form on a phone. Our form completion rate article covers published benchmarks and a field-by-field friction checklist, so we don't repeat them here.

Enter a value per completion and the calculator multiplies it by the number who dropped out after starting. With the defaults and a $50 value, that is 780 × $50 = $39,000.

Read that as a ceiling, not a forecast. It assumes every abandoner would have converted at full value, and many were only browsing or were never a fit. A more honest figure applies the share you think you can recover. If a fix brought back 1 in 5 abandoners, that is 156 submissions, or $7,800 at $50 each (an illustration, not a benchmark).

There is no universal number. A checkout form, a newsletter signup and a job application differ in intent, length and traffic source, and view-based rates also swing with page design, because a form lower on a long page collects views from people who never reached it. Published averages rarely state which denominator they used.

The comparison that holds up is your own form against itself: the same definitions, before and after a change, or two versions shown to randomly split traffic. For starter-based completion benchmarks with their sources and limits, see our form completion rate article.

Skip it when the audience is captive, such as a mandatory HR form or an exam registration: completion matters, but views and start rate mostly measure how the link was sent. Be careful with very small numbers too. At 40 views, one extra submission moves overall conversion by 2.5 points.

And conversion is not the goal in itself. If a shorter form converts more but sales qualifies fewer leads, measure the next step as well, for example qualified leads ÷ views.

Illustration: you split traffic between the current form and a shorter version, and each gets 1,400 starts. The current form completes 620 (44.3%) and the shorter one 700 (50.0%). Entered into our A/B test significance calculator as starts and completions, that gives z = 3.03 and p ≈ 0.0025, a difference unlikely to be chance. With a tenth of the traffic, the same rates would not reach significance, so size the test before you start.

Most form tools report submissions; fewer report starts. In GA4 you can use form_start and form_submit from enhanced measurement, with form views from a page_view or a custom event when the form scrolls into view.

In Zunoform, each form's Summary tab has a Where people drop off panel with views, starts and completed submissions, plus how many respondents reached and answered each question, so you can fill in this calculator and find the leaky question in the same place. Partial responses are saved as people go (on by default), which also lets you follow up with someone who left an email before abandoning, if your privacy notice covers it.