Understanding Discrepancies in 4-Step Funnel Values in Mixpanel
Why is it that when you have a 4 step funnel in Mixpanel, the values are different for event triggered? kapa.ai
Why is it that when you have a 4 step funnel in Mixpanel, the values are different for event triggered? kapa.ai
The difference in values for events triggered in a 4-step funnel in Mixpanel can be attributed to several factors. Let me explain the main reasons based on the information from Mixpanel's documentation: 1. Funnel Calculation Method: Funnels in Mixpanel calculate conversions based on users completing steps in a specific order within a given time frame. This means that not all events triggered will necessarily be counted in the funnel. As stated in the Funnels documentation: "In the Funnels report, users will need to perform Step 1 event, in order for their Step 2 event to be counted. Insights, on the other hand, will count the Step 2 event, even if the user does not perform the Step 1 event."2. Loose Ordering: Mixpanel allows for "loose ordering" in funnels, which means users can perform other actions between funnel steps. This can lead to differences in event counts. As explained in the Funnels FAQ: "Users can complete the steps you designate in your funnel in loose order. Loose order means that a customer can engage in other actions in between funnel steps, as long as they complete all the funnel steps in order."3. Conversion Window: Funnels have a conversion window, which is the time frame within which a user must complete all steps to be counted as a conversion. Events outside this window may not be included in the funnel calculation.4. Filtering and Attribution: The use of filters, especially per-step filters, can affect which events are included in the funnel. As described in the Per-Step Filtering documentation: "Per-step filters are performed pre-query. Thus, these filters will impact your funnel's conversion by removing events that don't qualify from consideration of being included in a funnel calculation."5. Counting Method: The counting method you choose (Uniques, Totals, or Sessions) can affect how events are counted in the funnel. Each method has different rules for how users can re-enter the funnel and how events are attributed.To get a more accurate understanding of the discrepancies in your specific funnel, you may need to examine the funnel setup, filters, and conversion criteria in detail. If you're comparing funnel data to other reports in Mixpanel, keep in mind that different reports calculate data in different ways, which can lead to discrepancies.
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 document a Mixpanel plan for adding wording flags from your CMS to Mixpanel as user profile properties, I would suggest following these steps based on Mixpanel's best practices: 1. Define the User Properties: First, clearly define which wording flags from your CMS you want to add as user profile properties in Mixpanel. Document these in your tracking plan, using the [blank Tracking Plan template](https://docs.google.com/spreadsheets/d/1ZdOZ6TMtRPxy7qRxiLsvH9HWcHJM6nZydWKoThRxFKc/edit#gid=1641519238) provided by Mixpanel. 2. Naming Convention: Follow Mixpanel's recommended naming conventions for user properties. As mentioned in the [Tracking Plan Methodology](https://docs.mixpanel.com/guides/plan/tracking-strategy#tracking-plan-methodology): - Use a consistent snake_case naming convention - Avoid abbreviations or specific jargon - Don't use prefixes like 'mp_' or '$' sign 3. Data Types and Values: Specify the data types for each wording flag property. Ensure that the values are consistent. For example, if a flag is boolean, use true/false consistently rather than mixing with yes/no or 1/0. 4. Implementation Method: Document how you plan to implement the update of these properties. You'll likely use the people.set() method in your chosen Mixpanel SDK. For example, in JavaScript, it might look like this:
javascript
mixpanel.people.set({
"cms_flag_feature_x": true,
"cms_flag_language_preference": "en_US"
});
5. Update Frequency: Specify how often these properties should be updated. For example, will they be set only once when a user first interacts with your system, or will they be updated regularly based on changes in the CMS? 6. Identity Management: Ensure that you have a clear plan for identifying users. As noted in the [User Profiles FAQ](https://docs.mixpanel.com/docs/data-structure/user-profiles#faq): "If you track User Profiles after you track events, they'll still join retroactively with all past events. This means that you don't need to worry about tracking Events and User Profiles in lockstep with each other. As long as they have the same values for Distinct ID, they'll join with each other." 7. Property Limits: Be aware of Mixpanel's limits on user properties. From the [User Profiles FAQ](https://docs.mixpanel.com/docs/data-structure/user-profiles#faq): "Each User Profile can contain up to 2000 properties. User property names can be at most 255 characters in length (longer names are truncated)." 8. Data Quality Assurance: Include a plan for testing and validating that the CMS flags are being correctly set as user properties in Mixpanel. 9. Documentation Updates: As mentioned in the [Tracking Plan Methodology](https://docs.mixpanel.com/guides/plan/tracking-strategy#tracking-plan-methodology): "Keep your tracking plan as a living and shared document that is continuously updated with any implementation or product changes."
By following these steps and documenting them clearly in your tracking plan, you'll ensure a systematic approach to adding your CMS wording flags as user profile properties in Mixpanel, maintaining data quality and consistency.
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.