Event Naming Convention

An event naming convention is the agreed rule for how event names are formed, so the event list stays predictable as the number of events grows.

A working convention locks three things: the case style such as snake_case, the order of the parts (object first then action, article_viewed rather than viewed_article), and the verb tense, usually past; alongside these, a prefix is normally reserved for events the platform itself emits. It matters because the name is the primary key of the whole dataset and correcting past names is expensive. The common failure is leaving the convention in a document: without a check at code review or a warning inside the tool, drift starts within weeks. Fine detail does not belong in the name either, so checkout_button_blue_clicked should be one event with a colour property.