Breakdown by property that has multiple values separated by coma
Breakdown by property that has multiple values separated by coma
Breakdown by property that has multiple values separated by coma
Hi Juan C., 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
In Mixpanel, if you want to break down by a property that has multiple values separated by commas, you should use a List property type rather than a String property with comma-separated values.Mixpanel's List property type is specifically designed for handling multiple values and provides better analysis capabilities than parsing comma-separated strings. A List property is represented as a JSON array (e.g., ["Folk", "Alternative"] or [1, 5, 10.0]).When you use a List property in Mixpanel: 1. Each value in the list is evaluated individually during breakdowns
2. You can filter using "Any" or "All" operators to match specific values within the list
3. You can perform more complex analyses like breaking down by lookup properties joined to list itemsFor example, if you have a list property called "List of ProductIDs" with values like ["P1", "P2", "P4"], when you break down by this property, Mixpanel will count each product ID separately in your analysis results.Here's how a breakdown by list property works:
- When breaking down, each item in the list is evaluated individually
- If an item appears in multiple events, it will be counted for each occurrence
- You can also break down by lookup properties joined to list items for more advanced analysisMixpanel Documentation provides detailed examples of how list properties behave in breakdowns and filters.If you're currently using comma-separated strings and want to switch to lists, you'll need to modify your implementation to send the data as a proper JSON array instead of a comma-separated string.
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! đ
If you're seeing "(not set)" when breaking down by a list property in Mixpanel, this indicates that some events in your analysis don't have that list property defined or the property value is null.
Why You're Seeing "(not set)"
In Mixpanel, "(not set)" appears in reports when: 1. The specific property you're breaking down by isn't sent with some events in your analysis
2. The property value was explicitly set as null
3. The property wasn't defined for those particular eventsAs the documentation explains: > "Undefined values are seen when one or more of the events being measured in a query do not contain the property used for breakdown... Undefined values are parsed as (not set) in the UI." Mixpanel Documentation
How to Address This Issue
Here are some steps you can take: 1. Verify implementation: Check that your list property is being properly sent with all relevant events. Make sure it's formatted as a proper JSON array.2. Filter out "(not set)": You can remove "(not set)" values from your report by: - Unchecking the "undefined/null" box in the visualization legend - Adding a filter where the property "is set" - Using the exclude action directly on the "(not set)" value in your visualization3. Check for hidden properties: If you're expecting the property to be set but still seeing "(not set)", check if the property might be hidden in Lexicon or inactive (not sent in the last 30 days) as mentioned in the Debugging documentation.4. Ensure consistent implementation: Make sure you're consistently sending the list property with all events you want to analyze.Remember that list properties in Mixpanel have limits: Event Properties are limited to 8KB and User Profile Properties to 256KB. If you're exceeding these limits, it might cause issues with your data.If you need more specific help, you might want to check your implementation details or share more information about your specific use case.
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.