Analytics measurement and metrics
Analytics events: choose and name the right ones
Create a small event taxonomy that stays understandable as your site and product grow.
Events are the vocabulary of a measurement system. A tidy taxonomy lets people compare behaviour over time without guessing what similarly named actions mean.
Name actions by meaning
Use stable, readable names that describe what happened, such as signup_completed or checkout_started. Avoid names tied to a temporary button label or implementation detail. Document trigger conditions and examples so developers and analysts implement the same meaning.
Put it into practice
See your traffic, funnel steps and site performance clearly in Alexander.
Try Alexander freeKeep event properties purposeful
Add only properties needed to answer a planned question, such as plan type or page category. Never send personal data or arbitrary form contents. Use controlled values rather than dozens of spelling variants, and keep high-cardinality data out unless there is a justified use.
Version and verify changes
Test the event schema, firing count and key browser paths before release. When meaning must change, document the date and consider a new name rather than silently redefining history. Review the taxonomy periodically and retire unused events deliberately.