Lorixen.
EN

Marking a Form Submission as a Key Event in GA4

Short answer: Decide first what signal proves an enquiry was sent: a visit to a thank-you page, a custom event fired by your form, or a Google Tag Manager trigger. The thank-you page route is simplest: create a new event in GA4 Admin that matches page_view where the page location contains /thank-you, give it a clear name such as generate_lead, then mark that event as a key event. Test it in DebugView or Realtime, set the counting method to once per session if reloads inflate the numbers, and import it into Google Ads if you advertise.

Why the built-in form_submit is not enough

GA4's enhanced measurement can log form_start and form_submit automatically, as described in Google's enhanced measurement help. It sounds ideal but has gaps:

  • It may fire when someone presses Send even if validation then fails.
  • It often misses forms that submit through JavaScript without a page reload, which is how many modern form plugins work.
  • It can count search boxes, newsletter fields and login forms as "forms" too.

So a form_submit count rarely matches the enquiries in your inbox. Use it as a hint, not as your key event.

Three ways to capture a real enquiry

Method Best when Weak spot
Thank-you page Form redirects to its own URL after success Reloads and direct visits to that URL count
Custom event from the form Plugin or developer can push an event on success Needs code or a plugin setting
GTM trigger You already use Tag Manager Success detection must be reliable

Option A: Thank-you page

If your form sends people to something like /enquiry-received/, you already have a dependable signal. Make sure that page is excluded from search engines with a noindex tag and is not linked in menus, so the only way in is through the form.

Option B: Event pushed by the form

Many form plugins can run a snippet on successful submission. Your developer adds a line that sends an event such as generate_lead with useful parameters, for example form_name: quote_request. This works for forms that show a success message without changing the URL.

Option C: Google Tag Manager

In Tag Manager, create a trigger that fires only on success: either a custom event the form pushes to the data layer, or an element visibility trigger watching the success message. Attach a GA4 event tag with your chosen event name. Avoid the generic Form Submission trigger unless you have confirmed it ignores failed attempts.

Creating the event in GA4 (thank-you page route)

  1. In GA4, open Admin, then under Data display choose Events.
  2. Select Create event, then Create.
  3. Name it, for example generate_lead. Use letters, numbers and underscores only.
  4. Under matching conditions, add event_name equals page_view.
  5. Add a second condition: page_location contains /enquiry-received.
  6. Leave "Copy parameters from the source event" ticked so page details come through.
  7. Save.

The new event only starts appearing after matching visits happen, so submit a test enquiry once it is saved.

Marking it as a key event

Once GA4 has seen the event at least once, it appears in the Events list. Open Admin, then Key events, and either toggle the event as a key event from the Events list or choose New key event and type the exact event name. Typing the name in advance works too if you want it counted from the first occurrence.

Give it a value if you want reports to show estimated lead value. For example, if roughly one in five enquiries becomes a job worth around £500, a value of £100 per lead is a reasonable working number.

Preventing duplicates

Thank-you page tracking counts every load of that page. Problems appear when someone refreshes, bookmarks it, or presses back and forward. Reduce double counting by:

  • Counting method: in the key event settings, choose "Once per session" instead of "Once per event". A visitor who reloads the page five times then counts once.
  • Redirect after success only: make sure the form does not redirect when validation fails.
  • Custom event with a guard: if a developer pushes the event, they can store a flag in the browser so it fires only once per submission.
  • Exclude internal traffic: your own test submissions should be filtered out once testing is done.

Testing with DebugView and Realtime

  1. Install the Google Tag Assistant extension or enable debug mode in Tag Manager preview.
  2. Open your site and submit a test enquiry.
  3. In GA4, open Admin, then DebugView. Google's DebugView guide explains how devices appear there.
  4. Look for your page_view followed by generate_lead with a key event marker.
  5. Check Realtime as well, which shows key events in the last half hour.

Standard reports can take up to a day or two to show the numbers, so do not worry if they look empty straight after the test.

Importing into Google Ads

If you run search ads, importing the key event lets Google Ads report and optimise on real leads:

  1. Confirm the GA4 property is linked to your Google Ads account in GA4 Admin, Product links.
  2. In Google Ads, go to Goals, then Conversions, then create a new conversion action.
  3. Choose import, then Google Analytics 4 properties, and select generate_lead.
  4. Decide whether it should be a primary action used for bidding.

Avoid importing the same enquiry twice, for example from GA4 and from a separate Google Ads tag, or campaigns will report double the leads.

FAQ

What is the difference between a key event and a conversion in GA4?

Key events are what GA4 now calls the actions you mark as important. Conversions is the term used in Google Ads for the actions it reports on and optimises toward.

How long until the key event shows in reports?

DebugView and Realtime show it within minutes. Standard reports usually catch up within a day or two.

Our form has no thank-you page. What now?

Use a custom event pushed by the form on success, or a Tag Manager trigger based on the success message appearing.

Should we use the automatic form_submit event?

Only as a rough signal. It can miss JavaScript forms and count failed attempts, so it rarely matches real enquiries.

Want enquiries counted accurately across GA4 and Google Ads? Let us know and we will set up and test the tracking.

Sources

WhatsAppBook a call