GA4 Custom Event Tracking: Measuring What Actually Matters

Google Analytics 4 tracks page views automatically — but most of the actions that actually matter to your business happen below that surface. Did a visitor watch your explainer video all the way through? Did they click your phone number on mobile? Did they scroll past your pricing table? Without custom event tracking, you have no idea. GA4’s event-based model is built precisely for this kind of measurement.

This guide explains how GA4 custom events work, how to set them up using Google Tag Manager, and how to use what you collect to make smarter decisions about your website. At Xpose, we implement event tracking for clients as a standard part of every analytics setup — because page views alone tell you very little about whether your site is actually working.

How GA4 Events Work

In GA4, everything is an event. A page view is an event. A scroll is an event. A click is an event. GA4 automatically collects a core set of events — page_view, session_start, first_visit — and enhanced measurement events like scroll, outbound clicks, site search, and video engagement (if YouTube is embedded). But automatic events can’t capture the specific interactions that are unique to your site, like clicking your "Get a Quote" button or downloading your price list PDF.

Custom events fill that gap. You define the event name (e.g. quote_button_click), add parameters to give context (e.g. button_location: header), and tell GTM when to fire it (e.g. when a specific element is clicked). GA4 then logs that event in your reports, and you can mark it as a conversion so it appears in your conversion tracking.

Setting Up Custom Events via GTM

The cleanest way to implement GA4 custom events is through Google Tag Manager. In GTM, create a new GA4 Event tag, connect it to your GA4 Measurement ID, and give the event a descriptive name following GA4’s snake_case convention (phone_click, form_submit, brochure_download). Then set the trigger — for a phone number click, you’d use a Click trigger filtered by the link URL containing tel:. Publish the container, verify in GTM Preview mode that the tag fires correctly, then confirm the event appears in GA4’s DebugView in real time.

For form submissions, be careful not to fire the event on the click of the submit button — fire it on the confirmation page or on a successful form submission callback instead. Firing on button click will inflate your numbers by including people who clicked but whose form had validation errors.

Turning Event Data into Decisions

Raw event counts are a starting point, not an endpoint. The real value comes from segmenting. What percentage of visitors who viewed your pricing page went on to submit a contact form? Which traffic source drives the most phone clicks? Is your video being watched to completion, or do people drop off in the first 30 seconds? GA4’s Explore reports let you cross-reference events with acquisition channels, devices, and user properties to answer these questions.

Mark your most important events as conversions in GA4 (Admin > Events > toggle "Mark as conversion"). This brings them into the conversion columns of your standard reports and makes them available for bidding optimisation in Google Ads. At Xpose, we help clients identify which two or three conversion events genuinely reflect business success — then build reporting dashboards around those specific signals rather than drowning in data.