# Event Taxonomy

An event taxonomy is a governed naming and classification system for product events and properties, designed to keep behavioral data consistent.

- Type: artifact
- Domain: Data, experimentation & growth
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/event-taxonomy/>)

## What it means

An event taxonomy defines how meaningful product occurrences are represented in analytics data. It establishes event and property names, grammar, casing, entities, shared context, allowed values, ownership, and lifecycle rules. The taxonomy is the vocabulary; a tracking plan lists the specific events to implement.

## Why it matters

Without shared rules, equivalent actions appear under several names, details become duplicate events, and analysts cannot compare journeys confidently. A clear taxonomy improves discovery, implementation consistency, governance, and trust while limiting a sprawling catalog of ambiguous clicks.

## When to use it

Create a taxonomy before substantial instrumentation, when multiple products or teams share data, or when an existing event catalog has become inconsistent. Apply it to new events and migration work, but avoid renaming historical concepts casually because downstream analyses may depend on them.

## How it works

1. Identify core entities and user actions from priority product questions and journeys.
2. Choose a readable naming pattern, grammatical tense, casing convention, and rules for events versus properties.
3. Define shared properties such as identifiers, platform, version, source, and timestamps with permitted values.
4. Document ownership, approval, deprecation, versioning, and privacy rules.
5. Validate incoming data against the taxonomy and review exceptions before expanding the vocabulary.

## A practical example

A commerce team standardizes past-tense object-action names such as “Product Viewed,” “Cart Updated,” and “Order Completed.” Channel, device, currency, and item count remain properties rather than spawning separate events. Deprecated names are mapped and monitored during a migration period.

## Where it breaks

A taxonomy cannot ensure correct firing logic, complete coverage, or useful analysis by itself. Overly rigid governance slows delivery, while overly generic events shift confusion into properties. Historical data may remain fragmented after conventions improve.

## Common mistakes

- Encoding every variation as a new event instead of a property.
- Using vague names such as “Clicked” without the object or business meaning.
- Changing conventions without migration, ownership, or deprecation rules.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/event-taxonomy/#visualization-event-taxonomy>)

## Sources

1. [Free Website Event Taxonomy Generator](<https://amplitude.com/taxonomy-generator>) — Amplitude · Product analytics taxonomy guidance
2. [The Foundation for Great Analytics Is a Great Taxonomy](<https://amplitude.com/blog/event-taxonomy>) — Amplitude · Industry practice article
3. [Official Events and Properties](<https://amplitude.com/docs/data/official-events-and-properties>) — Amplitude Docs · Official governance documentation

## Related topics

- [Instrumentation Plan](<https://wiki.soroush.uk/topic/instrumentation-plan/>)
- [Product Analytics](<https://wiki.soroush.uk/topic/product-analytics/>)
- [Metric Tree](<https://wiki.soroush.uk/topic/metric-tree/>)
