Cisco CMX vs. Flurry Analytics

I would encourage a colleague to use Flurry Analytics. Incorporating Flurry Analytics in an app is a simple and straightforward task, and will take the average app developer less than 15 minutes to understand and apply. This amount of time is nothing in the grand scheme of the development of the app, and the return on time invested to incorporate it is great. New tracking features can be added at any time.

• Flurry can track in-depth metrics across your app. This allows us to see every type of interaction our app users are performing.

• There is no option to choose a timezone which will allow me to compare their data over other systems in other time zones.
• Could be nice to have more reporting screening options.

Incentivized

Good user acquisition tracking
Sdk integration is super easy for both iOS and Android
Need it
Need to support more customized dashboards / reporting (example - set up a dashboard specifically to see users engaging with a new feature recently launched)

For my uses, Flurry is free which makes it way more attractive than the other platforms even on a very big number of monthly events. It also have set reports which are exactly the reports that a marketing person needs without any need of spending a developer time to create them for you, or holding an in-house BI person that works on creating reports.

Incentivized

• Tracking the number of times a user taps a help button can help to improve the app design. Perhaps the app is not as intuitive as first thought, and improvements based upon where in the help feature a user taps will lead to improvements in the app design to make it more intuitive.
• Tracking the number of times certain app features are used, or the amount of time spent within a given activity in the app can help to streamline an app - improve upon features that are used more frequently while eliminating less popular activities.
• Tracking time spent within an app can give an idea as to how popular the app is.