How Do You Track Form Submissions on Your Website?
The short answer
Section titled “The short answer”Form tracking counts four things: how many people start a form, how many hit an error, how many give up, and how many submit. Then it follows each submission to its outcome, like a booked job or a dead lead. Set it up in your analytics tool, test it, and check every month that the analytics count matches the submissions that actually reached you.
What this means
Section titled “What this means”Picture a made-up roofing company, Summit Peak Roofing, with a quote form. In one month:
- 200 people start the form
- 40 see an error, mostly on the phone number field
- 120 leave without finishing
- 80 submit
- 78 submissions reach the office inbox
- 30 become inspections and 12 become signed jobs
Each number tells the owner something different. The error count points to a broken phone field. The gap between 80 and 78 means two submissions got lost somewhere. The last two numbers show whether the form brings in real work.
This page is also the main home for outline line 21.6.2 (form completion), which asks for the same measures: starts, errors, abandonment, and submissions.
Why it matters
Section titled “Why it matters”- Submissions alone hide the problem. If you only count submissions, you can’t tell whether a drop came from fewer visitors or a broken form.
- Errors cost leads quietly. A field that rejects real phone numbers can turn away customers who never call to complain.
- Analytics can be wrong. Double-counted events, missing tags, or spam can make numbers look better or worse than they are. Checking against your inbox catches it.
- Leads aren’t sales. A form that brings in many submissions but few jobs may be attracting the wrong people (see 13.7.5 Appointment and Sales Tracking).
Who this applies to
Section titled “Who this applies to”Any business with a form on its website. If your main action is calls, track calls too (see 12.3.3 Call Tracking).
How to do it
Section titled “How to do it”- List every form. Use your form register (see 13.5 Website Forms). Give each form a clear name.
- Track starts and submissions. Google Analytics 4 (GA4) enhanced measurement can send a form_start event the first time someone uses a form in a session and a form_submit event when they submit. Turn it on in your data stream settings, then test whether those events fire correctly on your forms.
- Use a confirmation signal you trust. The most reliable submission count usually comes from something that only happens after a successful send, like a thank-you page view or a success event from your form tool. Mark that as a key event (see 13.7.1 Analytics Setup and Measurement Plan).
- Track errors. Ask your developer or form tool to send an event when validation fails, with the field name but never what the person typed.
- Measure abandonment. Abandonment is starts minus submissions. Look at it by form and by device. A big gap on phones often means the form is hard to use on a small screen.
- Make form parameters usable. GA4 sends details like form ID and form name with these events, but Google says you need to create custom dimensions to use them in reports.
- Keep personal information out. Never send names, emails, phone numbers, or message text to analytics.
- Tag where leads come from. Capture the source and campaign with each submission, using tagged links and hidden fields if your form tool supports them (see 15.8 Lead-Source Tracking).
- Test it. Submit each form yourself, with and without errors. Confirm the events show up in your analytics real-time or debug view, and the submission reaches the right place (see 13.2.8 Form Delivery).
- Reconcile monthly. Compare analytics submissions with what actually arrived in your inbox or customer relationship management (CRM) system. Investigate any big gap.
- Record outcomes. For each submission, mark what happened: contacted, booked, sold, lost, or spam.
What proof to keep
Section titled “What proof to keep”- A tracking sheet listing each form, the events tracked, and the date tested
- Screenshots from the test showing events in analytics
- Monthly reconciliation notes: analytics count, inbox count, and any gap explained
- A monthly summary of starts, errors, submissions, and outcomes
Store these in your website records folder.
Common mistakes
Section titled “Common mistakes”- Counting button clicks as submissions. People click submit and then hit an error. Count successful sends.
- Thank-you pages people can reach without submitting. If the page is linked from menus or shows up in search, visits inflate your count.
- Counting spam. Bots that get through your filter look like leads. Mark spam in your outcomes so it doesn’t skew results.
- Sending what people typed to analytics. That can put personal information where Google prohibits it.
- Never reconciling. Analytics and the inbox drift apart and nobody notices for months.
- Stopping at submissions. The question that matters is how many became paying jobs.
When to get help from a pro
Section titled “When to get help from a pro”An analytics specialist or web developer: if your counts don’t match your inbox or you can’t track errors. Ask:
- Does my submission event fire only after a successful send?
- How can I track form errors without capturing what people type?
- Why does my analytics count differ from my inbox?
Bill’s note
Section titled “Bill’s note”[Bill: add a short story or lesson here. For example, a client whose form had a broken field that only showed up in error tracking, or a time analytics and the inbox didn’t match and what the cause was.]
If you’d rather have this done for you, SiteSmarty sets up form and call tracking for local businesses.
How I did this for SiteSmarty
Section titled “How I did this for SiteSmarty”- [Date I did this:]
- [What I actually did, step by step: which forms I track on the SiteSmarty site, the events I used, and how I tested them]
- [What it cost and how long it took:]
- [What surprised me or what I’d do differently:]
- [Screenshot or photo to add, with private info blurred: the form events in analytics and the monthly reconciliation note]
- [Result so far:]
Questions people ask
Section titled “Questions people ask”How do I track form submissions in Google Analytics? Use a signal that only happens after a successful send, like a thank-you page view or a success event, and mark it as a key event. Enhanced measurement can also track form starts and submissions.
How do I know if people start my form but don’t finish? Compare form starts to submissions. The gap is your abandonment. Check it by device.
Should I use a thank-you page to track submissions? It’s a reliable method, as long as people can only reach that page by submitting the form.
Why don’t my analytics form counts match my inbox? Common causes are double-counted events, spam, ad blockers that stop tracking, and emails that never arrived. Reconcile monthly to find out.
How do I connect form leads to sales? Capture the lead source with each submission and record what happened to each lead in your customer records.
Audit check
Section titled “Audit check”- Question: Are form starts, errors, abandonment, and successful submissions tracked for each form, reconciled with real submissions, and tied to outcomes?
- Pass looks like: Each form named and tracked. Submission counted only after a successful send. Errors tracked without capturing what people typed. Abandonment reviewed by device. No personal information in analytics. Monthly reconciliation done. Outcomes recorded for each lead.
- Fail looks like: Button clicks counted as submissions. No error tracking. Thank-you page reachable without submitting. Spam counted as leads. No reconciliation. No outcomes.
- Evidence to collect: The tracking sheet, test screenshots, monthly reconciliation notes, and the outcome summary.
Where this fits
Do this first: 13.7.1 Analytics Setup and Measurement Plan, 13.5 Website Forms, 13.2.8 Form Delivery
Do this next: 13.7.5 Appointment and Sales Tracking
Related pages: 13.3.5 Conversion Paths, 13.6 Landing Pages and Funnels, 15.8 Lead-Source Tracking, 16.1 Lead Intake, 21.6 Reviewing Calls and Forms, 21.7 Funnel Review, 21.10 Conversion Rate Testing
Sources
- Google Analytics Help, "Enhanced measurement events" (checked October 16, 2026)
- Google Analytics Help, "Mark events as key events" (checked October 16, 2026)
- Google Analytics Help, "Best practices to avoid sending Personally Identifiable Information (PII)" (checked October 16, 2026)
This page explains general rules and Bill's own experience. It is not legal, tax, or insurance advice. Talk to a qualified professional about your situation.
