Find Why Visitors Abandon Your WordPress Forms

A contact form that gets 400 views and 12 submissions looks like a traffic problem, until you find out that 150 visitors started typing and left at the same field. Most WordPress sites cannot tell the difference, because page analytics only count page views. The form itself stays a black box.

This guide explains how to measure a WordPress form as a funnel, what the numbers mean, and how to find the one field that costs you the most submissions, without cookies and without storing anything visitors type.

Why page analytics do not explain form abandonment

Google Analytics shows that people visited the page with the form. It does not show how many of them touched the form, which field they stopped at, or which field produced a validation error. You can set up form events yourself in Tag Manager, but that takes work per form and usually needs cookies and consent.

A form has its own funnel: viewed, started, submitted. The gap between each step tells you something different.

• Viewed but not started: the form is not convincing, too long at first glance, or placed too low.
• Started but not submitted: something inside the form stopped the visitor. This is where per-field data matters.
• Submitted with errors first: validation messages are annoying people before they succeed.

The metrics worth tracking per form

Dreamfox Form Analytics records, for each form:

• views, starts and successful submissions
• start rate, completion rate, conversion rate and abandonment rate
• drop-off per field: the last field a visitor touched before leaving
• validation errors per field
• average time per form and per field
• an optional desktop, tablet and mobile breakdown
• trends per day, week or month

A successful submission only counts when the form confirms it, for example Contact Form 7's "mail sent" event. A submit attempt that fails validation is not counted as a success.

How abandonment is defined

A visitor abandoned a form when they started interacting with it (focused or filled a field) but left the page without a successful submission. The last field they touched gets the drop-off. Add those up per field and the table points at the field that loses the most people, for example a phone number field that is marked required.

The dashboard turns this into plain statements such as "Field phone-number causes 24% of all form abandonment". These conclusions come from fixed rules computed on your own server. No external AI service is involved and no data leaves the site.

What to fix first

Work through the funnel in this order:

1. Low start rate: shorten the visible form, move it higher on the page, and make the first field easy.
2. One field with a high drop-off share: ask whether you need it. Make it optional, split the question, or explain why you ask.
3. High validation errors on a field: loosen the format (phone numbers with spaces, postal codes in other countries) or show a clear example.
4. Slow fields: a field with a long average time usually means the visitor is unsure what to enter. Add a hint.
5. Mobile drop-off much higher than desktop: check the field types on a phone, tap targets and the keyboard that opens.

Change one thing at a time and watch the weekly trend, so you can link a change to the result.

Privacy: what is and is not stored

Form analytics only makes sense if you can use it without a consent banner debate. Form Analytics is built to store as little as possible:

• It never stores what visitors type, names, email addresses, phone numbers, IP addresses, cookies or raw user agents.
• Each form view gets a random identifier that lives for a single page view and is not linked to a person.
• Retention is yours to choose: 7, 30, 90, 180 or 365 days, and older data is deleted automatically every day.
• Do Not Track and Global Privacy Control are respected in the browser and enforced again on the server.
• Administrators are excluded from the statistics by default, and you can also exclude all logged-in users.

Whether you need a consent banner for your site stays your decision, but nothing here relies on cookies or persistent identifiers.

Which forms are supported

Contact Form 7 and Elementor Forms (Elementor Pro) are supported and detected automatically. If one of them is missing, nothing breaks. Other form plugins such as WPForms, Gravity Forms and Fluent Forms are not supported yet, so check this before you install if that is what you use.

Set it up in five minutes

1. Install and activate the plugin.
2. Open a page with a Contact Form 7 or Elementor form. Tracking starts right away.
3. Open Dreamfox Analytics in the admin menu and wait for the funnel to fill.
4. Review Settings for retention, Do Not Track and which users to exclude.
5. Come back after a week of traffic and look at the field with the highest drop-off.

The tracking script is one small file of about 4 KB gzipped. It loads only when a supported form plugin is present, batches events (at most one request every five seconds per page) and sends them when the visitor leaves, so it does not block navigation.

Free alternatives and when they are enough

Tag Manager events or a heatmap tool can answer the same question. They need setup per form, often cookies, and they show behaviour on the page more than field-level drop-off. If you run one form and already have a consent setup, that route works. If you manage several sites or forms for clients, an automatic per-form funnel saves the repeated configuration.

Related reading

Better forms are one part of a better site for clients. If you hand sites over, see how to let clients edit text without breaking the layout. More plugins are on our plugins page, and the product page for this plugin is Dreamfox Form Analytics.