What is (not set) in mixpanel

Hi Ani A., 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> 👋

In Mixpanel, "(not set)" refers to events where a property value has not been set during tracking or ingestion. This happens when you track an event but don't associate a specific value with a particular property.For example, if you add a new video called "MixFun" to your application, but during tracking you forget to send the name of this video, the event count is still tracked, but it's associated with a property value of "(not set)" instead of "MixFun".It's important to note that "(not set)" is different from "(remaining values)" in custom buckets: - "(not set)" specifically refers to property values that haven't been associated with any value - "(remaining values)" refers to values that are set but don't fall into any of your defined segmentsIn numeric properties, there's also a distinction between "(not set)" and "(non-numeric values)": - "(not set)" means no value was provided - "(non-numeric values)" refers to values that were sent but aren't numeric (like "a" or "b" for a property that should be numeric)When using Custom Buckets in Mixpanel, "(not set)" is automatically computed and will always show up in the UI without you having to select it as a segment.Mixpanel Custom Buckets FAQ

ℹ️ 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 working with numeric values in Mixpanel, "(not set)" represents instances where the property you're analyzing wasn't included with the event at all, rather than a specific range of numeric values.For numeric properties specifically, Mixpanel distinguishes between two different scenarios: 1. "(not set)" - This appears when events don't have the property assigned at all during tracking/ingestion 2. "(non-numeric values)" - This appears when values were sent but in a non-numeric format (like "a" or "b" for what should be a numeric property)When you're bucketing numeric data in Mixpanel using Custom Buckets, the system automatically handles "(not set)" values separately from your defined numeric ranges. These "(not set)" values will appear as their own category in your visualization, not as part of any numeric range you define.If you're seeing a specific numeric range showing as "(not set)", this is likely not related to the actual bucketing but rather indicates that those events simply don't have that property tracked at all.For numeric bucketing, Mixpanel offers two approaches: - Even Bucketing: Creates equal-sized buckets across a range - Varied Bucketing: Lets you define specific breakpoints for your bucketsIn both cases, "(not set)" will remain separate from your numeric buckets.Mixpanel Custom Buckets FAQ Mixpanel Falsy Values Documentation

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.