Skip to content
Resources / Glossary

Renamed event

An analytics event whose name string changes between two states of the codebase, splitting funnels across two names.

Failure modes

About this term

This page is part of the Skene analytics instrumentation glossary. Use it as a reference when writing specs, dashboards, or playbooks.

Canonical glossary index: /resources/glossary

How it happens

An agent (or a developer being tidy) standardises casing or naming conventions. checkout_completed becomes checkoutCompleted, or order_placed, or vanishes into a constant in another file. Each is a legal change. None of them updates the dashboards downstream.

What breaks downstream

Old data uses the old name; new data uses the new name. The funnel splits in two. Time-window metrics show artificial dips and spikes during the transition. Recovering means UNION-ing two event names in every affected query.

Renames usually arrive with a cleanup, when a developer or a coding agent brings event names in line with a naming convention. Queries match the event name as an exact string, so reports built on the old name stop counting once the change ships. A common mistake is to treat a rename as cosmetic, when every chart reads it as one event ending and another starting. An event taxonomy with agreed naming rules makes renames rarer, and a schema registry gives reviewers the old name to check.