Event Naming Convention

An event naming convention standardizes the names used for interactions recorded in an analytics system. Teams might choose descriptive lowercase names with underscores, such as quote_request_started and appointment_booked, along with defined rules for parameters and naming ownership. Consistency matters because inconsistent event names can fragment reporting: quote_submit, Quote_Submit, and lead_sent may describe the same business action but appear as different events.

In Google Analytics 4 (GA4), event names are case-sensitive, must start with a letter, and may contain letters, numbers, and underscores but not spaces. Google also reserves some names and prefixes. These are product requirements, not universal rules for all analytics tools. A sensible naming plan therefore has two layers: platform constraints that must be obeyed and a business vocabulary that makes reports understandable to nontechnical colleagues.

Before implementation, document each event's exact trigger, intended meaning, responsible team, parameters, and whether the event is suitable to mark as a key event. For a small home-service business, form_started should not be treated as interchangeable with form_submitted or lead_qualified. Test events on desktop and mobile and check that duplicate listeners do not inflate counts. A convention improves measurement governance; it does not make a broken tracking implementation accurate by itself.