Qwenvo

Form analytics: read drop-off to find the question that loses people

By the Qwenvo team · · 3 min read

Form analytics should answer one question: where do people give up? On Qwenvo, visit analytics and drop-off analytics show how many people opened your form and where the others stopped, free for every account. Read the drop-off first, fix the question that loses people, then measure again.

The numbers worth watching

  • Visits: how many people opened the form. If visits are healthy and submissions are not, the problem is inside the form.
  • Completions: how many people finished, compared with how many arrived.
  • Drop-off: where the people who did not finish stopped. This is the one you can act on.

Insights is a separate view: charts, averages and NPS for the answers people did give.

How to read a drop-off chart

  1. Find the cliff. Look for the one question where the line falls most, not a gentle slope.
  2. Read that question like a stranger. Is it personal, hard to answer, or asking for something not at hand, like an ID number?
  3. Check what came before. A cliff on question six can be caused by the length promised by questions one to five.
  4. Try it on your phone. Long dropdowns and uploads are harder on a small screen.

Fixes for the common cliffs

  • A sensitive question (income, phone, address): make it optional, move it to the end, or say why you ask.
  • A big open text box: replace it with Multiple choice plus an optional Other.
  • A file upload: make it optional or ask for it after the main form.
  • A long page: split with New page blocks and turn on the progress bar. See multi-page forms and progress bar.
  • Irrelevant questions: use conditional logic so people skip what does not apply. See conditional logic.

Change one thing at a time

Edit the single worst question, publish, and wait for enough new visits to see a difference. Changing five things at once means you never learn which one worked. With 90-day version history you can always see what the form looked like before an edit.

Pair analytics with partial submissions

Drop-off tells you where. Partial submissions show what people typed before leaving, as incomplete rows in Submissions. Together they answer where and why. See free partial submissions, and form abandonment fixes for the causes.

Add your own analytics too

Qwenvo supports Google Analytics 4 and Meta Pixel for tracking from your site. Mention them in your privacy notice, and check you have any consent your region requires before loading them.

What it costs elsewhere

On Tally, visit and drop-off analytics are Pro features ($29 a month, or $290 a year). Tally prices were checked on tally.so on 2026-10-29. Qwenvo includes them for $0.

A weekly routine that takes ten minutes

  1. Open the analytics for your most important form.
  2. Note the number of visits and completions.
  3. Find the question where most people leave.
  4. Write one guess about why, and one change to try.
  5. Make the change, publish, and note the date so you can compare later.

Do this every week for a month. Small fixes add up, and the log of your guesses shows you what your audience responds to.

When the problem is not the form

If almost nobody reaches the form, drop-off inside it will not help. Look at the page that links to it. Is the link clear, and does the page promise something the form delivers? A form that feels like a surprise loses people at once.

Do not chase a perfect number

A form that collects a long application will lose more people than a one-field newsletter signup, and that is fine. The goal is not the highest possible completion. It is a form where the people you want finish it, and where every question earns its place.

Questions people ask

What is a good form completion rate?

There is no universal number, because it depends on length, audience and how people found the form. Compare a form against its own earlier versions, not against someone else's average.

Why do I have visits but no submissions?

Compare visits with completions. If almost nobody gets past the first screen, the problem is the opening or the traffic you send. If many start and few finish, look at where drop-off peaks.

Does analytics include people who left early?

Drop-off analytics counts them, and partial submissions keep what they entered if you have the setting on.

Next step: open your busiest form's analytics and write down its worst question. Or make a free account to start measuring.

Every feature, $0, no card.

See where people drop off