How to Edit Events in Google Analytics 4

Ever opened your Google Analytics 4 reports only to find an important event tracked with a typo in the name for the last month? Or maybe you're tracking a generic form_submit event, but what you really need is to isolate only a specific "contact us" form submission. This article will show you exactly how to fix these common issues directly within the GA4 interface using the "Modify Event" and "Create Event" features - no GTM or code changes required.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Good Data Starts with Good Events

Clean, well-organized events are the foundation of reliable reporting. When your event names are inconsistent or too generic, it makes your analysis messy and difficult. Taking a few minutes to clean them up inside GA4 can save you hours of frustration down the road and give you more confidence in your data. It helps you:

• Correct mistakes: Fix typos (like conact_us_form) and inconsistent casing (like form_submit vs. Form_Submit) to ensure all data for the same interaction is grouped together.
• Create more specific events: Turn a generic event like page_view into a high-value event like pricing_page_view without needing developer help.
• Simplify reporting: Clearly named events make building reports and dashboards in Looker Studio, Power BI, or other tools much more straightforward.
• Improve conversion tracking: The new events you create can be marked as conversions, giving you a clearer picture of what's driving results.

Modify Event vs. Create Event: What's the Difference?

Google Analytics 4 gives you two primary tools for managing events within the interface, and choosing the right one depends on your goal.

1. Modify Event: Use this when you want to fix an existing event. It's like proofreading and correcting a mistake. The modification applies a rule that permanently alters the incoming event data before it's processed and stored. It’s the right choice for:

• Correcting a typo in an event name.
• Standardizing inconsistent event names (e.g., changing generate-lead or GenerateLead to the proper generate_lead format).
• Changing the value of an event parameter.

Think of this as an "edit" function. The original, incorrect event will no longer be processed once your rule is active.

2. Create Event: Use this when you want to create a new, more specific event based on an existing one. You’re not fixing the source event, you’re using it as a trigger to create a new, distinct event. The original event is still recorded as usual. It’s perfect for:

• Creating a thank_you_page_view event that only fires when a page_view occurs on a specific confirmation URL.
• Isolating a main demo request from all other form_submit events.
• Turning a generic click event into a download_pdf event when the clicked URL contains ".pdf".

Think of this as a "copy and specify" function. Both the original event (e.g., page_view) and the new event (e.g., thank_you_page_view) will be recorded.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

How to Modify an Event in GA4 (Step-by-Step Guide)

Let’s walk through a common scenario: you’ve discovered that your contact form submission event is being tracked as contact_form_submitt, with an extra "t". We want to correct it to contact_form_submit.

Step 1: Navigate to the Events Section

In your GA4 property, go to the Admin panel by clicking the gear icon in the bottom-left corner. Under the Data display column, click on Events.

Step 2: Choose to Modify an Event

On the top-right of the Events overview table, click the blue "Modify event" button.

Step 3: Create Your Modification Rule

Click the "Create" button. Now, you’ll define the logic for your fix.

• Modification name: Give your rule a descriptive name so you'll remember what it does later. For example, "Correct Contact Form Typo".

Step 4: Define the Matching Conditions

This is where you tell GA4 which events to look for and change. You need to be very specific here.

In the Matching conditions section:

• Set the first field to event_name.
• Set the operator to equals.
• Set the value to the incorrect name: contact_form_submitt.

This rule now tells Google, "if you see an event named exactly contact_form_submitt, apply the following changes."

Step 5: Configure the Modification

Now, you tell GA4 what you want to change about the event it just found.

In the Modify parameters section:

• Leave the first dropdown as event_name, because that’s what we want to change.
• Under New Value, enter the correct event name: contact_form_submit.

You can also use this section to add, change, or remove event parameters, but for our simple typo fix, we just need to change the event_name.

Step 6: Save and Verify

Click "Create" in the top-right corner to save your new rule. Your modification is now live. From this point forward, anytime GA4 receives an event named contact_form_submitt, it will automatically change it to contact_form_submit before saving it in your reports.

How to Create a New Event from an Existing One in GA4

Now for our second scenario. Let's say you want to track views of your /pricing page as a dedicated event, rather than lumping it in with all your other page_view data. We will create a new event called pricing_page_view that triggers whenever the page_view event occurs on the pricing page.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Step 1: Navigate to the Events Section

Just like before, head to Admin > Data display > Events.

Step 2: Start the Event Creation Process

This time, click the blue "Create event" button.

Step 3: Configure Your New Custom Event

Click "Create" to get started.

• Custom event name: Enter the name for your new event. Always use the recommended snake_case (all lowercase with underscores). We'll call ours pricing_page_view.

Step 4: Set the Matching Conditions

Here you define the conditions that trigger your new event. Since our new event depends on both the event name and the page URL, we will need two conditions.

• Condition 1:

Now, click "Add condition" to add the second rule.

• Condition 2:

These two conditions linked by an implicit 'AND' logic mean, "When an event named page_view happens on a URL that contains /pricing, fire our new custom event."

Step 5: Configure Parameter Copying

In the Parameter configuration section, ensure the box for "Copy parameters from the source event" is checked. This is important! It means your new pricing_page_view event will inherit all the useful parameters from the original page_view, like page_title, ga_session_id, and page_referrer.

Step 6: Save and Mark as a Conversion (Optional)

Click "Create" to save your new event rule. It should appear in your events list within 24 hours. Once it does, you can go back to the Events list, find pricing_page_view, and toggle on the switch in the "Mark as conversion" column to start tracking it as a key business objective.

Important Considerations and Best Practices

Before you go on an event-editing spree, keep these key points in mind to avoid creating a new mess while cleaning an old one.

1. Changes Aren't Retroactive

This is the most important rule. Any modification or creation rule you set up will only apply to data collected after the rule is saved. It will not go back in time and fix your old data. Your reports will show the old, incorrect event for historical date ranges and the new, correct event for future date ranges.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

2. Stick to GA4 Naming Conventions

Always use lowercase letters with underscores instead of spaces or hyphens (e.g., get_quote_submit, not GetQuoteSubmit or get-quote-submit). Consistency here will make reporting much cleaner.

3. Test with the DebugView

After creating a rule, don't just wait 24 hours and hope it works. Use the Admin > Data display > DebugView section to test your changes in real-time. This lets you immediately check if your new or modified events are firing as you expect on your website.

4. Don't Go Overboard

GA4 gives you a limit of 50 Modify event rules and 50 Create event rules per property. Use them to fix significant errors and create genuinely valuable new events. Ideally, major tracking should still be planned and implemented properly in Google Tag Manager, with these UI features used for quick adjustments and enhancements.

Final Thoughts

Knowing how to use GA4's "Modify" and "Create" event features gives you much-needed control over your data quality. You can quickly fix annoying tracking typos and create more specific, valuable events for analysis without having to wait on developer resources or make complex changes in GTM.

Of course, once your event data is clean, the real work of turning it into useful insights begins. Manually combining GA4 metrics with data from your CRM, ad platforms, and e-commerce store is often the most time-consuming part of marketing analytics. At Graphed, we've designed our service to eliminate this friction. We allow you to connect all your data sources in seconds and create real-time, interactive dashboards just by asking questions in plain English. For example, you can get answers by asking "show me a dashboard comparing Facebook Ads spend vs sessions and conversions from GA4 by campaign for the last 30 days,” and get an answer in seconds - no more wrangling CSVs or learning complex BI Tools. Give Graphed a try and spend your time acting on data instead of just chasing it down.