Event Tracking

Event tracking is the practice of recording specific user interactions on a website or app (clicks, form submissions, video views, purchases) as structured data points sent to an analytics platform. In GA4, event tracking is the fundamental data model: every measurable interaction is an event.

Category: Analytics (also: Architecture)

Author: Atomic Glue Analytics Team

## Definition

Event tracking is the method of capturing and recording discrete user interactions with a digital property and transmitting them to an analytics or marketing platform. These interactions can include button clicks, form submissions, video plays, file downloads, page scrolls, ecommerce transactions, and any other measurable action a user takes. In GA4's event-driven model, event tracking is not an add-on feature. It is the primary data model. Page views themselves are events (page_view). Sessions are derived from event sequences, not recorded independently. This differs fundamentally from Universal Analytics where pageviews and events were separate tracking mechanisms with different limits and reporting structures.

## Event structure in GA4

Every event in GA4 has an event name (string, up to 40 characters, alphanumeric with underscores) and up to 100 event parameters. Parameters can be strings or numbers and provide contextual data about the interaction. For example, a video_start event might include parameters like video_title, video_duration, and video_percent. Events fall into three categories: automatically collected (page_view, session_start, first_visit), enhanced measurement events (scroll, outbound click, site search), and custom events you define. Google also provides recommended events with prescribed parameter schemas for common use cases like ecommerce, lead generation, and gaming.

## Implementation methods

You can send events via gtag.js (Google's global site tag), Google Tag Manager (GTM), the Google Analytics Data API, the Measurement Protocol (for server-side hits), or directly via Firebase SDK for mobile apps. GTM is the most flexible approach because it decouples tracking logic from your website code, allowing you to modify event definitions without deploying new code. The data layer sits between your site and GTM, passing structured data that GTM uses to populate event parameters.

## Recommended vs custom events

Google recommends using recommended events (like add_to_cart, purchase, login, sign_up, search) with their prescribed parameters whenever your use case matches. Recommended events unlock pre-built reports, audience templates, and future Google features. If your use case is unique, you can create custom events with custom parameter schemas. However, there is a limit of 500 unique event names per GA4 property, so planning your event taxonomy upfront is critical.

## Note

Misconception: GA4 automatically tracks every user interaction. It does not. Enhanced measurement covers scrolls, outbound clicks, site search, video engagement, and file downloads. Everything else requires explicit event tracking configuration via GTM, gtag.js, or direct API calls. Also: event names are case-sensitive. 'Add_To_Cart' and 'add_to_cart' are treated as different events. Use lowercase with underscores as Google recommends.

## In code

// Using dataLayer.push to track a custom event via GTM
dataLayer.push({
  event: 'newsletter_signup',
  form_location: 'footer',
  user_type: 'new_visitor',
  newsletter_name: 'Weekly Digest'
});

## Common questions

Q: What is the difference between an event and a parameter?

A: An event is the interaction itself (e.g., 'purchase'). A parameter provides context about the interaction (e.g., value, currency, items). Think of events as verbs and parameters as adjectives.

Q: How many events can GA4 handle?

A: GA4 properties have a limit of 500 unique event names. There is no hard limit on total event volume for standard properties, though there are rate limits on hits per second. 360 properties get higher limits.

Q: Do I need to use Google Tag Manager for event tracking?

A: No, but it makes your life easier. GTM separates tracking configuration from code deployment. Without it, any change to event tracking requires a developer to update and deploy website code.

## Key takeaways

• In GA4, event tracking is the core data model, not a supplementary feature
• Every interaction is an event, including page views and sessions
• Enhanced measurement covers basic interactions; complex tracking needs custom setup
• Use Google's recommended events and parameters for pre-built reports and audiences
• Plan your event taxonomy carefully to stay within the 500-event limit

## Related entries

• [Google Analytics 4 (GA4)](atomicglue.co/glossary/google-analytics-4-ga4)
• [Google Tag Manager](atomicglue.co/glossary/google-tag-manager)
• [Data Layer](atomicglue.co/glossary/data-layer)
• [Pageview](atomicglue.co/glossary/pageview)
• [Session](atomicglue.co/glossary/session)

Last updated July 2026. Permalink: atomicglue.co/glossary/event-tracking