Event
In web analytics, an event is any user interaction recorded as a discrete action, from a pageview to a button click, used to measure behaviour beyond basic visits.
In web analytics, an event is a discrete user interaction recorded as a data point, used to measure specific actions beyond basic page visits and build a detailed picture of how people engage with a website or app.
What Event Means in Marketing
Every time a user does something on your site, that action can be captured as an event. Viewing a page is an event. Scrolling to the bottom of an article is an event. Clicking a button, watching a video, submitting a form, adding a product to a cart: all of these are events. The event-based data model is how analytics platforms turn a user’s behaviour into structured, queryable data.
In Universal Analytics, events were one of several hit types, separate from pageviews. In GA4, events are the universal data unit: pageviews are events, conversions are events, and any custom interaction you want to track becomes an event. This shift made the GA4 data model more consistent and flexible, but it also made understanding analytics reports require more deliberate setup, because you choose which events to make visible in your reports.
The practical value of event tracking is that it moves your analytics from “how many people visited?” to “what did they actually do?” Pageviews tell you which content people looked at. Events tell you whether they engaged with it, what they clicked, where they stopped and what actions they took. That’s the data that informs UX decisions, content priorities and conversion optimisation.
How Event Tracking Works
Automatic events. GA4 collects a set of events without any additional configuration. These include page_view, first_visit, session_start, scroll (at 90% page depth), click (for outbound links), view_search_results, video_start, video_complete and file_download. For most sites, these cover basic engagement without any custom implementation.
Enhanced measurement events. GA4 includes a toggle in the admin panel for enhanced measurement events, which extends automatic collection to on-site search, form interactions and scroll depth. These are on by default for new properties.
Recommended events. Google defines a set of recommended event names for common use cases: add_to_cart, purchase, sign_up, generate_lead and others. Using the recommended names ensures your events work with GA4’s built-in ecommerce and conversion reports and remain compatible with Google Ads.
Custom events. For any interaction not covered by automatic or recommended events, you define custom events with your own name and parameters. These are sent via Google Tag Manager, gtag.js or the GA4 Measurement Protocol (for server-side events).
Event parameters. Events carry parameters: key-value pairs that add context. A purchase event includes transaction_id, value, currency and items. A click event includes the URL clicked. You can register custom parameters as custom dimensions and metrics to make them available in reports.
Event Example
In GA4, conversions are simply events that you’ve marked as important. You go to GA4 admin, find the event you want to designate as a conversion, and toggle it on. Common conversion events: purchase, generate_lead, sign_up, contact_form_submit. Once marked, these events appear in your conversion reports and can be used as bidding goals in Google Ads.
Why Event Tracking Matters for Marketers
Events are the mechanism that connects your business goals to your analytics data. Pageviews and sessions are passive measures of traffic. Events are active measures of behaviour. If you want your analytics to tell you whether your marketing is actually working, you need event data: are people clicking calls to action, completing forms, adding products to cart and buying? That data starts with getting events configured correctly.
Frequently Asked Questions
What is the difference between events in Universal Analytics and GA4?
In Universal Analytics, events were a specific hit type alongside pageviews, transactions and social interactions. They had a category, action and label structure. In GA4, everything is an event: pageviews, sessions, conversions and custom interactions are all stored as events with associated parameters. GA4 collects several events automatically (page_view, first_visit, session_start, scroll) and lets you add custom events for any interaction you want to track.
What events should I track on a typical website?
GA4 automatically tracks page_view, scroll (90% depth), outbound clicks, site search, video engagement and file downloads without additional setup. Beyond that, what matters depends on your business goals. For ecommerce: add_to_cart, begin_checkout, purchase, view_item. For lead generation: form_submit, phone_click, contact_page_view. For content: scroll depth milestones, content engagement time, newsletter signup. Track what you'll actually use for decisions; unnecessary events add noise.
How do you set up custom events in GA4?
Custom events can be created through Google Tag Manager, directly in GA4's admin panel using event modification and event creation tools, or by adding gtag.js calls in your site code. Google Tag Manager is the preferred approach for most teams because it doesn't require code deployments for every new tracking requirement. Once an event fires, GA4 collects it automatically; you then register any parameters you want to report on as custom dimensions or metrics in the GA4 admin.
Want help with this for your brand? See my services.
Need help putting this concept into practice on your campaigns? Share your current targets and I will suggest the right approach.