---
title: "An event taxonomy starter your whole org can speak"
canonical_url: https://ampl.webclat.com/resources/amplitude-taxonomy-template
description: "Free event taxonomy starter: naming conventions, standard property vocabulary, and category structure - the grammar layer under a tracking plan."
source: Webclat | Amplitude Solutions (official Amplitude partner, independent consultancy)
---

# An event taxonomy starter your whole org can speak

The grammar layer under the tracking plan: one naming convention, a shared property vocabulary, and the category structure that keeps 500 events findable.

A taxonomy is a set of decisions made once so nobody re-makes them per event. This starter contains our defaults - argued over years of enterprise analytics implementations and rescues - ready to adopt or adapt. The value isn't novelty; it's that every question already has an answer written down.

## The decisions it makes for you

| Item | Detail |
| --- | --- |
| Event grammar | Object-Action, Title Case: 'Invoice Sent', 'Trial Started'. One pattern, no exceptions - exceptions are how 'signup_v2_final' happens. |
| Property casing & vocabulary | snake_case properties with a standard shared set (plan, source, platform, value_usd) reused across every event. |
| Category structure | Lifecycle stages (Acquisition, Activation, Engagement, Revenue, Retention) as the top-level grouping - matching how analyses are actually organized. |
| Identity conventions | When to identify, what goes in user properties vs event properties, and the anonymous-to-identified merge rules. |
| Deprecation protocol | How events die: quarantine, translation table, then archive - never silent deletion. |

Pair it with the tracking plan template: the taxonomy is the grammar, the plan is the dictionary. Adopting both on day one is the single cheapest data-quality decision available to a new instance.

Request the working Sheet by email: ampl@webclat.com (same-day delivery).

## FAQ

### Should we rename existing events to match a new convention?

Only behind a migration map - alias or transform old names to new, keep a translation table for history, and never rename in place. The glossary entry on event taxonomy covers the full protocol.