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

Event name

The string identifier passed to an analytics call, used to group occurrences of the same thing on a dashboard.

Calls

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

The event name is the first positional argument in most analytics SDKs: `posthog.capture('checkout_completed', ...)`, `mixpanel.track('signup', ...)`. Dashboards group occurrences by exact string match, so `checkout_completed` and `checkoutCompleted` are different events even when they describe the same user action.

Common conventions

Most teams pick one casing convention (snake_case is the most common) and stick to it. A few teams use `Object Verb` casing (Segment's recommendation). The choice matters less than consistency. Renames after the fact split funnels.

Related terms

  • Renamed event
  • Event taxonomy
  • Analytics call
Skene

Product

How it worksFeaturesArchitectureIntegrationsSecurityPricing

Resources

DocumentationGlossaryPlaybooksBlog

Company

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