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

Event taxonomy

The set of event names and properties a product agrees to emit, and the rules for naming them.

Concepts

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

Definition

An event taxonomy is the deliberate design of what events your product emits, what each event means, and what properties accompany them. A good taxonomy is small, descriptive, and stable. A bad taxonomy is ad-hoc, redundant, and changes whenever a new developer adds an event.

Stability matters more than completeness

A taxonomy with 30 well-defined events that stay stable beats a taxonomy with 300 events that drift constantly. Dashboards and funnels are built against names that exist today; every rename means re-doing those dashboards.

Related terms

  • Event name
  • Schema registry
  • Instrumentation surface
Skene

Product

How it worksFeaturesArchitectureIntegrationsSecurityPricing

Resources

DocumentationGlossaryPlaybooksBlog

Company

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