Event Tracking

Event tracking is the practice of recording specific user interactions on a website or app, such as clicks, scrolls, video plays, downloads, and form submissions. It captures what visitors actually do, not just the pages they load. In Google Analytics 4 (GA4), event tracking is the foundation of all measurement: every interaction, including a pageview, is collected as an event.

Why Event Tracking Matters

Pageviews alone tell you which pages people visit. Event tracking tells you what they do once they get there. That difference is the whole point.

A page can get thousands of views while the signup button gets zero clicks. Without event tracking, that page looks successful. With it, you see the real problem. Event data shows which buttons get clicked, how far people scroll, which videos they finish, and which forms they abandon.

This data feeds three decisions. It identifies which content drives action, so you can do more of it. It surfaces friction points, like a checkout step where users drop off. And it powers conversion tracking, because any event you mark as valuable becomes a measurable conversion.

Types of GA4 Events

GA4 sorts events into four categories, ordered from least to most setup required:

• Automatically collected events. GA4 records these the moment you install the tag. Examples: first_visit, session_start, and user_engagement. No configuration needed.
• Enhanced measurement events. GA4 tracks these automatically when enhanced measurement is on, which it is by default. Examples: scroll, click (outbound), file_download, video_start, site_search, and form_start.
• Recommended events. Google predefines the names and parameters, but you must add the code. Use these for known actions like purchase, sign_up, login, and add_to_cart. Matching Google’s names unlocks standard reports.
• Custom events. You define the name and parameters for actions unique to your site, like pricing_toggle_clicked or demo_requested.

Always check enhanced measurement and recommended events before building a custom one. Reinventing an event Google already supports breaks default reporting.

How Event Tracking Works

A GA4 event has two parts: an event name and parameters that describe it. Each event can carry up to 25 parameters, and parameter values capture detail like the button text or page location.

There are three ways to send events:

1. Enhanced measurement. Toggle it on in your GA4 data stream. GA4 captures scrolls, outbound clicks, downloads, and more with no code.
2. Google Tag Manager. Create a tag and a trigger (for example, fire on a button click). GTM sends the event to GA4. This is the most common method for custom events.
3. gtag.js or the Measurement Protocol. Add the gtag('event',...) call directly in your code, or send events server-side via the Measurement Protocol.

A custom event sent with gtag.js looks like this:

gtag('event', 'demo_requested', {
 plan_name: 'pro',
 button_location: 'header'
});

Event Tracking in GA4 vs Universal Analytics

GA4 and the old Universal Analytics handle events in fundamentally different ways. Confusing the two is the most common migration mistake.

Universal Analytics used a rigid structure: every event needed a Category, Action, and optional Label and Value. A pageview was a separate hit type, not an event.

GA4 dropped that model. Everything is an event with flexible parameters, and a pageview is just a page_view event. There are no required Category or Action fields.

	Universal Analytics	GA4
Event structure	Category, Action, Label, Value	Event name + parameters
Pageview	Separate hit type	A page_view event
Parameters per event	1 label, 1 value	Up to 25
Conversions	Goals	Key events

Custom Events and Key Events

A custom event is any event you define yourself when no automatic or recommended event fits. Name it in lowercase with underscores, like quote_downloaded, and keep names under 40 characters.

A key event is different. In 2024, Google renamed GA4 “conversions” to “key events.” A key event is any event you flag as valuable, such as a purchase or a lead form submission. Marking an event as a key event tells GA4 to count it toward your conversion totals and report it in attribution.

So the workflow is: track the event first, then mark the important ones as key events.

How to Check Event Tracking

Verify events before you trust the data. GA4 gives you two tools.

Use DebugView (Admin, then DebugView) to watch events fire in real time as you click through your own site. Use the Realtime report to confirm events register from live traffic. Historical events appear under Reports, then Engagement, then Events, though they can take 24 hours to process fully.

If you tag campaign links, linkutm’s analytics dashboard shows click data alongside your GA4 event reports, so you can match campaign clicks to on-site behavior.

Frequently Asked Questions

What is event tracking in GA4?

Event tracking in GA4 is the recording of every user interaction as an event. Unlike Universal Analytics, GA4 treats all hits as events, including pageviews. Each event carries up to 25 parameters that describe the interaction in detail.

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

An event is any tracked interaction, like a scroll or click. A conversion, now called a key event, is an event you have flagged as valuable. Every key event is an event, but only events you mark count as conversions.

Do I need code to track events in GA4?

Not always. GA4’s enhanced measurement automatically tracks scrolls, outbound clicks, downloads, video plays, and form interactions with no code. You only need code or Google Tag Manager for custom events specific to your site.

What are custom events?

Custom events are events you define for actions unique to your site when no automatic or recommended event applies. You choose the event name and its parameters. Examples include pricing_toggle_clicked or demo_requested.

To see campaign clicks next to your GA4 events, explore linkutm’s analytics dashboard.