---
title: "Analytics instrumentation glossary | Skene"
description: "Terms for analytics instrumentation: events, payloads, drift, baseline manifests, semantic diffs, and the five ways coding agents break tracking."
url: https://www.skene.ai/resources/glossary
doc_version: "eda50510690e"
last_updated: 2026-11-04
---

Resources / Glossary

# Analytics instrumentation glossary

This glossary defines the terms you meet when a funnel stops matching the product and engineering explains why: analytics calls, event taxonomy, instrumentation drift, and the failure modes that show up when coding agents change instrumented code. To see a renamed event caught on a pull request, read [how Skene works](https://www.skene.ai/product/how-it-works).

## [Analytics call](https://www.skene.ai/resources/glossary/analytics-call)

Calls

A statement in your product's code that records an event, such as a signup. In a Supabase-first setup, it is a write into a Postgres table.

## [Event name](https://www.skene.ai/resources/glossary/event-name)

Calls

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

## [Payload (event properties)](https://www.skene.ai/resources/glossary/payload)

Calls

The object you write alongside the event name, carrying contextual properties that land on the event row in your database.

## [Identify call](https://www.skene.ai/resources/glossary/identify-call)

Calls

The call that ties subsequent events to a known user identity, typically by mapping an anonymous ID to a real user ID.

## [Event taxonomy](https://www.skene.ai/resources/glossary/event-taxonomy)

Concepts

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

## [Instrumentation surface](https://www.skene.ai/resources/glossary/instrumentation-surface)

Concepts

The total set of analytics calls in a codebase. Skene's pull request reviews check it for removed or broken tracking.

## [Baseline manifest](https://www.skene.ai/resources/glossary/baseline-manifest)

Concepts

The recorded state of an instrumentation surface at a point in time, used as the comparison point for future PRs.

## [Instrumentation drift](https://www.skene.ai/resources/glossary/instrumentation-drift)

Concepts

Unintended changes to analytics calls between two states of a codebase. Often introduced by refactors or coding agents.

## [Semantic diff](https://www.skene.ai/resources/glossary/semantic-diff)

Concepts

A comparison that examines the meaning of a change rather than only its text.

## [Removed event](https://www.skene.ai/resources/glossary/removed-event)

Failure modes

An analytics call that existed in the previous version of the codebase and no longer exists in the new one.

## [Renamed event](https://www.skene.ai/resources/glossary/renamed-event)

Failure modes

An analytics event whose name string changes between two states of the codebase, splitting funnels across two names.

## [Moved event](https://www.skene.ai/resources/glossary/moved-event)

Failure modes

An analytics call that still exists in the codebase but now fires from a different place in the code than before.

## [Altered payload](https://www.skene.ai/resources/glossary/altered-payload)

Failure modes

A change to the properties object of an analytics call: renamed key, dropped key, or changed type.

## [Conditional firing change](https://www.skene.ai/resources/glossary/conditional-firing-change)

Failure modes

A change to the if-block guarding an event. The event still fires, but for a different set of users or sessions.

## [Customer Data Platform (CDP)](https://www.skene.ai/resources/glossary/cdp)

Tools

A tool that ingests events from your app and fans them out to multiple downstream destinations. Segment, RudderStack, Hightouch Events.

## [Schema registry](https://www.skene.ai/resources/glossary/schema-registry)

Tools

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

## [MCP (Model Context Protocol)](https://www.skene.ai/resources/glossary/mcp)

Tools

An open protocol for letting AI agents call out to external tools. Skene runs an MCP server that coding agents call to check their tracking changes before they open a PR.

## [Coding agent](https://www.skene.ai/resources/glossary/coding-agent)

Coding agents

An AI tool that reads and writes code: Cursor, Claude Code, Codex, Devin, Aider. The category Skene is built to live alongside.

## [Side effect](https://www.skene.ai/resources/glossary/side-effect)

Coding agents

Code that affects something outside the function it lives in. Analytics calls are side effects. So are logs, emails, and metric increments.

## [Funnel](https://www.skene.ai/resources/glossary/funnel)

Business

A sequence of events users move through. When one step's event is renamed or removed, the funnel chart shows a drop that never happened.

## [Conversion event](https://www.skene.ai/resources/glossary/conversion-event)

Business

An event that represents a desired outcome, usually tied to revenue. The most expensive thing to lose instrumentation on.

## [Activation event](https://www.skene.ai/resources/glossary/activation-event)

Business

The event that marks when a new user reaches first value. Usually one of the most-watched metrics in product orgs.

## [Cohort](https://www.skene.ai/resources/glossary/cohort)

Business

A group of users defined by a shared property or behaviour. Most retention analysis runs on cohorts.

## [Measurement window](https://www.skene.ai/resources/glossary/measurement-window)

Business

The period after a launch whose data is read against the plan's target, such as the first 14 days after launch.

## Sitemap

- [Markdown sitemap](https://www.skene.ai/sitemap.md): every page on this site, with its markdown counterpart.
- [Index for language models](https://www.skene.ai/llms.txt): the same set as a link-dense index.
- [Full corpus](https://www.skene.ai/llms-full.txt): reference content concatenated as plain text.
