GA4 Event Tracking: The Complete Guide to the GA4 Event Model

The GA4 event model is fundamentally different from Universal Analytics. In UA, events had a rigid Category/Action/Label structure. In GA4, everything is an event — including pageviews, scrolls, and sessions — and each event can carry up to 25 custom parameters. Understanding this model is the foundation of any correct GA4 implementation.

The Four Tiers of GA4 Events

GA4 events fall into four categories, each with different implementation requirements.

1. Automatically Collected Events

These fire automatically when you install GA4 without any additional configuration:

These require no code. They're always on.

2. Enhanced Measurement Events

These are automatic but need to be enabled in your data stream settings (Admin → Data Streams → your stream → Enhanced Measurement):

Enable all of these. They provide significant engagement signal with zero implementation effort.

One caveat: Enhanced Measurement's form_submit event is unreliable for custom-built forms (React forms, multi-step forms, AJAX submissions). For those, implement custom events.

3. Recommended Events

These are events Google defines with a standard schema — standard event names with standard parameter names. Using recommended event names ensures maximum compatibility with GA4 reports, predictive features, and Google Ads.

// User signs up for account
gtag('event', 'sign_up', {
  method: 'email'  // or 'google', 'facebook'
javascript

// User logs in gtag('event', 'login', { method: 'email' });

// Lead generated (form submission, demo request) gtag('event', 'generate_lead', { currency: 'USD', value: 50.00 // estimated lead value }); `

// Product viewed
gtag('event', 'view_item', {
  currency: 'USD',
  value: 49.99,
  items: [{
    item_id: 'SKU_001',
    item_name: 'Product Name',
    item_category: 'Category',
    price: 49.99,
    quantity: 1
  }]
javascript

// Add to cart gtag('event', 'add_to_cart', { currency: 'USD', value: 49.99, items: [{ item_id: 'SKU_001', item_name: 'Product Name', price: 49.99, quantity: 1 }] });

// Purchase completed gtag('event', 'purchase', { transaction_id: 'T_12345', value: 49.99, currency: 'USD', items: [{ item_id: 'SKU_001', item_name: 'Product Name', price: 49.99, quantity: 1 }] }); `

4. Custom Events

Custom events are for anything not covered by recommended events. They can carry any parameters you define.

// Custom event: user clicks a specific CTA
gtag('event', 'cta_click', {
  cta_location: 'hero',
  cta_text: 'Start Audit',
  page_type: 'landing'
javascript

// Custom event: user filters a product list gtag('event', 'filter_applied', { filter_type: 'price_range', filter_value: '0-100' }); `

Custom events do NOT appear in standard GA4 reports until you register their parameters as custom dimensions. See the section on custom dimensions below.

Implementing Events via GTM vs Direct gtag

Via Google Tag Manager (Recommended for Most Teams)

Using GTM's dataLayer gives you the cleanest separation between developers and analysts. Developers push structured data; analysts build tags without touching code.

// Developer pushes this from the application
window.dataLayer = window.dataLayer || [];
dataLayer.push({
  event: 'generate_lead',
  lead_source: 'contact_form',
  lead_value: 50,
  form_id: 'contact-main'
});
javascript

In GTM, you then create: - A Custom Event trigger listening for generate_lead - DataLayer variables for lead_source, lead_value, form_id - A GA4 Event tag with event name generate_lead and the variables mapped as parameters

Via Direct gtag.js

If you don't use GTM, call gtag('event', ...) directly from your application code:

// After form submission succeeds
document.getElementById('contact-form').addEventListener('submit', function(e) {
  e.preventDefault();
  // ... handle form submission ...
  gtag('event', 'generate_lead', {
    lead_source: 'contact_form',
    value: 50,
    currency: 'USD'
  });
});
javascript

Custom Dimensions and Metrics

Event parameters are collected by GA4 but they don't appear in reports until you register them as custom dimensions (for string values) or custom metrics (for numeric values).

To register a custom dimension: 1. Go to Admin → Custom definitions 2. Click Create custom dimension 3. Enter the dimension name (what appears in reports), scope (Event or User), and the exact parameter name from your events 4. Save — it can take up to 24 hours to appear in reports

// Setting a user-scoped property (persists across sessions)
gtag('set', 'user_properties', {
  account_type: 'premium',
  user_industry: 'ecommerce'
});
javascript

GA4 allows up to 50 event-scoped custom dimensions and 25 user-scoped custom dimensions per property on the standard tier.

Marking Events as Key Events (Conversions)

In GA4, conversions are called key events. To mark any event as a key event:

1. Go to Admin → Key events
2. Click Create key event
3. Enter the exact event name
4. Choose the counting method: Once per session (typically for leads) or Multiple times per session (for e-commerce)

Key events you should configure for most businesses: - generate_lead — once per session - purchase — multiple times per session - sign_up — once per session - begin_checkout — once per session (for funnel analysis)

Common Event Tracking Mistakes

// Prevent duplicate purchase events
const tid = 'T_12345';
if (!sessionStorage.getItem('purchase_fired_' + tid)) {
  gtag('event', 'purchase', { transaction_id: tid, value: 49.99, currency: 'USD', items: [] });
  sessionStorage.setItem('purchase_fired_' + tid, '1');
}
javascript

Audit whether your GA4 events are correctly structured and firing on the right actions — run a property audit →