GA4 Event Tracking Setup | Deciding What to Measure

In GA4 everything is an event. A page view is an event, so is a form submission, so is a purchase. That flexibility is powerful but comes at a price: if you do not build the structure, GA4 cannot give you a meaningful report.

Question first, setup second

Event setup should start not with which events to add but with which question you are trying to answer. “Which service page produces more enquiries”, “where do users abandon the form”, “which campaign brings qualified visitors” — questions like these define the events to measure by themselves.

When this step is skipped the outcome is always the same: dozens of events collected, none serving a decision. Measurement is costly work; only measure what will change a decision.

Naming discipline

Event names have to be consistent. If events doing the same job are sent under different names on different pages, reports fragment and the total never appears.

Using Google’s recommended names matters too: there are expected names for events such as purchase and add-to-cart, and when you use them GA4’s built-in reports work. Invent your own name and the data arrives but never shows in standard reports.

Parameters

The parameters an event carries matter as much as the event itself. Which form a submission came from, the value of a purchase, which button was clicked — these travel as parameters.

Without parameters you are left with a single total and no way to break it down. Knowing that forms were submitted 200 times is useless on its own; knowing which form was submitted how many times changes decisions. Custom parameters also have to be registered in GA4, otherwise they are collected but never visible in reports.

Choosing key events

Marking an event as a key event turns it into a conversion and makes it importable into advertising. Because that choice directly affects the bidding strategy, it should be made carefully.

The rule is simple: a key event should be the action that actually earns money. Intermediate signals such as scrolls, video plays and page views can be measured but should not be key events. When they are, the conversion count looks high while the algorithm hunts the wrong audience.

How do we start? First we discuss which questions you need answered, then I design the event and parameter structure around them. I send the setup plan in writing. You can reach me from the contact page.

Frequently Asked Questions

How many events can I define in GA4?

There is a generous technical limit, but the real limit is how many you can manage. A small set of well-defined events is always more useful than a large scattered one.

Should I turn off enhanced measurement events?

Leaving them on is usually fine, but automatic events such as scroll and outbound click can clutter the data. Turning off ones you do not use keeps reports readable.

I set up an event but it does not appear in GA4. Why?

Two common causes: the event is sent but the parameter is not registered as a custom dimension, or processing delay. If it appears in the realtime report, the setup is working.