Event Tracking

Written by Cobus van der Westhuizen, reviewed by Wynand van der Westhuizen, fact-checked by Lenata Oosthuizen. Last reviewed July 2026. Editorial policy.

What Is Event Tracking?

Traditional web analytics measured visitor behaviour primarily through page views. Every time a browser loaded a new URL, the analytics platform recorded a hit. This worked well for understanding which pages were popular, but it missed the richness of what users actually did on those pages. Event tracking was introduced to fill this gap by capturing specific interactions that happen within a page, without a new URL being loaded.

An event can be almost any interaction: a click on a phone number link, a scroll to 50% of a page, the start or completion of a video, a file download, the opening of a live chat widget, or a form submission. Each event is typically described using a category (the type of interaction), an action (what the user did), and optionally a label (which specific element was interacted with). In Google Analytics 4, this has been simplified to event names and parameters, but the underlying concept remains the same.

Event tracking is set up through the analytics tag on your site, usually configured via Google Tag Manager. GTM allows marketers to define triggers based on user behaviour, such as clicking an element with a specific CSS class or ID, submitting a form, or scrolling past a certain threshold. When the trigger fires, GTM sends an event to Google Analytics 4 with the relevant data. This setup requires no changes to the website code itself, which makes event tracking accessible to marketing teams without developer support.

The value of event tracking lies in the behavioural data it produces. Knowing that 2,400 users visited your pricing page is useful, but knowing that 380 of them clicked the "Get a quote" button, that 210 then reached the form, and that 47 submitted it reveals the conversion funnel in detail. Each drop-off point identifies a specific optimisation opportunity. Without event tracking, that funnel is invisible.

Event Tracking In Practice

The scenario below is an illustrative example, not a Juicy Designs client result. The figures indicate the scale of effect that event tracking work typically produces, so treat them as indicative rather than measured.

Consider a Sandton-based financial services firm that redesigns its website contact page, after which form submissions drop. Without event tracking, the team would have no way to diagnose the problem. With event tracking in place, a GA4 review might show that users are clicking the "Submit" button but that the form submission event is not firing consistently on mobile devices. Further investigation would typically point to a JavaScript conflict on mobile that prevents the form from completing. Once the data points to the problem, the fix is usually straightforward, and submissions could plausibly return to their previous level within a week or so.

Event tracking also feeds directly into conversion rate optimisation efforts. By tracking which elements users interact with and where they drop off, South African businesses can make evidence-based decisions about page layout, CTA placement, and content structure. This removes guesswork and focuses improvement efforts on the changes most likely to produce measurable results in enquiries, sales, or sign-ups.

What to track with events

Events capture the specific interactions that page views miss, the things people do on a page rather than just the pages they load. Useful events include form submissions and enquiry sends, button and call-to-action clicks, phone-number and email taps, file and brochure downloads, video plays, scroll depth, and add-to-basket and checkout steps. The aim is not to track everything but to track the actions that indicate progress towards a goal, so you can see where visitors engage and where they drop off. In Google Analytics 4, interactions are modelled as events by default, which makes this behaviour-level view central rather than an add-on, and lets any meaningful action be marked as a conversion.

How events become conversions

In Google Analytics 4 the relationship is direct: conversions are simply events you have marked as important. You track a range of events to understand behaviour, then designate the ones that represent real business value, an enquiry, a purchase, a call, as conversions, so they appear in conversion reports and can feed advertising platforms for optimisation. This is why accurate event tracking underpins everything downstream: if the event does not fire reliably, the conversion is undercounted, reports mislead, and automated bidding optimises towards bad data. Setting up and verifying the events that matter, before relying on the numbers, is the foundation that makes conversion measurement and optimisation trustworthy.

FAQ