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

Schema registry

A central catalogue of event names and payload shapes that an analytics team agrees to. Sometimes called a tracking plan.

Tools

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

A schema registry (or tracking plan) is the canonical list of every event your product emits and what each payload should look like. Segment Protocols, Avo, and Mixpanel's Lexicon are common implementations. The point is to make the taxonomy explicit instead of implicit.

Tracking plan vs. Skene

A tracking plan declares what should fire. Skene validates that the calls in your repo still match what should fire after the next PR. The two are complementary: a tracking plan without code validation drifts; code validation without a tracking plan can flag drift but cannot say whether the drift was intended at the design level.

Related terms

  • Event taxonomy
  • Baseline manifest
Skene

Product

How it worksFeaturesArchitectureIntegrationsSecurityPricing

Resources

DocumentationGlossaryPlaybooksBlog

Company

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