Location-Based Analytics
Your application will be distributed worldwide via the iTunes App Store. Learning where your users are running your app can be of key importance, so the Medialets Analytics SDK has this functionality built in. The first time your application runs on a device, the iPhone OS location manager prompts them via a pop-up window for permission to use their current location. If the user agrees, this popup will only appear once—the first time a user runs your application on their device. If you would rather not have your users see this pop-up, a method exists to disable location-based analytics for your application. See: API Reference.
| Note: As of February 2010, Apple changed its location policy in its iPhone Developer Program License Agreement. Section 3.3.6 now states that an app using "Core Location information must provide user benefit and cannot solely be enabled to allow mobile advertisers to deliver targeted advertisements based on user's location". Prior to enabling location-based analytics, ensure that your application is compliant with iPhone's Developer Program License Agreement; failure to do so may delay your application's approval. |
Custom Events
The Medialets Analytics SDK also allows you to record instances of virtually any event that occurs in your application using Custom Events. Whenever the desired event occurs in your application, the event instance is stored for eventual transmission to the Medialets Muse™ server. Additionally, a dictionary of other data associated with the event can be included in what is sent to us. The Medialets Analytics SDK can also observe notifications and record them as Notification Events. The gathered data is available in reports on Medialets Muse™ and can be downloaded in CSV files for offline processing. See: Event Analytics.
Asynchronous Event Posting
Due to the inherent nature of mobile platforms, end users may run your application even when no network connectivity is available. Therefore, the Medialets Analytics SDK is designed to cache recorded events locally on the device in an auto-generated SQLite database. It periodically sends events to our servers in bulk when your application is running and the device can connect to the internet. The Medialets Analytics SDK will automatically remove events from the local cache only after it receives an acknowledgement of successful transmission from the Medialets Muse™ server.
Analytics Reporting
Medialets Muse™, via its Medialets App Reports, translates the event information sent from users' devices into practical reports about your application's usage. For details on using Medialets App Reports, see: Medialets App Manager and App Reports AND Medialets Ad Reports.