Data taxonomy creation

A data taxonomy is like a dictionary for your product data — it defines what each piece of data means and how it should be named. Just like how a library organizes books by categories, your data needs a clear organization system that everyone understands.

Good names help everyone understand what the data means without having to ask around. For example, instead of "btn_clk", use "signup_button_clicked" — it's immediately clear what this event tracks. Follow a consistent pattern for all events.

Here are some best practices:

• Use the format "object_action" like "message_sent" or "profile_updated." For more detailed events, add relevant details at the end: "video_played_duration" or "article_shared_platform."
• Keep names in lowercase, use underscores between words, and avoid spaces or special characters.
• Common events should be named similarly across features. If you track button clicks, always use "_clicked" (not sometimes "_pressed" or "_tapped"). Use "started," "completed," "failed," or "updated" consistently for process stages. This makes it easier to find and compare related events across your product.
• Document these naming rules in a shared place like Notion or Confluence so all team members use the same terms when working with data.