Short answer: A “thank you” page is useful feedback for the visitor, but a page view alone is a weak count of successful enquiries. First verify that the form was accepted and reached the team. Then measure that confirmed action once, with a clearly named event or a tightly controlled success-page rule. Compare analytics with the actual inbox or form records before making spending decisions.
This is for a small service business with a quote or contact form. It builds on our GA4 measurement checklist and focuses on one easy-to-miss distinction: a visit to a URL versus an enquiry the business can act on.
Draw the journey before choosing an event
- Start: a visitor reaches the form, perhaps from a service page or social profile.
- Attempt: the visitor presses Submit. Validation or network errors may still prevent delivery.
- Accepted: the form system confirms success and stores or sends the enquiry.
- Received: the named person can find the message and knows the next action.
Count the accepted step as the measurement candidate; test the received step as an operational check. A button click is an attempt, and a generic page view may be neither. A public analytics question describes a thank-you URL that also appears after errors. That is a useful failure case to test, not proof that every form behaves that way.
Choose a signal your setup can actually support
- Confirmed form event: If the form exposes a reliable success event, have the site or analytics owner map that event to the specific lead form. Google’s GA4 key-event instructions describe narrowing a
form_submitevent to a named lead form before marking it as a key event. Check whether your form supplies the required name and whether the event fires only on success. - Success page: If the form redirects only after acceptance, a dedicated confirmation page can be a practical signal. Test direct visits, refreshes, back-button visits and error paths; a repeated page view must not silently become a second lead in your report.
- Manual baseline: If you cannot verify either signal, count enquiries in the form’s stored submissions or shared inbox while you fix the instrumentation. A smaller trustworthy count is more useful than a larger ambiguous dashboard number.
Hypothetical check: Submit one test enquiry with a distinctive non-personal label such as “QA October form”. Confirm one success message, one stored submission and one delivered notification. Refresh the confirmation page. If analytics adds another lead while the form record stays at one, the measurement rule needs work. This is a test pattern, not a reported result from this site.
Make the confirmation page useful to a person
Say what happened and what happens next: “We received your request. Our team will review the service area and reply through the contact route you provided.” Only promise a reply time if the team can meet it. Keep a visible alternative contact method for urgent or failed submissions, and avoid exposing the submitted personal details in the page URL or analytics events.
If the first problem is that form messages never arrive, work through the contact-form delivery checklist before polishing conversion reports. If you are still deciding what to ask, use the enquiry-form fields guide to remove unnecessary friction.
Review the numbers with an exception list
Once a week, compare confirmed form records, delivered messages and the analytics event. Note test submissions, duplicates and failed delivery separately. Do not treat a zero-difference target as automatic proof of accuracy: privacy choices, blocked scripts and configuration differences can affect analytics. The decision is whether the signal is reliable enough for the specific question you are answering, such as which service page to improve.
Source check: 6 October 2026. Product behavior is based on Google’s official GA4 documentation; the community example illustrates a possible failure mode. No test on Practical SaaS Lab’s own form is claimed.
