Event Naming Convention: Standardized Taxonomy Table Templates

Give me sentence starters or a template for creating an event and user property taxonomy table that helps describe and standardize event naming convention to surface what the event does without spending a lot of time reading the event description so the event describes the action taking place

2 comments

kapa.ai
APP
·
·
Certainly! Mixpanel documentation and best practices recommend using a clear, consistent naming convention for events and properties, typically in the format (Object) (Verb) (e.g., page_viewed, song_played). This approach helps surface what the event does at a glance, reducing the need to read lengthy descriptions. Here are sentence starters and a template you can use to create a taxonomy table for your events and user properties: ---
Event & Property Taxonomy Table Template
Sentence Starters for Event Naming
- [Object] [Action]: e.g., document_created, video_watched, purchase_completed - [Feature] [Interaction]: e.g., chat_opened, ai_prompt_sent - [Page/Screen] [Viewed/Visited]: e.g., home_page_viewed, profile_screen_viewed
Sentence Starters for Property Naming
- [Property] describes [aspect of event]: e.g., signup_type describes the method of signup - [Property] indicates [user attribute]: e.g., country indicates the user's country - [Property] captures [contextual detail]: e.g., button_color captures the color of the button clicked---
Best Practices
- Use snake_case for consistency and robustness, especially for downstream data use. - Avoid abbreviations and jargon; use clear, descriptive terms. - Do not create event or property names dynamically (e.g., avoid purchase_2024-06-01). - Use properties to add context, rather than creating overly specific events (e.g., use add_to_cart with an item property instead of add_shirt_to_cart, add_hoodie_to_cart, etc.) - Document your naming standards and keep your taxonomy table updated as a living document.These practices and templates will help your team quickly understand what each event does, just by looking at the event name and its key properties, without needing to read through detailed descriptions every time. For more details, see the Mixpanel documentation on event and property naming conventions and tracking plan methodology.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
kapa.ai
APP
·
·
Hi event, Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai

Loading comments

kapa.ai
APP
·
·
Certainly! Mixpanel documentation and best practices recommend using a clear, consistent naming convention for events and properties, typically in the format (Object) (Verb) (e.g., page_viewed, song_played). This approach helps surface what the event does at a glance, reducing the need to read lengthy descriptions. Here are sentence starters and a template you can use to create a taxonomy table for your events and user properties: ---
Event & Property Taxonomy Table Template
Sentence Starters for Event Naming
- [Object] [Action]: e.g., document_created, video_watched, purchase_completed - [Feature] [Interaction]: e.g., chat_opened, ai_prompt_sent - [Page/Screen] [Viewed/Visited]: e.g., home_page_viewed, profile_screen_viewed
Sentence Starters for Property Naming
- [Property] describes [aspect of event]: e.g., signup_type describes the method of signup - [Property] indicates [user attribute]: e.g., country indicates the user's country - [Property] captures [contextual detail]: e.g., button_color captures the color of the button clicked---
Best Practices
- Use snake_case for consistency and robustness, especially for downstream data use. - Avoid abbreviations and jargon; use clear, descriptive terms. - Do not create event or property names dynamically (e.g., avoid purchase_2024-06-01). - Use properties to add context, rather than creating overly specific events (e.g., use add_to_cart with an item property instead of add_shirt_to_cart, add_hoodie_to_cart, etc.) - Document your naming standards and keep your taxonomy table updated as a living document.These practices and templates will help your team quickly understand what each event does, just by looking at the event name and its key properties, without needing to read through detailed descriptions every time. For more details, see the Mixpanel documentation on event and property naming conventions and tracking plan methodology.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
kapa.ai
APP
·
·
Hi event, Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai

2 comments

2 comments

Event &amp; Property Taxonomy Table Template

Sentence Starters for Event Naming

Sentence Starters for Property Naming

Best Practices

Event &amp; Property Taxonomy Table Template

Sentence Starters for Event Naming

Sentence Starters for Property Naming

Best Practices

Event & Property Taxonomy Table Template

Event & Property Taxonomy Table Template