How event tracking works in RadiumOne Mobile Analytics

„Within Mobile Analytics everything comes down to tracking events. 

„Each event in turn has a set of attributes that add dimensions and depth and which we can use to analyze them after the fact.

„Some clients will have very strong ideas of what events they should be tracking and what attributes are important for each.  Others will require more hand holding.

„Anything that happens in the app code can be tracked as an event, not just user actions.  So, for example, in a dating app a user might tap 'Like" on another users profile and that's obviously trackable as an action, but when the system recognizes that both users have clicked "Like" and sends them both notifications, sending the "Like" notification can also be tracked as an action.

„If you are unsure, please bring in a Solution Engineer who can talk through the use cases with them.

Set of available events includes:

1) Automatic Events

The R1 Mobile Analytics SDK will automatically capture some generic events in order to get the most meaningful data on how users interact with your application. These events are triggered when the state of the application is changed, and therefore do not require any additional code to work out of the box:

Launch - emitted when the app starts

First Launch - emitted when the app starts for the first time

First Launch After Update - emitted when the app starts for the first time after a version upgrade

Application Opened - emitted when your app is opened after a message is sent.

Session Start - emitted when a new session starts

Session End - emitted when a session ends; includes a Session Length attribute with the session length in seconds

2) Standard Events

Standard Events cover all the main user flows (login, register, share, purchase...) in a standardized format for optimized reporting on the portal, providing a great foundation for your analytics strategy. They unlock great insights, particularly with respect to user lifetime value.

Login - Tracks a user login within the app

Registration - Records a user registration within the app

Facebook connect - Allows access to Facebook services

Twitter connect - Allows access to Twitter services

User Info - This event enables you to send user profiles to the backend.

Upgrade - Tracks an application version upgrade

Trial Upgrade - Tracks an application upgrade from a trial version to a full version

Screen View - Basically, a page view, it provides info about that screen

Transaction - A purchase

TransactionItem - Deprecated, use the Transaction event instead.

Delete Cart

Add To Cart

Delete From Cart

3) Custom Events

Custom events enable you to create and track specific events that are more closely aligned with your app. If planned and structured correctly, custom events can be strong indicators of user intent and behavior. Some examples include pressing the “like” button, playing a song, changing the screen mode from portrait to landscape, and zooming in or out of an image. These are all actions by the user that could be tracked with events.

Custom events can also be used to track things that happen in an app that do not involve direct user input.  For instance a dating app could fire an event when the server matches two users based on interest and it sends them both notifications, even though neither end user has taken an action yet.

4) In-App Webview Events

By setting up in-app webview events, you can track events that begin inside your native application but are completed in the embedded browser. To do so, you will have to embed some JavaScript in the page that you will want to fire the event, and you need to properly trigger the webview in your application.  These can include events in any of the three categories above.  

Read More:

Implement event tracking in iOS
Implement event tracking in Android

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk