GA4 Events and Parameters, Explained

Imagine you run a small bakery and you want to know how your day went. The old way was to count how many people walked through the door. Useful, sure, but it misses almost everything that matters: who picked up a loaf and put it back, who asked about the wedding cakes, who paid and who left empty-handed. Counting footsteps tells you about traffic. It tells you nothing about behaviour.

That, in a nutshell, is the shift behind GA4 events. Where older analytics tools obsessed over how many pages people looked at, the current version of Google Analytics measures what people actually do. Every click, scroll, video play, form submission, and purchase is an "event". Once you understand events and the little tags of detail attached to them, called parameters, the whole platform suddenly makes sense. This guide walks through it all in plain language, no developer jargon required.

What an "event" actually means

In everyday speech, an event is something that happens. In analytics, the definition is reassuringly similar: an event is a single thing a person did on your site or app at a single moment in time. Loading a page is an event. Clicking a button is an event. Scrolling far enough down to reach the footer is an event. Buying something is an event. If you can describe an action in a short phrase, GA4 can almost certainly record it as an event.

This is a genuine break from how analytics used to work. The previous generation of Google Analytics was built around the pageview as its central unit. Events existed, but they were a bolt-on, treated as a separate category with their own clunky structure of category, action, and label. If you are migrating mentally from that world, our companion piece on what changed between GA4 and Universal Analytics is worth a read, because the event-first model is the single biggest difference between the two.

Why measuring actions beats counting pages

Think about a person reading a long article. In a pageview-centric world, that visit looks identical to someone who landed, glanced at the page for two seconds, and bolted. Both are "one pageview". But the reader who scrolled to the bottom, clicked a related link, and watched an embedded video clearly behaved very differently. Events let you see that difference. They turn a flat headcount into a rich picture of intent and interest.

The four families of GA4 events

Not all events are created equal, and the good news is that many of them require no work from you at all. Google sorts events into four broad groups, and knowing which is which saves a lot of confusion when you are staring at your reports for the first time.

The first group is automatically collected events. The moment you install GA4, it starts logging things like first visits, session starts, and app updates. You did nothing; they simply appear. The second group is enhanced measurement events, which you can switch on with a single toggle. These cover the common interactions almost every site cares about: scrolls, outbound clicks, site searches, video engagement, and file downloads. The third group is recommended events, which are Google's suggested names for common business actions like sign-ups or purchases. Using their names unlocks extra reporting features. The fourth group is custom events, which you define yourself for anything unique to your business.

Parameters: the detail behind every event

If an event is the headline, parameters are the supporting sentence. A parameter is an extra piece of information attached to an event that answers a question like which one, how much, or from where. On its own, a purchase event tells you a sale happened. Add parameters and you suddenly know the value of the order, the currency, the items bought, and the payment type. The event is the verb; the parameters are the adjectives and nouns that give it meaning.

Here is a homely example. Suppose someone plays a video on your homepage. The event might be called video_start. The parameters travelling alongside it could include the video's title, its length in seconds, and the percentage of the way through the visitor was when they clicked. Without parameters, you would know only that a video was played. With them, you know which video, and that distinction is the difference between a vague statistic and a decision you can act on.

Event parameters versus user properties

It helps to keep two ideas separate. An event parameter describes the action itself and changes from one event to the next: the page title, the search term, the order value. A user property, by contrast, describes the person and tends to stay stable across their visit: their preferred language, their membership tier, whether they are a returning customer. Both are useful, but they answer different questions. Parameters tell you about moments; user properties tell you about people.

From event to insight: registering and using parameters

Here is a wrinkle that trips up a lot of newcomers. Just because a parameter is being collected does not mean it will appear in your reports automatically. Most custom parameters need to be "registered" as a custom dimension or custom metric before GA4 will let you slice your data by them. It sounds fiddly, but it is a one-time setup, and we cover the mechanics step by step in our guide to custom dimensions and metrics in GA4.

Once registered, those parameters become powerful. You can build an audience of everyone who triggered a particular event with a particular value, then study them in a deep-dive exploration report. This is where the event model earns its keep: the same humble events you set up early on become the raw material for sophisticated analysis later.

Marking the events that matter as conversions

Not every event deserves equal attention. A scroll is nice to know about; a completed checkout is the whole point of being in business. GA4 lets you flag your most important events as "key events" or conversions, which pulls them into prominent reports and makes them available for measuring return on advertising spend. If you are setting up your first goals, our walkthrough on how to set up conversion tracking shows exactly which events to elevate and why.

How events actually get into GA4

You might be wondering how all this data finds its way from a button click into a report. There are two common routes. The first is the GA4 tag placed directly on your site, which handles automatic and enhanced measurement events out of the box. The second, and the one most growing businesses graduate to, is a tag management system that lets you create and adjust events without editing your website's code each time. Our guide on how to set up Google Tag Manager covers this comfortable middle ground, where marketers can ship new tracking without waiting on a developer.

Whichever route you take, the principle is the same. Something happens, the tag bundles up the event name and its parameters, and that little package is sent off to Google's servers where it is counted, stored, and made available for reporting. The beauty of it is that you rarely need to think about the plumbing once it is set up.

A naming convention saves you from future chaos

One piece of unglamorous advice will pay off enormously: decide how you will name events and parameters before you create dozens of them. GA4 treats Quote_Requested, quote_requested, and quoteRequested as three entirely different events, and once data is collected under a messy mix of names it is painful to untangle. Pick lowercase with underscores, keep names short and descriptive, and write your conventions down somewhere your whole team can see. Future you will be grateful.

What to track first if you are just starting out

It is tempting to track everything, but that path leads to noise rather than clarity. A better approach is to start with the handful of actions that map directly to your goals. For a shop, that is product views, add-to-carts, and purchases. For a lead-generation site, it is form starts, form submissions, and perhaps brochure downloads. For a content site, it might be scroll depth, newsletter sign-ups, and clicks on key calls to action.

If you are not yet sure which metrics deserve your focus, our overview of the key metrics every business should track monthly is a sensible companion, and the broader primer on what web analytics is and why it matters sets the scene if the whole subject still feels new. Get those foundations right and even a modest set of well-chosen events will tell you more than a sprawling, unfocused setup ever could.

The reports themselves can feel intimidating at first, but they follow a logic once you know events sit underneath everything. Our guide to reading a GA4 report without getting lost ties the threads together, showing how the events you have configured surface in the standard reports you will check most days.

Common mistakes worth dodging

Three traps catch most people. The first is over-tracking: firing an event for every tiny interaction until the data becomes impossible to interpret. The second is under-describing: creating an event but forgetting the parameters that would have made it meaningful, so you end up knowing that something happened but not the useful specifics. The third is forgetting to register parameters as dimensions, then wondering why you cannot find them in your reports.

Avoiding these is mostly a matter of restraint and intention. Before you create an event, ask what decision it will help you make. If you cannot answer that, you probably do not need it yet. Tracking is a means to an end, and the end is always a better business choice, whether that is fixing a leaky checkout, doubling down on a popular product, or quietly retiring a page nobody reads.

Frequently asked questions

References

1. Google. "[GA4] Events." support.google.com/analytics.
2. Google. "[GA4] Enhanced measurement events." support.google.com/analytics.
3. Simo Ahava. "Google Analytics 4 event tracking guides." simoahava.com.