Measurement and analytics
GA4: Measure a Received Enquiry, Not Just a Click on Send
A click, a rejected attempt and a received enquiry don't prove the same thing. Here's how to choose the signal to send to GA4 and check it before you rely on it.
Does your GA4 report show more “forms sent” than your inbox holds enquiries? The gap often comes from the signal you chose. A visitor who clicks “Send” is expressing an intention. A received enquiry is a fact: the information reached you.
This article sets out principles and a method for choosing what GA4 should count. It reports no test: AETHER has not carried out any form-tracking test, and we show no screenshot or result here. If you first want to understand what each tool does, start with our article on GA4 and Google Tag Manager.
Three moments that don't prove the same thing
Between the form appearing and your notification email, several things happen. Each can be detected, but each proves something different.
Three moments that don't prove the same thing
| Moment | What it proves | What it doesn't prove |
|---|---|---|
| Click on Send | The visitor wanted to send | That the form was valid, that the server accepted it or that you received it |
| Rejected attempt | The visitor tried, but a field was missing, a validation failed or the server returned an error | Any enquiry at all. Counting this attempt as an enquiry inflates your results |
| Enquiry received | The site confirmed the enquiry was recorded | That the enquiry leads to a sale: a lead is not revenue |
Only the third row matches what most small businesses call a lead. The click is useful for understanding the journey, for example to spot a form that is often abandoned. It shouldn't be used as the result.
Why automatic tracking can count too early
GA4 can collect form events through enhanced measurement. Google describes two events, form_start and form_submit, which let you compare how many users started a form with how many submitted it. These options can be turned off in the enhanced measurement settings.
Our judgment is this: a submit event detected in the browser describes what the browser saw, not what your server accepted. Depending on how the form is built, those two moments may not coincide.
Google Tag Manager shows the nuance well. Its form submission trigger has a “Check Validation” option. According to the documentation, when it is off, the trigger fires whenever a user attempts to submit the form, even if the server then rejects the submission. When it is on, the trigger fires only if the form is successfully validated. That validation happens in the browser: in our view, it doesn't confirm that the server recorded the enquiry.
When the form is handled by code that overrides the usual submit behaviour, Google offers another route: the custom event trigger, designed for interactions that standard tracking methods can't handle.
Choosing the success signal
The question to ask whoever built the form is simple: what is the first moment at which the site knows for certain that the enquiry has been recorded? That moment should produce the signal. Depending on the form, it could be a confirmation response from the server, a thank-you page reached only after success, or a message the site pushes to the data layer at that precise instant.
A few rules of method:
- One clear event name. For example “enquiry received” in your measurement plan, rather than several variants depending on the button clicked.
- Reserved for real receipt. The event you designate as a key event should never fire on a click or on a rejected attempt. Any collected event can become a key event, so GA4 won't check for you that the signal is the right one.
- No guessing when in doubt. If the outcome of the submission is unknown, for example after a network error, it's better to count nothing than to guess a success.
- One submission, one signal. Plan for what happens when the visitor double-clicks or reloads the confirmation page. No tool guarantees the absence of duplicates by itself: that gets checked on your form.
- Real enquiries are the reference. What lands in your inbox or tracking tool is the benchmark. GA4 gives a partial view, limited among other things by visitors' consent choices and by blockers.
No personal data in measurement
The form contains personal information. Measurement doesn't need it to count. A generic event such as “enquiry received” is enough: no name, email, phone number or typed text needs to travel to GA4 or GTM. Google asks you to avoid sending Analytics information that could personally identify a user, and specifically mentions data entered in form fields.
One point deserves attention in GTM: the form submission trigger automatically populates built-in variables, including the form text. That's no reason to pass them along. Send as little as possible and check what actually leaves the site.
This approach is consistent with our principle for measurement: the visitor's choice governs analytics, and measurement isn't a way to copy the content of enquiries. Final decisions depend on the published privacy policy and on each visitor's choice; this text is neither legal advice nor a compliance certification.
Checking before you trust the numbers
Once the signal is defined, checking is part of the job. GA4 offers two tools: the Realtime report, which shows events triggered in the last 30 minutes, and DebugView, which displays the events of an individual user.
A reasonable verification plan covers at least:
- an enquiry genuinely accepted, which must produce one event;
- a rejected attempt (missing field, error), which must produce none;
- a double click or a reload, which must not produce two enquiries;
- a visitor who declines analytics, for whom nothing should be sent;
- a comparison, over a short period, between GA4 events and the enquiries actually received.
We describe an approach here without presenting it as tested by AETHER. Every site, form and provider needs its own checks.
Frequently asked questions
Can I rely on enhanced measurement for forms?
It gives a first look at form starts and submissions, and Google notes that its parameters appear in reports only if you create custom dimensions. It doesn't confirm on its own that an enquiry reached you. To decide on a budget or a campaign, define a real-receipt signal.
Should GA4 show exactly the same number as my inbox?
No, and it doesn't promise to. Consent, blockers and network losses limit measurement. What matters is a gap you understand and that stays stable, not a perfect match.
Is a GA4 key event the same as a sale?
No. A received enquiry is a lead. It becomes a sale only after your own follow-up steps, which GA4 can't see without additional setup.
Next step
Want your reports to reflect the enquiries you really receive? Our measurement and analytics service starts with a measurement plan: which action counts, which signal confirms it and how to check it. The first conversation clarifies your form, your access and your consent choices. To tie this data to your campaigns, see also our article on Google Ads budgeting.