Event Tracking: Capturing What Visitors Do

Event tracking captures the interactions that pageviews miss — the clicks, form submits, video plays, scroll depths, downloads and outbound clicks that reveal what visitors actually do on a page, not just that they loaded it. And in GA4 this matters more than ever, because GA4 is fundamentally event-based: nearly everything is an event now. Understanding event tracking is understanding how modern analytics sees behaviour. Here's what events are, what to track, and how GA4 changed the picture.

What events capture

The gap events fill: pageviews tell you a page loaded; events tell you what happened on it — did they click the CTA, submit the form, play the video, scroll to the bottom, download the PDF, click an outbound link? These interactions are where engagement and intent show up, and they're invisible to pageview-only tracking. Event tracking captures them — recording "this visitor clicked this button" or "submitted this form" — turning the page from a black box (they landed, they left) into a visible sequence of actions. The interactions worth tracking are the ones tied to your goals: the clicks toward conversion, the engagement signals, the friction points — the behaviour that tells you whether the page is working.

What to track (and what not to)

The events worth capturing, tied to purpose: conversion-path clicks (CTA clicks, add-to-cart, form starts and submits — the actions leading to goals), engagement signals (video plays, scroll depth, time-based engagement — how deeply visitors engage), content interactions (downloads, outbound link clicks, internal search — what content they pursue), and friction points (form abandonment, error encounters — where they struggle). The discipline: track events that inform decisions, not everything possible (over-tracking creates noise and analysis paralysis — capture what ties to goals and behaviour you'll act on, per the what-to-track rules); and name events consistently (a naming convention so your event data is analysable rather than a chaotic list — the same discipline GTM demands). Purposeful event tracking illuminates behaviour; indiscriminate event tracking buries it.

How GA4 changed events

The fundamental shift: GA4 is event-based at its core — where Universal Analytics treated events as a special category alongside pageviews, GA4 makes everything an event (pageviews are events, clicks are events, conversions are events) with a flexible event+parameters model. This means: GA4 auto-collects many events (enhanced measurement captures scrolls, outbound clicks, site search, video engagement automatically — less manual setup for common events), events carry parameters (rich context attached to each event — more flexible than UA's category/action/label), and conversions are marked events (you designate which events count as conversions, per goal setup). The practical upshot: event tracking is now central, not supplementary — often configured via GTM, capturing the behaviour that reveals whether your content and pages do their job, measuring what content and authority earn (our half).

Frequently asked questions

What events should I track?

The ones tied to your goals and decisions — conversion-path clicks (CTAs, forms, cart actions), engagement signals (video, scroll, downloads), and friction points (abandonment, errors). Don't track everything possible (that creates noise); track what informs action, per the what-to-track discipline. GA4 auto-collects many common events (scrolls, outbound clicks) via enhanced measurement, so you may need less manual setup than you'd think.

How is event tracking different in GA4?

GA4 is fundamentally event-based — everything (pageviews, clicks, conversions) is an event with parameters, versus UA's separate pageview/event model. GA4 auto-collects many events (enhanced measurement), events carry richer context (parameters), and you designate events as conversions. Event tracking is now central to how GA4 works, not a supplementary feature — a significant shift for anyone moving from UA.

How do I set up event tracking?

In GA4, enable enhanced measurement for auto-collected events, then use Google Tag Manager for custom events (configuring triggers and tags for specific interactions) — GTM is the common tool for flexible event deployment. Name events consistently (a convention), track purposefully (goals and decisions, not everything), and verify with preview/debug before relying on the data, measuring what content and authority earn (our lane).