GA4 Event Tracking Setup: A Practical Beginner's Guide

GA4's event-based model is more flexible than Universal Analytics — and significantly easier to misconfigure. Teams new to GA4 often end up with hundreds of events, no consistent naming, and reports that surface noise instead of signal.

This guide covers what you need to know before you create your first custom event.

How GA4 Event Tracking Works

Everything in GA4 is an event. Page views, scrolls, button clicks, form submissions, purchases — they are all events with parameters attached. This is different from Universal Analytics, which used a separate hit type system.

GA4 automatically collects a set of events without any configuration:

• page_view — fires on every page load
• session_start — fires at the beginning of a session
• first_visit — fires when a user visits for the first time
• scroll — fires when a user scrolls 90% down a page
• click — fires on outbound link clicks
• view_search_results — fires when a user performs a site search

These automatic events are useful baselines, but they are not enough for most measurement plans. You need custom events to track the interactions that are specific to your product.

GA4 Event Structure You Need to Understand

Every GA4 event has a name and up to 25 parameters. Parameters are the context that makes an event useful.

An event named form_submit tells you a form was submitted. An event named form_submit with parameters form_name: "demo_request" and user_type: "returning" tells you something actionable.

When planning custom events, always think in pairs: the event name, and the parameters that answer "which one" and "in what context."

GA4 Event Tracking Setup: Creating Custom Events via GTM

Google Tag Manager is the standard way to implement custom events without touching your site's codebase for every change.

Step 1: Create a GA4 Configuration Tag

In GTM, create a GA4 Configuration tag with your Measurement ID. Set it to fire on All Pages. This establishes the GA4 connection and sends page view events.

Step 2: Plan Your Events Before Building

Before opening GTM, write a tracking specification. For each event you want to capture:

• Event name (all lowercase, underscores for spaces, no spaces or special characters)
• What triggers it (button click, form submission, page load)
• Which parameters to include
• How you will verify it is working

Planning before building prevents the most common GA4 mistake: a bloated event list with inconsistent naming that is impossible to report on cleanly.

Step 3: Set Up a Trigger

A trigger tells GTM when to fire an event. For a button click:

1. Create a new Trigger of type Click - All Elements or Click - Just Links
2. Set the trigger to fire when a specific CSS class or ID matches
3. Preview the trigger in GTM's debug mode to confirm it fires at the right moment

Step 4: Create the GA4 Event Tag

1. Create a new Tag of type Google Analytics: GA4 Event
2. Select your configuration tag
3. Enter your event name following your naming convention
4. Add parameters using GTM variables (built-in variables like Click Text or custom JavaScript variables)
5. Assign your trigger to the tag
6. Save

Step 5: Test in Preview Mode

Use GTM's preview mode to verify the event fires on the correct interaction. Then check GA4's DebugView (found under Admin) to confirm the event arrives with the correct parameters.

Do not publish to production until DebugView confirms the event is working as expected.

Naming Conventions for GA4 Custom Events

GA4 event names are case-sensitive. Add_To_Cart and add_to_cart are different events. Use these rules:

• All lowercase
• Underscores between words (form_submit, not formSubmit or form-submit)
• Descriptive but concise — the name should be readable without documentation
• Follow GA4's recommended event names for standard actions (GA4 has a list of recommended events for ecommerce, engagement, and onboarding that you should use instead of inventing your own)

The Most Common GA4 Event Tracking Mistakes

Sending personally identifiable information as parameters. Do not include email addresses, names, phone numbers, or user IDs in event parameters. GA4's terms of service prohibit PII in event data, and it creates compliance risk.

Creating an event for every micro-interaction. Track what you will actually use. An event you never look at is clutter that makes your event list harder to navigate.

Not marking conversions. GA4 events are not conversions by default. Go to Admin, then Events, and toggle the events that represent actual conversion actions (form submissions, purchases, signups) to be marked as conversions. Without this step, your conversion reports are empty.

Changing event names after launch. GA4 stores historical data under the event name you used. If you rename an event, you create a gap in your historical trend data. Get naming right before you ship.

What Good Event Tracking Looks Like

A well-configured GA4 implementation has:

• Fewer than 50 custom events, each with a clear purpose
• Consistent naming conventions across all events
• Parameters that enable segmentation and filtering
• Three to five events marked as conversions
• A written tracking specification that matches what is live in GTM

If your GA4 setup has grown organically and the event list is now too large to navigate confidently, a tracking audit is usually the right first step before adding anything new.

If you want a clean GA4 implementation built from a proper tracking specification — one that will still make sense in two years — talk to Clixo.