Learn · How-To

How to Track Form Submissions and Key Actions

Traffic numbers are the least useful thing analytics gives you. What matters is whether anyone did something: submitted an enquiry, downloaded the thing, started a call. This guide covers capturing those actions as events, and then the harder judgement — deciding which ones are actually conversions rather than just activity you happened to be able to measure. It assumes GA4 is already connected through Tag Manager.

1. 1

   List the actions that matter before you build anything

   Write down the handful of actions that indicate real commercial interest on your site. For most B2B businesses that is an enquiry form, a document download, a call click and possibly a pricing page visit. Keep the list short. A site measuring thirty events is usually a site where nobody can say which three matter.

2. 2

   Find out how your forms actually submit

   Before configuring anything, determine whether your form does a genuine page load to a thank-you page, submits via JavaScript without navigating, or is an embedded third-party widget in an iframe. These three cases need three different approaches, and guessing wrong produces a trigger that silently never fires.

3. 3

   Use a thank-you page trigger where you have one

   If submission lands the visitor on a distinct confirmation URL, that is the most reliable signal available. Create a trigger on that page view and send a GA4 event from it. It survives form plugin changes, which the alternatives often do not.

4. 4

   Use the form submission or element visibility trigger where you do not

   For forms that submit without navigating, GTM offers a form submission trigger, and for confirmation messages that appear in place, an element visibility trigger watching the success message. Element visibility is frequently the more dependable of the two, because it keys on what the visitor actually sees.

5. 5

   Name events consistently and deliberately

   Pick a naming convention and apply it. Event names in GA4 are permanent in the sense that historic data keeps whatever you called it at the time, so renaming later splits your reporting in two. Lowercase with underscores, describing the action rather than the page, is a sane default.

6. 6

   Send useful parameters with each event

   An event that only says "a form was submitted" answers almost nothing. Send which form, which page, and any non-personal qualifier you have. Do not send names, email addresses or phone numbers into analytics — that is both a privacy problem and against the platform terms.

7. 7

   Test every single one by doing it yourself

   Submit each form, click each call link, download each document, while watching Preview mode and GA4 Realtime. Testing one and assuming the rest follow is how a site ends up with three working events and two that were never connected.

8. 8

   Mark only the real ones as key events

   In GA4, mark as key events only the actions that represent genuine commercial intent. Everything else stays an event you can look at. Marking every measurable action as a conversion is how a business ends up reporting four hundred conversions a month and no new customers.

9. 9

   Document what each event means

   Write a one-line definition for each event somewhere outside the tools. Six months from now somebody will ask whether a number includes a particular form, and the only honest answer will be whatever you wrote down.