# Tracked data Below are described all the data that are tracked by the MBAudience SDK and that you will be able to use from the [MBurger](https://mburger.cloud) dashboard. Most of the data are tracked automatically, for a couples a little setup by the app is neccessary. * **app\_version**: The current version of the app. * **locale**: The locale of the phone, the value returned by `Locale.preferredLanguages.first`. * **sessions**: An incremental number indicating the number of time the user opens the app, this number is incremented at each startup. * **sessions\_time**: The total time the user has been on the app, this time is paused when the app goes in background (using `didEnterBackgroundNotification`) .and it's resumed when the app re-become active (using `willEnterForegroundNotification`). * **last\_session**: The start date of the last session. * **push\_enabled**: If push notifications are enabled or not; to determine this value the framework uses this function: `UNUserNotificationCenter.current().getNotificationSettings`. * **location\_enabled**: If user has given permissions to use location data or not; this is true if `CLLocationManager.authorizationStatus()` is `authorizedAlways` or `authorizedWhenInUse`. * **mobile\_user\_id**: The user id of the user curently logged in MBurger * **custom\_id**: A custom id that can be used to filter further. * **tags**: An array of tags * **latitude, longitude**: The latitude and longitude of the last place visited by this device --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ep.mburger.cloud/ios-docs/audience/tracked-data.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.