Mixpanel’s mobile SDKs automatically track common mobile events (for iOS and Android) and two common people properties (for iOS only).
View this article to see the full list of default properties collected by Mixpanel.
- First App Open: This event tracks the first time the user opens the app if they have not opened the app previously. Mixpanel determines whether or not the user has opened the app based on archived information. If an app is uninstalled and re-installed again, the "First App Open" event will be fired. However, the event will not be fired between app updates.
App Updated: This event is fired when a given user updated his or her app from a previous version. This change is detected based on a persisted app version value. If a change is detected from a previous app version we’ll fire the “App Updated” event.
App Crashed: We fire an App Crashed event when we receive either an exception or a signal indicating the app has crashed. Along with the crash we also provide a property called “Reason” to help identify what kind of crash this was. Note: App Crashed isn’t currently supported on the Swift SDK. Also, be assured that this doesn’t interfere with current crash reporting tools.
App Session: The App Session event is fired if the user spends more than 10 seconds in the app. This event also includes a property, “Session Length,” that reflects the number of seconds the user spent in the session. If you’d like to override the minimum and/or maximum session value you can do so following the details here.
In App Purchase (IAP): This event is fired if a user conducts an in-app purchase through your app. We also provide three properties along with this event; Product Name, Product Quantity, and Product Price. Note: At this time, the In App Purchase event is not available on Android.
Note: "Total App Sessions" and "Total App Session Length" events are not available on Android
- Total App Sessions: The total number of "App Session" events that the user has sent.
- Total App Session Length: The total number of seconds that a user has spent using the app. This is calculated by adding the "Duration" property attached to the "App Session" event.
You will experience duplicate tracking if you programmatically track any of the automatically tracked common mobile events above. To prevent this, either remove the programmatic tracking or disable common mobile events.
Disable Common Mobile Events