Understanding 'Not Set' Category in Kapa.ai Product Details
kapa.ai when I want to breakdown the source of product detail viewed, i see a category called ‘not set’. Why is it? What does it mean?
kapa.ai when I want to breakdown the source of product detail viewed, i see a category called ‘not set’. Why is it? What does it mean?
When you see a category called “not set” while breaking down the source of product detail viewed in Mixpanel, it means that the property you are using for the breakdown (such as “source” or a UTM parameter) was not present on some of the events being analyzed.Mixpanel displays “not set” (which corresponds to “undefined” or “null” in the raw data) when: - The specific property you are segmenting by is not always sent with the event. For example, if some “Product Detail Viewed” events do not include the “source” property, those events will be grouped under “not set” in your breakdown. - For UTM parameters, “not set” often indicates organic or direct traffic, where the URL did not contain UTM tags, so the property is absent from the event. - If you are segmenting by a user profile property and the user profile does not contain that property, or if the event was triggered by a user without a profile, those will also show as “not set.” - For geolocation data, “not set” can appear if the user’s IP could not be mapped to a location or was not included in the request.In summary, “not set” means the property was missing or undefined for those events. You can exclude these values from your report if you wish, using the visualization legend or by filtering for events where the property “is set” Supported Properties Data Type: Falsy Values | Traffic Attribution: Web Attribution.
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! 📚
When you filter by a source category list and then break down by source name in Mixpanel, seeing several “not set” values means that, for those particular events, the “source name” property was missing or undefined.This can happen for several reasons: - The property you are breaking down by (“source name”) was not sent with the event, even though the event matched your filter on the source category list. In Mixpanel, if a property is missing from an event, it will show up as “not set” in the UI Supported Properties Data Type: Falsy Values. - For web attribution, if a user arrived without UTM parameters or the relevant source information in the URL, the UTM properties (like source name) will be absent, and those events will appear as “not set.” This often indicates organic or direct traffic Traffic Attribution: Web Attribution. - If you are using a user profile property for the breakdown and the user profile does not have that property set, or if the event was triggered by a user without a profile, it will also show as “not set.”In summary, “not set” sources are events where the “source name” property was not available at the time of tracking. These could be from users who arrived organically, directly, or from sources where the property was not captured or sent with the event.
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 a user chooses "ask app not to track" (i.e., opts out of tracking), Mixpanel's SDKs will stop sending any data for that user. This means that no events—including those with source properties—will be sent to Mixpanel at all for that user. As a result, their activity will not appear in your reports, and you will not see their events as "not set" or otherwise; their data is simply not tracked or available in Mixpanel after opt-out.The "not set" category appears only for events that are tracked but are missing the specific property you are breaking down by. It does not represent users who have opted out of tracking, because for those users, no events are sent to Mixpanel in the first place Protecting User Data: Opting users out of tracking and anonymizing data.In summary: Users who have chosen "ask app not to track" do not contribute to the "not set" category, because their events are not tracked at all. "Not set" only applies to events that are tracked but missing the relevant property.
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.