Which common mobile events can Mixpanel collect on my behalf automatically

Mixpanel’s mobile SDKs can automatically track a selection of common mobile events pertinent to your app so you can immediately start tracking data after implementation!

The events we can automatically track are: “First App Open”, “App Updated”, “App Crashed”, “App Session” and “In App Purchase” (iOS only) and are outlined in more detail below.

If you have already implemented Mixpanel on your mobile app and you would like to enable the tracking of these events, you can navigate to your Project Settings → Autotrack and enable “Automatically collect common mobile events.” This will start collecting all default event data and their respective properties going forward. It's important to ensure you're using the latest release of our mobile SDKs (Obj-C > 3.1.5, Android > 5.1.0, Swift > 2.1.6).

If you have not yet implemented Mixpanel on your mobile app, you will have the option to enable the automatic tracking of common mobile events as a part of the initial implementation flow.

Note: Enabling tracking of common mobile events will track all following events. At this time, there is no way to select specific events to track from the ones listed below.

  • 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 purchases 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.

With all of these events together you’ll be poised to begin tracking core actions that occur within your app! If you’d like to explore building out the set of events that you track in your app take a look at the details on our hardcoded and codeless tracking methods.