GA4 Custom Event Tracking Using Google Tag Manager

GA4's automatic tracking catches page views and basic clicks. It does not know what a "sign up" means to your business, or which button on your pricing page actually matters. A custom event fills that gap, and building one through Google Tag Manager takes four steps, three of which involve zero coding beyond a single line of JavaScript.

A custom event in GA4 is an event you define yourself to track an interaction that GA4's automatic and enhanced measurement do not capture natively.

Built through Google Tag Manager, the process pushes data to the dataLayer, triggers a tag based on that push, and sends the result to GA4 as a named event with whatever parameters you choose.

We covered the reporting side of this in our GA4 events vs conversions guide. This article is the implementation half: the actual code and GTM configuration that makes a custom event exist in the first place.

How a Custom Event Actually Travels From Click to Report

Step 1: Push the Event to the DataLayer

According to Google's official Tag Manager data layer documentation, every custom event starts with a dataLayer.push() call, either written directly in your site's code or triggered through a form library's callback.

dataLayer.push({
  'event': 'registrationComplete',
  'plan': 'pro_monthly',
  'user_type': 'new'
});

A basic dataLayer push, fired the moment a registration form completes successfully

Step 2: Create a Custom Event Trigger in GTM

According to Analytics Mania's guide to the GTM custom event trigger, the trigger's event name must match the dataLayer's event value exactly, since GTM matching is case-sensitive.

Step 3: Create Data Layer Variables for Your Parameters

Variable Type: Data Layer Variable
Data Layer Variable Name: plan
Variable Name in GTM: DLV - plan

Repeat this for each parameter pushed to the dataLayer, like plan and user_type

Step 4: Build the GA4 Event Tag

Naming: DataLayer Event vs. GA4 Event Name

These do not have to match, and understanding why avoids a common point of confusion.

DataLayer Event Code Generator

Enter an event name and two parameters to generate the exact JavaScript to paste into your site.

When to Use a Custom Event vs. a Recommended Event

According to Analytics Mania's guide to custom events in GA4, Google's recommended events come with predefined parameters and are worth using whenever your interaction matches one, since analysts and future team members will recognize the naming convention immediately.

A genuinely custom event makes sense when no recommended event fits, such as a specific interaction unique to your product, like expanding a pricing comparison table or completing a multi-step configurator tool.

Server-Side Considerations for Custom Events

According to TAGGRS' documentation on setting up a GTM data layer, always sending events to GTM through a dataLayer.push rather than a direct gtag call keeps the setup portable, whether the container eventually moves to server-side tracking or stays entirely client-side.

Common Mistakes When Setting Up a Custom Event

According to CustomerLabs' guide to setting up custom events in GTM, including key variables like product ID or page URL in the dataLayer push, not just the event name alone, is what makes the resulting reports actually useful.

According to DataTrue's GA4 event tracking setup guide, forgetting to enter the GA4 Measurement ID correctly in the tag configuration is a common setup error that silently prevents events from ever reaching the property at all.

A third common mistake involves duplicate tags. Two separate GA4 event tags firing on the same trigger, often left over from earlier testing, send the same event twice, inflating counts across every report that references it.

Testing Before You Publish

According to Analytics Mania's guide referenced above, GTM's Preview mode shows the dataLayer event firing in real time. Clicking it confirms whether the GA4 event tag actually fired as expected.

Once the tag fires correctly in Preview mode, switching to GA4's DebugView confirms the event and its parameters arrived at the property with the correct values before publishing the container live to real visitors.

According to Owntag's guide referenced earlier, keeping a simple internal reference document listing every dataLayer event name, its GTM trigger, and its corresponding GA4 event name prevents naming drift as more people on a team start adding new tracking over time.

FAQs on GA4 Custom Event Tracking