Mixpanel Community Icon

kapa.ai any recomendation to make the Naming rule?

·
·

kapa.ai any recomendation to make the Naming rule?

  • Avatar of kapa.ai
    kapa.ai
    APP
    ·
    ·

    Please stand by camila as I search the knowledge base. I normally take about 15 seconds or so. đź‘‹

    Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai

  • Avatar of kapa.ai
    kapa.ai
    APP
    ·
    ·

    Based on the knowledge sources, here are recommendations for creating naming rules in Mixpanel:

    Event Naming Conventions

    1. Use consistent case format: Mixpanel is case-sensitive, so sign_up_completed and Sign_Up_Completed are considered different events. Snake_case (lowercase with underscores) is generally recommended as it's more robust, especially if you plan to export data to warehouses later. Creating a Tracking Plan2. Follow (Object) (Verb) format: Name events using the pattern of what was acted upon followed by the action, such as song_played or page_viewed. Events: Capture behaviors and actions3. Avoid dynamic naming: Don't create event names with changing values like Purchase (11-01-2019). Instead, create a static event name (Purchase) and use properties to capture dynamic values. Events: Capture behaviors and actions4. Balance granularity: Events should be neither too broad nor too specific. For example, instead of tracking Add Shirt to Cart, Add Hoodie to Cart, etc., track a single Add to Cart event with an Item property. Events: Capture behaviors and actions

    Property Naming Best Practices

    1. Maintain consistency: Use the same naming convention across all properties.2. Avoid abbreviations and jargon: Use clear, understandable names that anyone in your organization can understand. Creating a Tracking Plan3. Avoid prefixes: Don't use mp_ and $ prefixes in your custom property names. Creating a Tracking Plan4. Be consistent with property values: Ensure values like "Premium" vs. "premium" are standardized. Creating a Tracking Plan

    Documentation and Governance

    1. Create a tracking plan: Document your events and properties in a shared tracking plan that serves as a living document. Creating a Tracking Plan2. Use Data Standards feature: Enterprise customers can use the Data Standards feature to enforce naming conventions (snake_case, camelCase) and other metadata requirements. Data Standards: Keep Your Data Clean and Consistent3. Maintain consistency across tools: Use the same naming conventions across all your analytics and optimization tools to avoid confusion. Product analytics improves patient experienceFollowing these naming conventions will help ensure your Mixpanel implementation remains clean, consistent, and easy to use for everyone in your organization.

    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.