A practical event taxonomy for growing apps

A reliable taxonomy starts with decisions, not tool syntax. List the questions product, growth, and customer teams need to answer, then identify the smallest set of behaviours that can answer them.

Use object–action names such as report_created or invitation_accepted. Properties should add stable context: plan, entry point, role, or content type. Avoid encoding context inside an event name, where it becomes difficult to compare.

Assign an owner and a definition to every event. Before release, test expected triggers, forbidden duplicate triggers, identity stitching, and property types. Review the taxonomy quarterly; retiring stale events is part of maintaining trust.