Book Image

Getting Started with Flurry Analytics

By : Bhanu Birani
Book Image

Getting Started with Flurry Analytics

By: Bhanu Birani

Overview of this book

Analytics help you to understand the way your users are interacting with your mobile application. Flurry provides you with a strong analytics tool to keep track of your application and to analyze your application data without much hassle. It provides an SDK for almost all platforms to gather data from all platforms of mobile and web applications. The enormous amount of data Flurry handles directly translates into unique, powerful insights into your applications.Getting Started with Flurry Analytics is a practical, hands-on guide to instantly getting started with Flurry analytics using step-by-step exercises. You will take advantage of the real power of Flurry analytics and provides you with an example-based learning approach to help you master it quickly and efficiently.This book starts by discussing how to set up and integrate Flurry analytics and ends by making you aware of how to track your application using Parse. You will also learn about tracking your application data using Flurry analytics to strengthen your strategies and to improve the application monetization process. You will also learn about configuration and implementation of Flurry analytics and how to make the application track all the necessary details to empower management decisions.
Table of Contents (12 chapters)

Crash Analytics


Last but not the least, crash analysis can be done by the Errors item in the Technical menu item on the side bar in any application page. It gives you a graphical representation of the total errors over time, average errors per session, a detailed view, and exception log. It makes the life of a technical team very easy by helping track mishaps in the application.

The following are the advantages of Crash Analytics in Flurry:

  • We can prioritize the errors and crashes that have been tracked. We can do this using the same SDK

  • We can receive an e-mail notification of the crash so that the implementers are notified of the application crash before it's too late

  • We can get full stack traces of errors with symbolication

  • We can find errors listed by their name

We will be learning about Crash Analytics in detail in Chapter 4, Technical Analytics.