This page describes how to use the AMPLIFY Appcelerator Services Analytics for native iOS applications, built with Objective-C and the iOS APIs.
Appcelerator Analytics collects real-time data about your application's usage which can then be viewed in the Analytics dashboard. By default, the Analytics dashboard provides information about app installs, number of sessions, and average app session length (organized by app name, platform, and geography). Your app can also utilize custom analytic events and event funnels.
For platform-specific details about how analytics captured, see Analytics Architecture.
For information about viewing analytics data, see Managing Client Applications.
Analytics refers to data about how your application has been used, as well as information about how users interact with your application. Analytics data is transmitted in the form of events.
Events are operational milestones in the application. Some events are generated automatically, such as those that mark an installation, or the beginning and end of a session. Others may be custom events, which have a meaning specific to an application, such as tapping a specific button or opening a certain window.
A feature event represents an action a user could take in an application, such as 'liking an item' or launching a video'. Applications use the Titanium or APSAnalytics API to create custom events.
Event funnels let you define custom, ordered event sequences that let you track a specific user process, such as finding a product and making a purchase.
The Analytics dashboard organizes, analyzes, and presents analytics data captured for your applications. You also use the Analytics dashboard to create and view event funnels.
To integrate the Performance service with a new or existing iOS application:
- Go to the Dashboard and create a new native iOS application.
- Download the Services SDK and get your Analytics application key.
- Unpack the
- Drag the
Appcelerator.frameworkfolder into your Xcode project's root folder if you are using Xcode 6 and above, or the
Frameworksfolder if you are using Xcode 5 or below.
- Select Copy items into destination… and click Finish.
- Select your project in the Project Navigator and click the Build Phases tab.
- Expand the Link Binary With Libraries section and add the
- Click the Build Settings tab, then click the All button in the top-left corner of the tab.
- Expand the Linking section and add
-ObjCto Other Linker Flags.
In your application delegate implementation file, import
In the application delegate's
application:didFinishLaunchingWithOptionsmethod, enable the service by calling the APSServiceManager's
The iOS application can now send user session events and make additional method calls using the
APSAnalytics class .
Advanced Initialization Options
By default, after the application has been back grounded for 30 seconds, the Analytics service ends the current user session and starts a new one when the application enters the foreground again. To adjust the timeout, use the
Creating Custom Events
You use the
method to generate a feature event that captures a specific application or user activity. A feature event should represent an action, such as launching a video, or 'new item', 'launch video', and so forth. The name you assign to a feature event should incorporate the application state into the event name, rather than long descriptive names. The following naming convention is suggested, where group.event refers to the parent event:
Feature event names should be as generic as possible. For instance, if you want to track when users select a certain menu option, use a name like "user.menu.selection", not "joeuser.menu.selection". The first option is better because it groups all the same types of an event into a single metric that's easy to view on Dashboard. The person analyzing the data only has to look at a single number to get an overview of how many users have selected that menu option. The second might be fine for very small user bases, but if you have more than 100 users it means that the person analyzing the data would have to look through 100 different event names to be able to generate any useful data.
For example, to track a user's menu selection you might use the following code, where the 10 digit number uniquely identifies the selection in your code:
You should avoid using long, descriptive event names, as shown below:
to send real-time geographic data to the Analytics service. Pass the method a CLLocation object containing the location data. For example, you can use
delegate method to send geo-events when the device receives new location data.