Draft an analytics tracking requirement templated document for Mixpanel for adding tracking code to add custom events and also setting user property. Do not include actual code, just simple and direct instructions easy to understand
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
Certainly! Hereâs a simple, direct template for a Mixpanel analytics tracking requirement document, based on best practices and guidance from the knowledge sources:
Mixpanel Analytics Tracking Requirements
1. Overview
This document outlines the requirements for implementing Mixpanel analytics tracking in our product. It covers the addition of custom event tracking and the setting of user properties to enable robust analysis of user behavior and demographics.
2. Event Tracking
- Define Events: List the key user actions to be tracked (e.g., âSign Upâ, âPurchase Completedâ, âButton Clickedâ).
- Event Naming: Use a consistent naming convention, preferably in the format object_action (e.g., video_watched, page_viewed). Event names should be short, descriptive, and use snake_case for consistency.
- Event Properties: For each event, specify the properties to capture additional context (e.g., for âSign Upâ: source, country, OS). Properties should be relevant to the event and help answer key business questions.
- Where to Add Tracking: Specify the exact location in the codebase or user flow where each event should be tracked (e.g., after a successful sign-up, when a purchase is completed).
- Avoid Dynamic Event Names: Do not create event names dynamically. Use static event names and capture dynamic values as properties.
3. User Property Setting
- Define User Properties: List the user attributes to be set (e.g., email, country, subscription type). - When to Set Properties: Specify when user properties should be set or updated (e.g., after user registration, on profile update). - Consistency: Ensure user properties are updated consistently to reflect the latest user state.
4. General Best Practices
- Track Only What Matters: Focus on events and properties that align with business metrics and KPIs. - Use Super Properties: For properties that should be included with every event (e.g., userâs source, initial referrer), register them as super properties. - Case Sensitivity: Remember that Mixpanel treats strings as case-sensitive; maintain consistency in naming.
5. Documentation
- Tracking Plan: Maintain a tracking plan document listing all events, properties, and user properties being tracked, including their definitions and intended use. - Review and Update: Regularly review and update the tracking plan as product features evolve.
This template is based on Mixpanelâs recommended tracking strategy and best practices for defining events and user properties, ensuring your analytics implementation is structured and actionable [Build Your Tracking Strategy] [Events and Properties Best Practices] [What to Track].
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.
Let me check the knowledge base for you again. One moment! đ
When a user property (such as "age" or "subscription plan") can change over time, Mixpanel recommends tracking these changes carefully. User Profiles in Mixpanel always reflect the latest value of each property, and all events are joined with the current state of the user profile, not the value at the time the event occurred. Therefore, if you want to analyze how a property changes over time, you should:
- Update the user property at login: Each time a user logs in, check if the property (e.g., "age") has changed. If it has, update the user property in Mixpanel. - Track the property as an event property if you need historical context: If you need to analyze how the property changed at specific points in time, also include it as an event property on relevant events (e.g., "User Logged In" event with the current "age" as a property).
Example Instruction for Tracking Age at Login:
- On user login, retrieve the user's current age. - Compare the retrieved age with the value stored in Mixpanel (if available). - If the age has changed, update the "age" user property in Mixpanel. - Optionally, include the current "age" as an event property on the login event for historical analysis.
This approach ensures that the user profile always has the latest value, and you can analyze changes over time if you also track the property as an event property. Mixpanel documentation highlights that user profiles only store the latest value, so for properties that change over time, tracking them as event properties is recommended for time-based analysis [User Profile FAQ].
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.
Let me check the knowledge base for you again. One moment! đ
To add a property such as unique_id to the event payload, simply include it as a property when tracking the event. Do not call the identify function; just add unique_id as a regular event property.
Instruction: - When tracking the event, add unique_id as a property in the event payload. - Do not call the identify function or set the user identity with this value.
This approach ensures unique_id is available for analysis as an event property, but it will not affect user identification or profile merging in Mixpanel. The knowledge sources confirm that you can add any custom property to an event payload, and only calling identify() will set the user identity in Mixpanel [Reserved Event Properties].
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.
Let me check the knowledge base for you again. One moment! đ
Let me check the knowledge base for you again. One moment! đ
To instruct adding tracking code to set a user property when the target response for a user is YES, you can say:
When the target response for a user is YES, set a user property (e.g., "target_response") to "YES" using the appropriate Mixpanel method for setting user properties. Ensure that the user is identified before setting the property, so the update is associated with the correct user profile.
For example, in JavaScript, you would call mixpanel.people.set({ target_response: "YES" }) after identifying the user [Storing User Profiles - Javascript].
This instruction ensures the user property is updated in Mixpanel whenever the user's response is YES.
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.
To instruct adding tracking code to set a user property when the target response for a user is YES, you can say:
Instruction: When the target response for a user is YES, set a user property (e.g., "target_response") to "YES" in Mixpanel. This should be done by calling the appropriate method to set user properties after the response is received.
For example, in JavaScript, you would call the .people.set() method after identifying the user, and set the property accordingly. This ensures the user profile reflects the latest value for "target_response" [Storing User Profiles - Javascript].
Example instruction: - After a user responds "YES" to the target question, set the user property "target_response" to "YES" in Mixpanel. - Ensure the user is identified before setting the property.
This approach is consistent across Mixpanel SDKs: set the user property when the condition is met, so the user profile is updated with the latest value.
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.
Let me check the knowledge base for you again. One moment! đ
To instruct adding tracking code to set a user property when the target response for a user is YES, you can say:
When the target response for a user is YES, set a user property (for example, target_response) to "YES" using the appropriate Mixpanel method for setting user properties. Ensure this is done after the user is identified, so the property is associated with the correct user profile.
For example, in the JavaScript SDK, you would use:
- Identify the user (if not already done).
- Set the user property with .people.set({ target_response: "YES" }).
This ensures the user profile in Mixpanel reflects the latest value for the property when the response is YES [Storing User Profiles - Javascript].
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.
