The form_start interaction event
form_start is an enhanced-measurement event that fires the first time a user interacts with a form on the page — well before form_submit. The pair lets you measure form abandonment: how many people begin a form versus how many finish it. It is captured automatically when form interaction tracking is enabled, with parameters describing the form, not the entered data. It turns 'did they submit' into 'where did they drop'.
What it captures
When form interaction tracking is on, GA4 logs form_start on the first interaction with a form and form_submit on submission (enhanced measurement). Parameters describe the form — an id or name — not what was typed. The signal marks intent: the user engaged with the form, regardless of whether they completed it.
Measuring abandonment
The gap between form_start and form_submit is your abandonment view: a high start-to-submit drop points to forms that are too long, validate harshly, or ask too much. Use it to prioritise which forms to simplify. Because no field contents are captured, you get the behavioural signal without touching the personal data users enter — the only safe way to study form drop-off.
- form_start = first interaction; form_submit = submission
- Gap between them quantifies abandonment
- Parameters identify the form, never field values
How it appears in analytics and logs
Many form_start events with few form_submit events mean users begin but abandon the form — a length, validation, or friction problem rather than discovery.
Diagnostic use case
Measure form abandonment by comparing form_start (began) with form_submit (finished), so you can see which forms lose users mid-way.
What WebmasterID can help detect
WebmasterID can record a form-begin signal as a first-party event tied to a form identifier, without capturing any field values typed by real users.
Common mistakes
- Capturing entered field values alongside the event.
- Reading form_start as a completed submission.
- Not enabling form interaction tracking, missing the start signal.
Privacy and accuracy notes
form_start records that interaction began and which form, never the field contents. Keep parameters to form identity; entered values must stay out of analytics.
Related pages
- The form_submit event
A form_submit event records that a visitor submitted a form — a signup, contact, or checkout form. It is one of the highest-value events because it usually maps to an intent or conversion. The hard rule is that the submitted field values (name, email, message) must never enter analytics: you record that a form was sent and which one, not what was typed.
- Enhanced measurement (auto events)
Enhanced measurement is a GA4 setting that automatically collects a set of interaction events — scrolls, outbound clicks, site search, video engagement, file downloads, and form interactions — without extra code. It is convenient but not magic: it only covers standard patterns, can over- or under-count, and each option can be toggled. This page explains what it does and its limits.
- The generate_lead event
generate_lead is a GA4 recommended event that fires when a visitor expresses interest in a product or service — typically a form submission for a quote, demo, or contact. It can carry currency and value to express an estimated lead worth. It is the core conversion event for lead-generation sites, but a raw lead count says nothing about lead quality.
- CTA tracking (docs)
Track form engagement without field data.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.