← Back to the notebook
MarTech / 3 MIN READ

Give your events a vocabulary.

Useful analytics starts with shared meaning, before dashboards.

Sample essay · Original starter content for this website, ready for Divy’s review.

Name the thing that happened

An event name is a small agreement between product, engineering, and marketing. It should describe an observable action, such as a form submission, rather than an interpretation such as user engagement. Agree on naming conventions and write down what qualifies as an event before adding tracking code.

Keep a compact event dictionary

For each event, record its purpose, trigger, owner, and allowed properties. Distinguish an attempted action from a successful one. Keep property types consistent across platforms. A compact dictionary makes it easier to understand whether two tools are measuring the same behavior.

Verify the whole journey

Check one representative journey from interaction to collection to reporting. Look for duplicate firing, missing consent checks, and properties that contain unnecessary personal data. Instrumentation becomes useful when its meaning and limitations are understandable to the people making decisions from it.