Working · 2026-11Vendor claimGrowth opsAnalytics

Event taxonomy and naming convention

Define which events and properties you track, how they are named and how they fit together before instrumenting.

Also called: tracking plan, data taxonomy

Claim and evidence

The claimDefine which events and properties you track, how they are named and how they fit together before instrumenting.

No dated example yet. Treat this tactic as a hypothesis.

What the numbers show

No published number for this tactic has passed our word-for-word check yet, so there is no chart.

Why it works

Diagram, not data
Start frombusiness goalsBreak metricsinto eventsOne namingconvention andcasingReview andversion withdevelopers
Start from business goalsBreak metrics into eventsOne naming convention and casingReview and version withdevelopers

Consistent names prevent duplicate and unusable events when several teams send data. Starting from business goals keeps the plan lean.

How to run it

  1. Define business objectives
  2. Break key metrics into events
  3. Set one naming convention with consistent casing
  4. Define properties consistently across events
  5. Review and version the plan with developers

Ways to run it

Design options to test, not promised results.

  1. Option AObject-action names

    Name every event as an object plus a past-tense action with one fixed casing.

  2. Option BShared property dictionary

    Define each property once and reuse the same name and type across all events.

  3. Option CVersioned tracking plan

    Keep the plan in a reviewed, versioned document that developers sign off before instrumenting.

Dated examples

No dated example yet. Treat this tactic as a hypothesis.

Does it still work?

Workingas of 2026-11

Amplitude docs updated 2026-09-09; the same principle appears in other analytics tools but those pages were not fetched. source

Risks

  • Inconsistent casing creates separate events
  • Over-tracking creates clutter

Sources

  1. amplitude.com · Amplitude docs · 2026-09-09
    “A taxonomy defines which events and properties you track, what you name them, and how they fit together.”
    ✓ quote checked word-for-word on the page
  2. amplitude.com · Amplitude docs · 2026-09-09
    “Amplitude captures `Song Played` and `song played` as two separate events.”
    ✓ quote checked word-for-word on the page

Change log

  • 2026-11-20 — harvest v0.1 (ops-ai)