Most App Analytics dictionaries are autobiographies of panic. Someone needed a chart before a review, a developer added btn_click_final_v3, and three years later a new teammate is asked to explain a dip that nobody can find in the code.
At the Knowle table we use a spoken test. If you cannot say the event name in a stand-up without explaining the joke, it does not ship. Order submitted passes. Checkout success maybe does not. Version suffixes are a confession that the previous name was a guess.
We prefer object, then verb, then the few properties that change a decision: plan, ticket type, entry point. Properties that exist “in case we need them” become a second product that nobody staffs. In Signal Architecture we mark those properties in pencil and ask who will own the join when the schema drifts.
Deletion is part of naming. A good convention includes a retirement note: when the screen dies, the event dies, and the chart is archived with a sentence about what replaced it. That sentence is the difference between a ledger and a ruin.
If you want the worksheets we use for this, they live inside the flagship programme and, in shorter form, on the House Taxonomy page.