Definition:

An event, in digital analytics, is an interaction or occurrence recorded on a website or in an application to measure what happens. It may represent a page view, a click, a purchase or an application error.

Events make it possible to analyse specific actions, beyond counting visits. Not every event corresponds to a deliberate user action: events can also record automated processes or system behaviour.

Contents

1 What events are used for in digital analytics
2 How an event is described
3 Types of events in Google Analytics 4
4 The difference between an event and a key event
5 Example: measuring a request for a quote
6 Setting up and checking events

What events are used for in digital analytics

Events help you understand how a website or application is used and where a process is completed or interrupted. In a digital analytics project, event selection starts with the questions the business needs to answer.

For example, a store can measure when a product is viewed, added to the cart and purchased. Comparing these steps helps identify where participation drops, although the data alone does not explain why.

Recording more events does not mean having better information. Each event should represent an identifiable action and serve a purpose in the analysis.

How an event is described

An event usually includes a name that identifies what happened and additional data that provides context. In Google Analytics 4, this data is called parameters.

For example, the purchase event records a purchase. It can include parameters such as transaction_id, which identifies the transaction; value, which specifies its value, and currency, which identifies the currency.

The name tells you what happened; the parameters describe that particular transaction. There is no need to create a different event name for every product or amount.

Types of events in Google Analytics 4

Google Analytics 4 uses an event-based measurement model. Events fall into these groups according to how they are collected or defined:

Automatically collected events: recorded when the tool is implemented, such as the start of a session.
Enhanced measurement events: measure certain website interactions when this feature is enabled, such as outbound link clicks or downloads of supported file types.
Recommended events: have names and parameters defined by Google for common actions, such as purchase for purchases or generate_lead for lead generation. They require an appropriate implementation.
Custom events: defined when the previous groups do not cover the interaction you need to measure.

Using a recommended event does not mean it is recorded automatically. Choosing the name and configuring what triggers it are separate matters.

This classification of GA4 events helps you check which options cover each requirement before creating your own events.

The difference between an event and a key event

A key event is an event considered particularly important to business objectives and marked as such in GA4. It is not a different interaction: it is a classification that highlights its importance for measurement.

A purchase or a request for a quote can be a key event. A menu click may be useful for studying navigation without having the same business importance.

Marking an event as a key event does not fix its implementation. If it is recorded twice or triggered before the action is completed, it will still produce incorrect measurement.

Example: measuring a request for a quote

A company wants to know how many people request a quote through its form. Measuring only clicks on the submit button is not enough: the form could contain errors and fail to submit.

The event should be recorded when the request is confirmed as successfully completed. If this interaction represents lead generation, generate_lead can be used and marked as a key event.

Useful information, such as the type of service requested, can also be included without sending names, email addresses or other personally identifiable information to Google Analytics.

This distinguishes between attempting to submit the form and actually completing a request.

Setting up and checking events

Events can be implemented through website code, platform integrations or tools such as Google Tag Manager. Applications also use the relevant measurement SDKs.

Before considering an implementation complete, check these points:

Trigger condition: the event is sent when the intended action occurs.
Duplicates: the same interaction does not generate extra records because of an incorrect configuration.
Parameters: the values sent describe the action correctly.
Testing: events appear with the expected data in debugging tools such as GA4 DebugView.
Privacy: data collection respects consent and the restrictions applicable to the data sent.

The number of events is not the same as the number of people. A single user can perform the same action several times, so it is important to distinguish between repetitions and users who complete it.