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.
What this means
form_submit fires when a form is submitted. GA4's enhanced measurement can capture form interactions automatically (form_start and form_submit) for standard HTML forms. The event tells you the form was completed; paired with form_start it shows how many people began versus finished.
What to record — and not record
Record the form's identity (a form id, name, or destination) and the page it was on. Never record what the visitor typed: names, emails, phone numbers, and free-text are personal data and may be special-category data. Putting them in event properties turns analytics into a data-protection liability and is unnecessary for measuring conversions.
- Record: form id/name, page, success/fail
- Never record: field values, emails, free text
- Pair with form_start to measure completion
How it appears in analytics and logs
A form_submit event means a form was sent. Missing submits hide conversions; submits without matching form_start can mean validation or tracking issues on the form.
Diagnostic use case
Measure how often each form is submitted and where, so you can find drop-off and high-intent pages, while keeping every field value out of analytics.
What WebmasterID can help detect
WebmasterID supports tagged form events with stable ids and no field capture, so form_submit stays a clean conversion signal without ingesting any typed personal data.
Common mistakes
- Capturing field values into event properties.
- Only tracking submit, never form_start, so drop-off is invisible.
- Firing on client validation failure and over-counting submits.
Privacy and accuracy notes
Form field contents are personal data and must never become event properties. Record a form id or name only. WebmasterID's form tagging (data-wmid-form) captures the form identity, not its contents.
Related pages
- The click event and outbound clicks
A click event records that a visitor activated a link or element. The most common analytics use is the outbound click — a click on a link leaving your domain — which a normal page_view can never capture because the destination is another site. This page covers what to record on a click, how outbound detection works, and which properties stay privacy-safe.
- Conversion rate: definition and denominators
Conversion rate is the share of some base that converted. The trap is the denominator: conversions per session, per user, and per unique visitor give different numbers and mean different things. Without stating the base, a conversion rate is ambiguous — and comparing rates with different bases is meaningless.
- GDPR and web analytics: the practical picture
The GDPR governs processing of personal data of people in the EU. For analytics that means: identifiers and IP addresses can be personal data, consent is often required for cookie-based tracking, and minimisation matters. Cookieless, first-party, anonymised measurement reduces the surface — but this is a factual overview, not legal advice.
- Form & CTA tracking (docs)
Tag forms with ids, never field contents.
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.