Pricing
Log inStart free
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

Glossary

Glossary

Analytics callEvent namePayload (event properties)Identify callEvent taxonomyInstrumentation surfaceBaseline manifestInstrumentation driftSemantic diffRemoved eventRenamed eventMoved eventAltered payloadConditional firing changeCustomer Data Platform (CDP)Schema registryMCP (Model Context Protocol)Coding agentSide effectFunnelConversion eventActivation eventCohort

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.

Related terms

  • Instrumentation drift
  • Removed event
  • Event name

Product data your GTM team can trust.

Product

Before you shipHow it worksFeaturesIntegrationsSecuritySupabasePricing

Developers

DevelopersSkene CloudMCP servervs coding agentsOpen sourceDocs

Resources

ResourcesGlossaryPlaybooksBlogReleases

Company

AboutCommunityEventsContactPrivacyTerms
© 2026 Skene Technologies. All rights reserved.