To show the sum of session duration divided by the number of active users in a given timeframe (i.e., average session duration per active user), you can use Mixpanel’s Formula feature in Insights reports. Here’s how you can achieve this: 1. Create two metrics in your report:
- Sum of Session Duration: Use the “Aggregate Property” measurement to sum the “Session Duration (seconds)” property for your sessions.
- Active Users: Use the “Unique Users” measurement for the same timeframe.2. Add a Formula:
- Click the Metrics button and select Formula.
- Assign variable names to your two metrics (e.g., A for sum of session duration, B for unique users).
- In the formula field, enter A / B to divide the total session duration by the number of active users.
- If you want the result in minutes instead of seconds, use (A / B) / 60.This will give you the average session duration per active user for the selected timeframe.Reference:
Mixpanel documentation specifically describes using formulas to divide one metric by another, such as dividing session duration by 60 to convert to minutes, and using aggregate property measurements in combination with formulas to achieve per-user calculations. For more details, see the FAQ on session duration and Formulas in Insights.If you need to see a step-by-step example, refer to the linked FAQ and Insights documentation above.
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.
Hi Moritz H., 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
Yes, your understanding is correct and aligns with Mixpanel’s documented capabilities: - If "Purchase Completed" does not have the club id property, you can use the Borrowed Properties feature to bring the club id from "Purchase Started" onto "Purchase Completed". - You can then inline filter "Purchase Started" by club id = 123, and inline filter "Purchase Completed" by the borrowed club id = 123. - Additionally, you can hold the borrowed club id property constant in the funnel. This ensures that only users who have the same club id value (123) for both steps are counted as conversions.This setup will ensure your funnel only represents users who started and completed purchases for club id 123, and that the club id value is consistent across both steps—even though the original "Purchase Completed" event did not have the club id property. This approach is supported by Mixpanel’s documentation on both Borrowed Properties and holding a property constant in funnels Borrowed Properties Hold Property Constant.If you want to restrict your analysis to a specific club id and ensure consistency across steps, this is the correct method.
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! 📚
Yes, if you want to analyze your funnel for a specific club id (for example, only users interacting with club id = 123), you should: 1. Apply an inline filter for club id = 123 on both "Purchase Started" and "Purchase Completed" steps. This ensures that only events with that specific club id are included at each step. 2. Hold the club id property constant (using the borrowed property if needed). This ensures that, for each funnel attempt, the club id value remains the same across both steps.This combination guarantees that: - Only events with the specific club id are considered at each step (via inline filtering). - Only users who retain the same club id value across both steps are counted as conversions (via holding property constant).This approach is supported by Mixpanel’s documentation, which explains that inline filters add granularity to each step, while holding a property constant enforces consistency of the property value across steps Filters Hold Property Constant.If you only want to analyze a specific club id, using both inline filtering and holding the property constant is the correct and most precise method.
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! 📚
You do not need to use both inline filtering and holding the borrowed property constant. The best practice, according to Mixpanel documentation, is: 1. Create the borrowed property of club id from "Purchase Started" and apply it to "Purchase Completed" (so both events have the property). 2. Hold the borrowed property constant in your funnel. This ensures that only users who have the same club id value for both steps are counted as conversions.You do not need to add additional inline filters for club id on either step, unless you want to restrict your analysis to a specific club id (e.g., only club id = 123). Holding the property constant already ensures that the value matches across both steps for each user’s funnel attempt Hold Property Constant Borrowed Properties.In summary: Just create the borrowed property and hold it constant—no need for extra inline filtering unless you want to focus on a specific club id 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! 📚
Based on the knowledge sources, the recommended approach is to use the "Hold Property Constant" feature with the borrowed club id property from "Purchase Started" applied to both steps in your funnel.Here’s why: - Hold Property Constant ensures that only users who have the same club id value for both "Purchase Started" and "Purchase Completed" are counted as conversions. This is specifically designed for scenarios where you want to track users who complete all funnel steps with the same property value, such as club id. However, this requires that the property exists on both events. If "Purchase Completed" does not have club id, you should use the Borrowed Properties feature to bring the club id from "Purchase Started" onto "Purchase Completed" first, and then hold it constant in the funnel Hold Property Constant Borrowed Properties.- Filtering each step by club id (using inline filters) is less robust for this use case. Inline filters are applied pre-query to each step individually, but they do not guarantee that the same club id is used across both steps for a given user’s funnel attempt. Holding the property constant is specifically designed to enforce this requirement across steps Filters.Summary: - Use Borrowed Properties to bring club id from "Purchase Started" to "Purchase Completed" if needed. - Then, use Hold Property Constant on the borrowed club id property in your funnel. This approach is more accurate and purpose-built for your scenario than filtering each step separately.
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! 📚
