Service model

Event taxonomy guide

A durable naming system for application analytics—so redesigns do not shatter your funnels.

Object before surface

Name the business object—order, profile, project—not the screen title. Surfaces change; objects persist through redesigns.
Action as intent

Use verbs that describe user intent: submit, invite, export, renew. Avoid verbs tied to widgets like click_button_primary.
Properties with consumers

Every property needs a known chart, segment, or experiment. If nobody consumes it after two quarters, schedule removal.
Owners on the sheet

Assign a product or engineering owner beside each event. Taxonomy drift is a people problem before it is a tooling problem.
Release dual-write window

When renaming, dual-write for one or two releases so historical funnels stay comparable, then retire the legacy name deliberately.

Ready to apply this to your application?

Most teams start with an event dictionary rebuild. If you already know which paths matter, conversion path mapping may be the better first step.