Using the Localytics Dashboard

Events and Screen Flows

• Events
• Event Attributes
• Picking Events to Track
• Screen Flows

Events

Localytics allows app developers to tag certain Events to track within the app. Events are interesting things which the user does within an application. These may be things such as a user changing their options, logging in to a service, or beating a level in a game. One example seen here is the “Trip completed” event for the App GPS Walk and Run Tracker. The events reports gives a summary of all the events tagged in an app. Clicking on any of the events on the charts or in the chart data will bring you to a report for that specific event, you are also able to switch between events from a drop down located above the chart.

Event Attributes

Along with allowing app developers to track certain app-specific items of interest, Localytics also allows app developers to record contextual data specific to that event. In our example below for the GPS app, an Event Attribute has been attached to the “Trip Completed” Event that recorded the Max speed seen during the trip. The results are then displayed in a proportional pie-chart.

You can view the demo to see other advertising and GPS reliability Event Attributes tracked for this app. You can see more about Event Attributes on the Localytics blog.

Suggested Uses
Events and Event Attributes can be among the most powerful tools at your disposal to get a good idea of how people are using your apps. See below:

Picking the Right Events

• Because every app is different, there is no single set of guidelines for tagging the right events. Instead, you have to think about how your app will be used and what is most useful to you. The best way to tag an application is to start with the business or engineering questions which need to be answered and then figure out what events can provide these answers. Here are some questions to consider to get started:


• What is the purpose of your app?
• What do I need to know about my user’s experiences?
• Which events represent the best feedback from users?
• Which events help track conversions, or in-app purchases?
• What features should we invest in?

For an example, consider the GPS Walk and Run Tracker demo application. The application is targeted at both walkers and runners but it may be valuable to know which audience the application is actually reaching. To find this out, an attribute was added to the “trip completed” event which records the max speed reached during the trip. This data shows that the application is used more frequently by walkers than runners.

Screen Flows

During the integration process it is possible to tag each screen presented to the user with a descriptive name. This data can be viewed as a flow diagram highlighting common users flows, frequently visited screens and areas where most users are lost. Tagging screens also allow them to be used in creating funnels.

Suggested Uses
Understanding user flow is critical to providing the best user experience. This data highlights which way users find specific features and which features cause users to leave the application. It can also be used to help developers focus on high-traffic areas or the steps that seem to lose the most users.