VANKPA
The decision
An event naming convention should let the team understand what happened and compare it consistently over time. Define the action, trigger, parameters, and owner together. Similar names can hide different behavior if the underlying definitions are not shared.
In practice
A lead form start and a completed inquiry should remain distinct. A click on a contact link is also different from a message received. Keep those stages visible so reporting does not inflate outcomes by combining unrelated signals.
- Create an event dictionary, review implementation against it, and test representative journeys.
- Document changes and retire obsolete events deliberately.
- Let report users inspect the meaning of the measures rather than infer it from a label.
When to take the next step
Agree names before implementing new tracking or combining reports. Trace a representative customer action and verify that every team describes the event the same way.
Questions clients ask
Should event names use business language?
Use clear, stable names the implementation and reporting teams can connect to an agreed definition.
What should the dictionary record?
The trigger, meaning, parameters, exclusions, owner, and any version changes.