How to Set Up GA4 Custom Events (Beyond the Defaults)
Google Analytics 4 automatically tracks a useful baseline: page views, scrolls, outbound clicks, and file downloads. But the actions that actually matter to your business — a pricing calculator being used, a video being watched to completion, a specific button being clicked — usually aren't covered by default. That's where custom events come in.
This guide covers what custom events are, when you need them, and how to set them up correctly.
Key takeaways:
- GA4's automatically collected events cover general browsing behavior, not business-specific actions
- Custom events are typically implemented through Google Tag Manager, without needing a developer for every change
- Not every event needs to be a "key event" — reserve that label for actions tied to real business value
- Poorly named or duplicated custom events are the most common cause of messy GA4 reports
- Testing in DebugView before publishing prevents bad data from being permanently mixed into your reports
Default Events vs. Custom Events
| Type | Examples | Set Up By |
|---|---|---|
| Automatically collected | page_view, scroll, click (outbound), file_download | GA4, no setup needed |
| Enhanced measurement | video_start, video_progress, form_start | Toggled on in GA4 settings |
| Custom events | pricing_calculator_used, quote_requested, chatbot_opened | Google Tag Manager or direct code |
When You Actually Need a Custom Event
Not every click needs its own event — that leads to cluttered reports nobody uses. A custom event is worth setting up when the action:
- Directly signals purchase or lead intent (e.g., "Request a Quote" clicked)
- Represents meaningful engagement with a key feature (e.g., a product configurator used)
- Is something your team will actually make decisions based on
If the answer to "would we change anything based on this number?" is no, it's probably not worth tracking as a custom event.
Setting Up a Custom Event: Step by Step
1. Define the Trigger Clearly
Decide exactly what user action should fire the event — a specific button click, a form submission, or reaching a certain scroll depth. Vague triggers lead to inconsistent data.
2. Build It in Google Tag Manager
In GTM, create a new Trigger matching your defined action (e.g., "Click - CSS Selector matches .quote-button"), then create a Tag using the GA4 Event tag type, referencing your GA4 configuration tag.
3. Name Events Consistently
Use lowercase, underscore-separated names that match GA4's own conventions — for example quote_requested rather than "Quote Requested!!" or "quoteRequest." Consistent naming prevents duplicate or fragmented reporting later.
4. Add Useful Parameters
Attach parameters that add context, such as form_location or product_category. These let you break down the same event by different dimensions later without creating separate events for each variation.
5. Test in DebugView, Then Publish
Before publishing your GTM container, use GA4's DebugView to confirm the event fires exactly once, with the correct parameters, when you perform the action yourself.
6. Mark It as a Key Event (If Appropriate)
In Admin > Events, toggle "Mark as key event" only for actions that represent genuine business value — this keeps your key event list meaningful rather than diluted.
Common Mistakes to Avoid
- Tracking everything: More events isn't better; it makes reports harder to read and slows down analysis.
- Inconsistent naming: Mixing naming conventions across events makes filtering and comparison unreliable.
- Skipping DebugView: Publishing untested triggers is the fastest way to end up with duplicate or misfiring events in your historical data.
Frequently Asked Questions
Do I need a developer to create custom events in GA4?
Not usually. Most custom events can be built through Google Tag Manager using triggers based on clicks, form submissions, or page elements, without touching site code directly.
What's the difference between a custom event and a key event?
A custom event is any event you've defined beyond GA4's defaults. A key event (formerly called a "conversion") is a custom event you've specifically flagged as representing real business value, which then feeds into conversion reporting.
How many custom events should a typical business track?
There's no fixed number, but most small-to-medium business sites do well with 5–10 well-chosen custom events tied directly to leads or sales, rather than dozens of loosely defined ones.
Next Steps for Your Business
Custom events turn GA4 from a generic traffic report into a tool that actually reflects how your business makes money.
Our team can help identify which actions on your site are worth tracking and set up the custom events and key events to match, so your analytics reflect what really matters.