Documentation standards

Documentation helps everyone understand how your analytics is set up and how to use it correctly. Good documentation is like a manual for your data — it explains what you track, why you track it, and how to use the information. Keep it simple and up-to-date.

So, basic documentation should essentially cover these 3 things:

• A list of all events and their meanings
• A guide to your naming patterns
• Instructions for common tasks

For example, document that "user_signup_completed" tracks successful account creation, while "user_signup_failed" tracks when something goes wrong during signup, with notes about what data each event includes.

Store documentation where everyone can find it easily, like Notion, Confluence, or a shared Google Doc. Include practical examples — if you track "purchase_completed," show a real event with its attributes. Update docs whenever you add new tracking or change existing events to avoid confusion.