what is the default value when an event property does not capture any data because that functionality is not available for a user so no value can be set what is the default mixpanel property sent that allows us to know kapa.ai
When an event property is not captured (i.e., the functionality is not available for a user and no value can be set), Mixpanel does not send a default value for that property. Instead, the property is simply omitted from the event. In Mixpanel reports, this will appear as “undefined” or (not set) when you segment or break down by that property.
- Undefined: This occurs when the property is not present on the event at all. In the UI, it is shown as “(not set)”. This is the standard behavior for properties that are not applicable or not available for a given event or user. For example, if you segment by a property that is not always sent, those events without the property will be grouped under “undefined” (source).
- Null: If you explicitly set a property to null, it will also appear as “(not set)” in the UI, but as null in raw data. However, best practice is to omit the property entirely if it is not applicable (source).
Recommendation: If a property value is unavailable (e.g., null, N/A, or empty string), Mixpanel recommends that you do not send the property at all with the event or user profile. This ensures data quality and avoids confusion in reporting (source).
Summary: - If a property is not set, it is omitted from the event. - In Mixpanel reports, this will show as “undefined” or “(not set)”.
You can filter out these “undefined” or “null” values in your reports if you do not want to see them (source).
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 are asking which properties are included in the event payload when an event is sent to Mixpanel, the following applies:
Required properties that must be included in every event payload are:
- event: The name of the event.
- properties: An object containing metadata about the event, which must include:
- time: The timestamp of the event (in seconds or milliseconds since epoch).
- distinct_id: The unique identifier for the user who performed the event.
- $insert_id: A unique identifier for the event, used for deduplication.
Example event payload:
{
"event": "Signed up",
"properties": {
"time": 1618716477000,
"distinct_id": "91304156-cafc-4673-a237-623d1129c801",
"$insert_id": "29fc2962-6d9c-455d-95ad-95b84f09b9e4",
"ip": "136.24.0.114",
"Referred by": "Friend",
"URL": "[mixpanel.com/signup](http://mixpanel.com/signup)"
}
}
You can also include any additional custom properties relevant to your event. If a property is not applicable or not available for a particular event, it should simply be omitted from the payload. In Mixpanel reports, events missing a property will show as “undefined” or “(not set)” when you break down by that property. There is no default value sent for missing properties; omission is the standard approach see here, and here.
If you need to prevent certain default properties from being sent, you can use the property_blacklist configuration in the JavaScript SDK see here.
Summary:
- Required: event, properties.time, properties.distinct_id, properties.$insert_id
- Optional: Any other properties you want to track
- Omit properties that are not applicable; they will appear as “(not set)” in reports.
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.