GA4 Event Tracking: The Complete Guide

GA4 event tracking captures every meaningful user interaction on your website or app as an event. Unlike Universal Analytics, which used a category/action/label hierarchy, GA4 treats everything as an event: page views, scrolls, clicks, form submissions, purchases. You get four types of events to work with: automatically collected (tracked with no setup), enhanced measurement (toggled on in the GA4 admin), recommended (Google’s suggested events by business type), and custom events (anything specific to your business). This guide walks through all four types, shows you how to set them up using Google Tag Manager, and explains how to verify they’re firing correctly in DebugView.

“Most GA4 implementations I audit are collecting data, but not the right data. Teams turn on enhanced measurement and call it done, missing the 15-20 custom events that actually tell you whether your marketing is working.”

Hardik Shah, Founder of ScaleGrowth.Digital

GA4 uses a flat event-based data model where every interaction is an event with parameters. There’s no session-based hierarchy. A page view is an event. A purchase is an event. A scroll past 90% is an event. Each event can carry up to 25 custom parameters that provide context about what happened.

GA4 event is any user interaction or system occurrence tracked by Google Analytics 4, consisting of an event name and up to 25 key-value parameter pairs that describe the interaction.

This model is fundamentally different from Universal Analytics. In UA, you had hits, sessions, and users as separate concept layers. In GA4, everything flows through events. According to Google’s developer documentation (2025), GA4 properties can collect up to 500 distinct event names and 50 custom dimensions per property. The four event types form a hierarchy of implementation effort:

1. Automatically collected events: Zero setup. GA4 fires these the moment your tracking code loads.
2. Enhanced measurement events: Toggle on/off in GA4 Admin. No code required.
3. Recommended events: You implement them, but you use Google’s predefined event names and parameters.
4. Custom events: Your own event names and parameters for business-specific interactions.

Enhanced measurement events are pre-built interaction trackers that you toggle on in GA4 Admin > Data Streams. No code changes, no GTM tags.

Event	What It Tracks	Default State
scroll	Fires when user scrolls past 90% of page height	On
click (outbound)	Fires when user clicks a link to an external domain	On
view_search_results	Fires when site search is used	On
video_start, video_progress, video_complete	Tracks embedded YouTube video engagement at 10%, 25%, 50%, 75%	On
file_download	Fires when user clicks a link to download a file	On
form_interaction	Fires on form start and form submission	On

Enhanced measurement gives you about 70% of what a basic implementation needs. For serious tracking needs, disable the enhanced measurement versions and build your own via GTM with tighter control.

Custom events track interactions specific to your business that aren’t covered by other event types. Examples: clicking a pricing toggle, expanding an FAQ accordion, using a calculator tool. Method 1: In GA4 Admin. Go to Admin > Events > Create Event. Define conditions based on existing events. Limited flexibility. Method 2: Via Google Tag Manager. Create a GA4 Event tag in GTM, specify the event name and parameters, and set a trigger. This gives you full control. GA4 limits you to 500 unique event names per property and 25 parameters per event. Each parameter value has a 100-character limit. These are hard limits.

1. Open GTM and create a new Tag. Choose “Google Analytics: GA4 Event” as the tag type.
2. Name the event. Use snake_case, all lowercase. Example: cta_click.
3. Add parameters. Common: button_text, page_section, destination_url.
4. Set the trigger. Use a “Click – All Elements” trigger with conditions.
5. Preview and test. Click Preview to open GTM’s debug panel alongside your site.
6. Publish. Events appear in GA4’s Realtime report within seconds.

Rule 1: Use snake_case. All lowercase, words separated by underscores. GA4 is case-sensitive. Rule 2: Follow verb_noun format. Examples: click_cta, submit_form, view_pricing. Rule 3: Don’t duplicate Google’s names. Never create a custom event called page_view or scroll. Rule 4: Be specific enough to be useful, general enough to be maintainable. Use parameters for specificity, not event names. Rule 5: Document everything. Maintain a shared spreadsheet listing every event name, its parameters, and trigger conditions.

1. Create a “catch-all” CTA click event. One cta_click event with parameters: button_text, page_url, page_section, destination_url.
2. Use GTM’s “Element Visibility” trigger for engagement. Track when key page sections enter the viewport.
3. Set up server-side tagging for high-traffic sites. Improves collection accuracy by 15-30%.
4. Build audiences from events immediately. Audiences only start collecting from the day they’re created.
5. Export to BigQuery from day one. You can’t backfill, so every day without the export is data lost forever.