Skene
Product
Pricing
Docs
Blog
About
Log In
ProductPricingDocsBlogAbout
Log In
Resources / Glossary

Moved event

An analytics call that still exists in the codebase but now fires from a different control-flow context than before.

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

The call moves out of a conditional, into a different code path, or behind a feature flag. The call itself looks intact. What changed is when it runs.

What breaks downstream

Volume changes silently. A first-purchase event that used to fire inside `if (user.isFirstPurchase)` now fires on every purchase. Or a retention milestone that used to fire only after a real interaction now fires automatically. The event count looks fine; the meaning has changed.

Related terms

  • Conditional firing change
  • Instrumentation drift
Skene

Product

How it worksFeaturesArchitectureIntegrationsSecurityPricing

Resources

DocumentationGlossaryPlaybooksBlog

Company

AboutOpen sourceContactPrivacyTerms
© 2026 Skene. All rights reserved.
Privacy PolicyTerms of Service
Skene