How to Define Events in Google Analytics

Setting up Google Analytics is just the first step, the real magic happens when you start tracking the specific user actions that matter to your business. This is done through events, which are the fundamental building blocks of data collection in Google Analytics 4. Learning how to define and configure them properly will transform your analytics from a simple traffic counter into a powerful tool for understanding customer behavior.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

This tutorial will guide you through exactly what GA4 events are, why they're so important, and two different step-by-step methods for creating the custom events you need to measure success.

What Exactly Are Events in Google Analytics?

In Google Analytics 4, an "event" is any distinct action a user takes on your website or app. That's it. This is a big shift from the old Universal Analytics, which was based on pageviews and sessions. In GA4, everything is an event - from viewing a page (a page_view event) to starting a new session (a session_start event) or making a purchase (a purchase event).

Think of events as little data packets that get sent to Google Analytics every time something meaningful happens. You visited this page? That’s an event. You scrolled down 90% of the way? That’s an event. You clicked to play a video? You guessed it - that's also an event.

This event-based model is incredibly powerful because it allows you to measure and analyze user engagement far more accurately than just looking at which pages people visited. It helps you answer critical business questions like:

• How many users signed up for our newsletter last week?
• Which call-to-action buttons are people actually clicking?
• What percentage of visitors watch the product demo video on our homepage?
• How many people add an item to their cart but don't complete the purchase?

By defining and tracking the right events, you can move beyond simple vanity metrics and start measuring what truly drives growth.

The Different Types of Events in GA4

Google Analytics categorizes events into four distinct types. Understanding the difference is key to knowing what you need to configure yourself versus what Google handles for you out of the box.

1. Automatically Collected Events

These are the events that GA4 collects by default as soon as you install the analytics tag on your site. You don’t have to do anything to enable them. They form the foundation of your data collection and include essential interactions.

Some of the most common automatically collected events include:

• session_start: Fires when a user begins a new session.
• first_visit: Fires the first time a user visits your site.
• page_view: Fires each time a new page loads.
• click: Fires when a user clicks a link that leads them away from your current domain.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

2. Enhanced Measurement Events

Enhanced Measurement allows you to track more complex user interactions without having to touch any code. These events are also collected automatically, but only if you have the feature enabled in your GA4 settings (which it is by default).

To check your settings, go to Admin > Data Streams, click on your web stream, and you'll see the Enhanced Measurement section.

Enhanced Measurement events include:

• scroll: Fires when a user scrolls 90% of the way down a page.
• file_download: Fires when a user clicks a link to a file (like a PDF, DOCX, or CSV).
• video_start, video_progress, video_complete: Fires for embedded YouTube videos on your site.
• view_search_results: Fires when a user performs a search on your website (if you use a standard search query parameter).

For many businesses, these automatically tracked events provide a ton of valuable information right away.

3. Recommended Events

Google provides a list of "Recommended Events" that are common across different industries. These events aren’t tracked automatically, you have to implement them yourself. The benefit of using Google's recommended names and parameters is that it makes your data compatible with GA4's standard reporting and future feature updates.

For example, for an e-commerce site, Google recommends events like:

• add_to_cart: When a user adds an item to their shopping cart.
• begin_checkout: When a user starts the checkout process.
• purchase: When a user completes a purchase.

For other industries, there are recommended events like login, sign_up, and generate_lead.

4. Custom Events

This is where you get to define what's most important and unique to your website. A custom event is any event that you name yourself and implement from scratch. If an action you want to track isn't covered by automatic, enhanced, or recommended events, you'll need to create a custom one.

Examples of custom events could be:

• cta_button_click: To track clicks on a specific call-to-action button.
• newsletter_signup_footer: To track signups from the form in your site's footer.
• pricing_plan_toggle: To see how many users switch between monthly and annual pricing views.

You have complete control over a custom event's name and the additional information (called parameters) you send along with it.

How to Set Up Custom Events in GA4

Now, let's get into the practical steps. We'll cover two primary methods for setting up your own events: one using just the Google Analytics interface, and a more powerful method using Google Tag Manager (GTM).

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Method 1: Creating Events Directly in the GA4 Interface (No Code Needed)

This method allows you to create a brand new event whenever another event you're already tracking meets specific conditions. The most common use case is creating an event for a form submission that directs users to a "thank you" confirmation page.

Let's say you want to create a generate_lead event every time someone visits yoursite.com/thank-you.

Step 1: Navigate to the Events Admin Panel In your GA4 property, click on Admin (the gear icon in the bottom-left), then under Data Streams, click on your web stream, and then click on "Events."

Step 2: Start Creating a New Event On the Events page, click the "Create event" button.

Step 3: Define Your Custom Event On the next screen, click "Create." This opens the configuration panel where you’ll define your event logic.

Step 4: Configure the Matching Conditions You need to tell GA4 when to fire your new event. In this case, we want it to fire whenever a basic page_view event occurs on our specific thank-you page.

• Custom event name: Enter your desired name. Let’s use generate_lead. Remember to follow Google's naming conventions (lowercase letters and underscores only).
• Matching Conditions: This is where you set the rules.

Your configuration should now say: When event_name equals page_view AND page_location contains /thank-you, create a new event called generate_lead.

Step 5: Create and Verify Click “Create” in the top-right. Your new event is now live! To verify it’s working, you can open a new tab and visit your thank-you page. Then, check the Reports > Realtime report in GA4. You should see your generate_lead event appear in the "Event count by Event name" card within a minute or two.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Method 2: Using Google Tag Manager (Recommended for Flexibility)

While the GA4 interface method is great for simple cases, Google Tag Manager (GTM) offers much more power and control without requiring you to edit your website's code manually. It is the preferred method for tracking things like button clicks, form submissions that don't go to a thank you page, and other granular interactions.

Let's walk through tracking a click on your main "Request a Demo" button.

Step 1: Enable Click Variables in GTM Before creating triggers, you need to make sure GTM is listening for click actions. In your GTM container, go to Variables. In the "Built-In Variables" box, click "Configure" and ensure all the "Clicks" variables like Click Text, Click URL, and Click ID are checked.

Step 2: Create a Trigger Triggers tell GTM when to fire a tag. We need a trigger that only fires when someone clicks our specific demo button.

1. Go to the Triggers menu and click "New."
2. Name your trigger something descriptive, like "Click - Request a Demo Button."
3. Click "Trigger Configuration" and choose "Click - All Elements" under the Click section.
4. Set the trigger to fire on "Some Clicks."
5. Now set the condition. Look at your website's button to find a unique identifier. Let’s assume the button text is "Request a Demo." Set the condition to fire when Click Text equals Request a Demo. (For more reliability, using Click ID is better if your button has a unique HTML ID).
6. Save the trigger.

Step 3: Create the GA4 Event Tag Now we create the tag that sends the event data to Google Analytics when the trigger fires.

1. Go to the Tags menu and click "New."
2. Name your tag "GA4 Event - Request a Demo."
3. Click "Tag Configuration" and select "Google Analytics: GA4 Event."
4. For "Configuration Tag," select your main GA4 configuration tag (the one you set up when you installed GTM).
5. For "Event Name," enter what you want the event to be called in GA4. For this example, use request_demo_click.
6. (Optional but recommended) In the "Event Parameters" section, you can add more context. For example, add a parameter named button_text with the value {{Click Text}}. This will tell you exactly which button text was clicked.
7. Save the tag.

Step 4: Link Your Tag to the Trigger After saving the tag configuration, a "Triggering" section will appear. Click on it and select the "Click - Request a Demo Button" trigger you created in the last step. Save the entire tag.

Step 5: Test and Publish The most critical step! Before going live, use GTM's "Preview" mode. This opens a debug version of your site. Click the "Request a Demo" button. In the GTM debug panel, you should see your tag "GA4 Event - Request a Demo" appear under the "Tags Fired" section. If it fired, you're good to go! Go back to GTM, click "Submit," and publish your container.

Viewing Your Events in GA4 Reports

Once you've set up your events and they have started collecting data, you can find them in a few places in GA4:

• Reports > Realtime: Perfect for instantly verifying that your new events are firing correctly.
• Reports > Engagement > Events: This is the main report where you'll see a list of all events, their total counts, and user counts over your selected date range. You can click on any event name to drill down into more detail about its parameters.

Final Thoughts

Defining events in Google Analytics is how you go from tracking simple page traffic to understanding how users actually interact and engage with your website. By setting up events that align with your business goals, you can finally measure the actions that truly drive conversions, whether that's a lead form submission, a demo request, or an e-commerce purchase.

Of course, collecting the data is just one piece of the puzzle. The ultimate goal is to generate actionable insights quickly, without getting lost in complex reports. At this stage, we have found that many marketers still spend hours navigating menus or trying to build custom reports. That's why we've streamlined the entire process. Once you connect Google Analytics, you can use Graphed to build real-time marketing dashboards and ask questions about your performance in plain English, getting instant answers and visualizations without ever having to manually configure a report again.