Guide 162 · Events · GA4 + Tag Manager

Rename an event in GA4: there is no rename button — the supported path is Modify, and history stays under the old name

Checked 11 November 2026 · Verification: event reference validated structurally (event, parameters, rules, worked example); worked example recomputed · Steps traced to Analytics Help, opened 11 November 2026 · 6-minute read

An event named lead_form that should have been generate_lead cannot be renamed with a button, because GA4 has no rename button for events. The supported path is the Modify event feature for an event created in the interface, or a new event created from the old one — and either way the history stays under the old name. This guide renames a created event the supported way and shows exactly where the history splits.

Expected signal

After the edit, new events arrive under the new name in DebugView and in the Events report, and the old name's row stops growing — the history under the old name stays exactly where it was, under the old name.

Download the reference: the rename-event reference (JSON) (2314 bytes, MD5 f97bcb7b334140d8cbffde6943af7f34). It lists the worked example — lead_form renamed to generate_lead — the old and new names with their lengths against the 40-character limit, and the rules: no rename button, history is never renamed, and a created event is the supported path. The rename itself is not in the file: it happens in the interface.

What you need

Viewer access or above at the property level. The modify path needs Viewer or above; marking the renamed event as a key event needs Marketer or above.
A created event to rename. Here it is lead_form, a created event that should have been the recommended generate_lead from the start.
The new name, checked against the rules first. The new name is generate_lead: 13 characters, under the 40-character limit, lowercase letters and underscores, starting with a letter.

The worked example

The worked example is the rename of lead_form to generate_lead. The numbers that matter are the two lengths and the history that stays put.

Measure	Value
Old name length (lead_form)	9
New name length (generate_lead)	13
Length change	13 - 9 = 4
Name limit	40
Events collected under the old name	412
Events moved to the new name	0

Those figures were recomputed here before publication: 13 minus 9 is 4 characters added; both names are within the 40-character limit; and 0 of the 412 events collected under lead_form move to the new name. The rename itself is the standard form:

Before: lead_form
After:  generate_lead

The trace

Confirm the event is a created one. The modify path edits events created in Analytics. If the event is sent by a tag — a custom event from Tag Manager — the rename happens in the tag, by changing the Event Name in the GA4 Event tag, not in the interface. This guide renames the created event lead_form.
Open the Events page. In Analytics, go to Admin, then under Data display, click Events. You must be signed in to a Google account. This step needs a Google sign-in, so it was traced to Google's documentation, not run here.
Open the created event. In Custom configurations, click Custom events and choose a data stream. In the Custom events table, click lead_form to modify it.
Change the event name. In the Event name field, replace lead_form with generate_lead. Leave the source event and the conditions untouched: the rename changes the name, not what the event measures. The new name is a recommended name, so it also gains the lead reports that the custom name never had.
Save the edit. Click Save. From this point on, the event is collected under generate_lead. The 412 events already collected under lead_form stay under lead_form: no rename, no rewrite, no backfill.
Check it in DebugView and note the split. Fire the event yourself and open DebugView (Admin, then Data display, then DebugView) to confirm it shows as generate_lead. Then open the Events report and note the two rows: lead_form, which stops growing, and generate_lead, which starts at zero. Anyone reading the report needs to know the split happened on this date, or the two rows read as two different events.

Dead ends

DEAD END — LOOKING FOR A RENAME BUTTON. There is none. The Events table has no rename action, and the three-dot menu offers marking as a key event, not a new name. The modify path is the only interface route, and it only covers events created in the interface.

DEAD END — RENAMING THE TAG AND EXPECTING HISTORY TO FOLLOW. Changing the Event Name in a GA4 Event tag renames what is sent from that day on. It does not rename a single event already collected. A tag rename splits history exactly the way an interface rename does.

DEAD END — RENAMING TO A RECOMMENDED NAME WITHOUT THE PARAMETERS. A renamed event gains the recommended reports only if it also sends the recommended parameters. Renaming lead_form to generate_lead without adding value and currency gives the name but not the revenue reporting.

End state

One event, one new name, two rows in the report for a while. New events arrive as generate_lead and old history stays as lead_form, and the split is written down with its date so the report reads correctly. The lesson that survives the rename is the one in the naming-rules guide: plan names first, because the rename is cheap and the split history is permanent.

Sources

Analytics Help — Create or modify key events — modify an event in Analytics: Custom configurations, then Custom events, then choose a data stream, then click the event, modify the conditions or parameters, and save; modifications overwrite existing events
Analytics Help — [GA4] Collection and configuration limits — event names are case-sensitive, up to 40 characters, letters, numbers, and underscores, starting with a letter
Analytics Help — [GA4] Recommended events — generate_lead is a recommended event for all properties and for lead generation

Checked 11 November 2026. The click paths above are the ones in Google's help and developer pages, opened 11 November 2026. No step in this guide was run inside a live Analytics property or a live Tag Manager container, because both need a Google sign-in and this site does not sign in as anyone. What was run: the reference file was validated structurally in Python 3.12.3 — it parses, the old and new names are present with their lengths — and the lengths were recomputed: lead_form is 9 characters, generate_lead is 13, a change of 4, both within the 40-character limit; 0 of the 412 events under the old name move. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map.