Form analytics is the measurement of how people interact with a form, field by field: how many see it, how many start it, how long each field takes, which error messages appear, where people give up and how many submit successfully. It turns a single number, form submissions, into an explanation of why the rest did not submit.
How form analytics works
It works at two levels of detail.
At form level, you track a few events: the form being seen, the first interaction with any field, and a confirmed successful submission. GA4’s enhanced measurement can send form_start and form_submit events automatically, though at the time of writing (October 2026) its submit event relies on the browser’s standard submit behaviour, so it can miss forms that send by JavaScript and can fire on attempts that fail validation.
At field level, you want to know which field someone was on when they left, how long they spent there and how often they corrected an entry. Specialist form analytics products measure this directly. Session recording tools such as Microsoft Clarity and Hotjar let you watch individual visits with what people type masked out. A developer can also send custom events for field focus and blur through Google Tag Manager.
The useful measures are start rate (starts divided by views), completion rate (successful submissions divided by starts), the field where abandonment most often happens, time per field, and how often each validation error is shown.
A typical finding: a quote form for a removals company loses most of its abandoners at the field asking for a full address, or at a phone number field that rejects a UK mobile number written with a space or with +44 at the front. Neither shows up in a submission count.
Why it matters
For a lead generation business the form is where the money is made or lost. If you pay for clicks, every person who starts the form and abandons it is spend that nearly paid off. Fixing a leaking field is often cheaper than buying more traffic.
There are UK privacy points to get right. Recording and form analytics scripts usually set cookies or read from the device, so they need consent under PECR like other analytics. They must also be configured to mask every input. Capturing what people type into name, email, phone or free-text fields is collecting personal data you did not need and have not told them about. Read your form findings together with form abandonment figures rather than in isolation.
Common mistakes
- Measuring only submissions, so there is no way to see where people stop.
- Counting a submit event that fired on a failed attempt as a lead, which inflates conversions and misleads Smart Bidding.
- Leaving keystroke capture switched on in a recording tool.
- Drawing firm conclusions from a couple of dozen recordings.
- Removing fields the sales team relies on without asking them, then receiving enquiries nobody can price.
How to act on it
Write the form’s journey as steps: page viewed, form started, each section of a multi-step form completed, success confirmed. Make sure each step is tracked reliably, with the final step fired only on a genuine success; a correctly configured form submission trigger or a success event from the form itself does that job.
Find the step or field with the largest loss, watch a sample of recordings at that point, change one thing and measure again, checking mobile separately because that is where most form problems hide. When I build landing pages for paid campaigns, field-level tracking goes in before launch so the first weeks of spend tell you something.