Creating a Conversion Funnel with Events from Multiple Users and Unique IDs
How can i create a conversion funnel with events that are made by two different users, holding a unique ID constant?
How can i create a conversion funnel with events that are made by two different users, holding a unique ID constant?
To create a conversion funnel with events made by two different users while holding a unique ID constant, you can use Mixpanel's "Hold Property Constant" feature in funnels. This feature allows you to track conversions across multiple users who share a common property value, such as a unique ID.Here's how you can set this up: 1. Create your funnel in Mixpanel's Funnels report. 2. In the "Advanced" section of the Conversion Criteria, click on "Holding property constant". 3. Select the property that represents your unique ID (e.g., a Salesforce Account ID or any other shared identifier).By holding this property constant, Mixpanel will ensure that all steps in the funnel are performed with the same property value, even if the events are triggered by different users.This approach is particularly useful for B2B scenarios or when tracking account-level conversions. As mentioned in the Mixpanel blog: "Tracking events with SFDC ID as the distinct ID along with the user ID as a property on the events let us do funnel/retention analysis on an account level but still gave us the ability to filter down to a particular user if required. For example, a typical sales funnel involves multiple users from the customer's organization involved in the process and hence the distinct ID cannot be tied to a single user."Remember that you can hold up to 3 properties constant simultaneously, which allows for more complex analyses if needed.For more detailed information on using the "Hold Property Constant" feature in funnels, you can refer to the Mixpanel Funnels documentation.
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! 📚
I apologize that the previous suggestion didn't work as expected. Let's explore some other settings in Mixpanel funnels that you could try adjusting to achieve your goal: 1. Conversion Criteria: - Try changing the counting method between "Uniques", "Totals", or "Sessions". This can affect how conversions are calculated. - Adjust the conversion window to allow more or less time for users to complete the funnel steps. Mixpanel Funnels documentation provides more details on these settings.2. Property Attribution: - Experiment with "First Step Defined" or "Last Step Defined" property attribution. This determines which step's property value is used for the entire funnel. You can find more information about this in the Property Attribution section of the Mixpanel documentation.3. Exclusion Steps: - Consider adding exclusion steps to filter out users who perform certain actions between your main funnel steps.4. View as Flow: - Try using the "View as Flow" feature to get a more detailed view of user paths and potential drop-off points. The Mixpanel Funnels documentation explains this feature in more detail.5. Property Sum: - If you're tracking revenue or another numeric value, you could try using the Property Sum feature to visualize how a specific value changes through the funnel steps. More information on this can be found in the Property Sum section of the Mixpanel documentation.If you're still experiencing issues after trying these adjustments, it might be helpful to double-check your event tracking implementation and ensure that the unique ID you're trying to hold constant is being correctly passed with each event.Additionally, you might want to consider reaching out to Mixpanel's support team for more personalized assistance, as they can look into your specific setup and data.
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 reach out to Mixpanel's support team for more personalized assistance, you have several options: 1. In-app Support: If you're logged into Mixpanel, you can click on "Contact Support" in the Help Menu. This is the most direct way to get support while using the platform.2. Web Support Form: If you're not logged in, you can access the support form by going to mixpanel.com/get-support.3. Email Support: For specific migration-related questions or assistance, you can email the Customer Success team at success@mixpanel.com.The response time and level of support you receive may vary depending on your Mixpanel plan. According to the Mixpanel Response Times documentation, support offerings and first response times are as follows: - Premium Plus: 1 hour for critical issues, 4 hours for normal issues (24/7) - Premium Support: 4 hours for critical issues, 8 hours for normal issues (24/5) - Enterprise: 8 hours for critical issues, 24 hours for normal issues (24/5) - Growth: 24 hours for critical issues, 48 hours for normal issues (24/5) - Free: 48 hours for critical issues (24/5)For immediate community-based support, you can also join the Mixpanel Community Slack, where you can ask questions and get help from other experienced Mixpanel users.Remember, if you're experiencing a persistent, widespread issue or cannot access your account, your ticket will be prioritized as Critical. For general product questions or feature requests, your ticket will be categorized as Normal priority.
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, there are important considerations for developers when configuring a 'held constant' property to create a funnel between events from different users. Here are the key points to keep in mind: 1. Consistent Property Tracking: Developers need to ensure that the property being held constant is consistently tracked across all relevant events, regardless of which user triggers them. This property should be present and have the same value for all steps in the funnel.2. Property Attribution: According to the Mixpanel Funnels documentation, developers should be aware of how property attribution works. Mixpanel offers two options: - First Step Defined: The property value from the first time it's defined in the funnel is used for all steps. - Last Step Defined: The last defined property value in the funnel is used for all steps. Developers should choose the appropriate attribution method based on their use case.3. Property Naming and Type: As mentioned in the Mixpanel Tracking Strategy guide, it's important to: - Use consistent naming conventions (preferably snake_case) - Avoid abbreviations or specific jargon - Use appropriate property data types - Ensure consistent property values (e.g., "Premium" vs "premium" are considered different)4. Avoid Null or Empty Values: The same guide suggests that if certain property values are essentially considered unavailable (e.g., null, N/A, or empty string), the property should not be sent with the event at all.5. Identity Management: Developers should understand how Mixpanel handles identity management. As stated in the Identity Management Overview, Mixpanel uses the Distinct ID to identify users. When creating a funnel between different users' events, ensure that the held constant property is correctly associated with the relevant Distinct IDs.6. Testing and Validation: It's crucial to thoroughly test the implementation to ensure that the held constant property is being correctly tracked and attributed across different users' events.By keeping these points in mind, developers can help ensure that the 'held constant' property is correctly configured and works effectively to create a funnel between events from different users.
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.
kapa.ai in group analytics, does a group ID need to be a constant that the user consistently belongs to, or can it fluctuate / can the user have many at once? i’m just wondering as in our case users will have multiple projects over their lifetime rather than belonging to a more fixed group like a company or account
Let me check the knowledge base for you again. One moment! 📚
Based on the knowledge sources provided, I can answer your question about group analytics in Mixpanel.In Mixpanel's Group Analytics, a user can indeed belong to multiple groups simultaneously, and these group associations can change over time. This flexibility allows for scenarios like yours, where users have multiple projects over their lifetime rather than belonging to a fixed group.Here are some key points to consider: 1. Multiple Group Associations:
Mixpanel's documentation states that "An event can be attributed to multiple groups by passing in the group_key value as a list of multiple group_id values." This means users can be associated with multiple projects at once.2. Changing Group Associations:
The group associations are not required to be constant. You can update a user's group associations as they change projects.3. Setting Multiple Groups:
Most Mixpanel SDKs provide methods to set multiple groups. For example, in JavaScript:
mixpanel.setGroup('company', 'mixpanel');
// add "mp-us" as an additional company group
mixpanel.addGroup('company', 'mp-us');
```LBKS [Source](https://docs.mixpanel.com/docs/tracking-methods/sdks/javascript#group-analytics)LBKS4. Tracking Events with Multiple Groups:
When tracking events, you can include multiple group IDs. For example:
```LBKS mixpanel.track('some_event', {
company: ['mixpanel', 'mp-us']
});
```LBKSLBKS5. User Profiles:
You can also add group identifiers to user profiles. This allows you to maintain a record of all projects a user has been associated with over time.LBKS
```LBKS mixpanel.people.set({
"projects": ["project1", "project2", "project3"]
});
```LBKS [Source](https://docs.mixpanel.com/docs/tracking-methods/sdks/javascript#group-analytics)LBKSIn your case, where users have multiple projects over their lifetime, you could use a group key like "project" and associate users with multiple project IDs. You can update these associations as users join or leave projects, and track events with the relevant project IDs.LBKSThis approach allows you to analyze user behavior across different projects, see how users interact with multiple projects, and track project-specific metrics while still maintaining the flexibility to account for changing project associations over time.
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.