Description: You can now rename a custom event or a labeled event without breaking anything that uses it. Renaming changes only the display name. Charts, cohorts, metrics, experiments, flags, guides and surveys, and saved segments keep working and show the new name. Create, rename and delete actions for custom events also now show up in the activity feed.
Why: Until now, a custom event's name was both its label and the key every chart used to find it. Renaming one silently broke every chart, cohort and metric that used it. The rename also didn't show in the activity feed, so to customers the event seemed to vanish with no trace. Custom events now work like regular events: a stable internal key plus a display name you can edit.
What's new:
• Renames don't break anything: renaming changes only the display name. Every chart, cohort, metric and other object that uses the event keeps returning data, with no manual updates.
• Labeled events are covered too: labeled (autocaptured) events get the same fix.
• Exports show the new name: CSV exports and event summaries show the new name, not the old one.
• MCP renames are safe: renames made through Amplitude MCP also change only the display name.
• Audit visibility: create, rename and delete actions on custom events appear in the activity feed with who made the change, when, and the old → new name. You can search them by event name, so CS and support can answer "what happened to event X?" without escalating.
Where: Amplitude Data > Events > select a custom or labeled event > edit the name. Changes appear in the activity feed.
Customers Impacted: Admins, Managers and Members can rename custom events. In orgs that use RBAC, any user with the Manage Data Enrichment permission can rename them.