Events

Last Updated: Jan 17, 2016 10:57PM PST

This article assumes you have already instrumented events in your application code. If you still need to instrument, first read our iOS SDK Integration and Android SDK Integration.

To view your events, select the Application of interest. The events associated with that application and its versions will appear.

Under Actions, you may view the report for that event. For a full list, view the Event Reports page. Events will show up, either under Applications or Event Reports, if:
  • You have properly instrumented events with the Apsalar SDK in your application code or are sending events through the Apsalar API.
  • Users have triggered the event on an application with the Apsalar SDK.

Testing

If you are testing your events' implementation, the Event Tracking Console displays calls just a few minutes after they occur. To see what events have been registered in ApScience, go to the My Events page. This will show you a listing of all of your events grouped by your applications. 

In this example, the iOS application instrumented an event called SecondScreen as follows:

- (void)viewDidLoad
{
    [super viewDidLoad]; 
    [self configureView]; // Record that user has hit a Detail View 
    [Apsalar event:@"SecondScreen"]; // Event is called SecondScreen
    NSLog(@"Apsalar Event SecondScreen Completed."); // Log the message in the debug console
}
  • Event Revenue Attributeyou may manually enter revenue attribute values for an event. If your application has Apsalar’s iOS SDK version 5.0.0+, you do not need to track revenue by assigning it in your code for in-app purchases (see Revenue). With the latest SDK, international revenues for in-app purchases are also automatically converted in Dashboard, Trending reports, Real-Time Cohorts, and Funnel reports. Get the latest SDK here.
  • Apsalar supports multiple parameters / arguments for iOS and Android events. If you implement event arguments, track them by clicking "View Attributes". The screen shot below shows an event without attributes (top) and one with attributes (bottom). See Apsalar's iOS and Android Integration Guides for technical instructions on how to instrument event attributes.
  • Engagement Index: you may enter an engagement value (e.g. 1, 3, 10, etc.) for an event to gauge interaction value within your app. If the event is "low engagement", such as launching the app, assign a smaller numerical value. If the event is "high engagement", such as getting to the last level in a game, assign a bigger numerical value. 
  • Actions: View Report, View Attributes (if any), Assign/Change Revenue, and Assign/Change Engagement Value.

Best Practices

Events are associated with a specific application name and OS, so you should choose names that will help you identify your event.

  • If you remove an event from your application code, the event will still be registered and appear in your event list. Best practice is to not remove events once they are instrumented.
  • If you remove an event, do not include that event in any Funnel, since your application will no longer be tracking the event.

Event Name Limit

There is a limit of 400 event names per app version. If you exceed the 400 event name limit in your application, new event names for that particular app version will not register. 
 
Your events should be hard-coded within your application, never created dynamically when a user action is triggered. To keep event names to a minimum, Apsalar recommends implementing attributes for your event (e.g. purchase_one_tree, purchase_two_trees; product_id; etc.). In summary:
  • If you have dynamically generated event names, you should remove them and use attributes instead.
  • If you are over this limit, all new event names will be rejected.
  • Release a new application version with less than 400 (usable) event names if you have more than 400 event names. 
Clicking View Report will bring you to the event report where you may filter for granularity (day, week, month), time range, metric (total count, unique users, average per session, events per session, revenue, and ARPU). In the example below, the Event Name is SecondScreen and the Application Name is Apsalar (com.apsalar.myapp.Apsalar).

To learn more about event reports and event analysis, see Event Analysis.

 

support@apsalar.com
http://assets2.desk.com/
apsalarinc
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
Invalid characters found
/customer/en/portal/articles/autocomplete