Flurry
237 results found
-
Pendo vs Flurry head-to-head shows Pendo has an upper hand
Aggregated event reporting (ie feature usage) (Pendo better); Granular individual (client, employee) app usage reporting (Pendo better); Funnels (Pendo better) ; Ease of use (Pendo better); In app messaging (Pendo better)
5th ranked -
Flurry documentation is not as good as Fabric's. Not easy to find info about custom events
Found documentation for Fabric easier to use since it combines both official and community based on Stackoverflow etc; he attributed this to Fabric’s larger user base; for Flurry to find info about custom events he had to use the official site only and use the topic links in left hand margin to find what he wanted; he didn’t see a search feature
5th ranked -
It would be nice for Flurry to support a Web SDK.
Mixpanel is more useful across the org as it provides both web and mobile data. Having a web SDK in Flurry would be useful.
5th ranked -
For Flurry to move upstream they need to add better behavioral analysis.
Contrasted Flurry as a tool for “product insight” vs Mixpanel for “marketing insight” when “going from launching to growth hacking”
5th ranked -
Difficult to configure Push during Flurry implementation
Had problems configuring push during Flurry implementation experience; works fine during test but not on live app
5th ranked -
Continue showing event data on Flurry's mobile app
Flurry's mobile app shows event data which is very valuable. Facebook's analytics app only shows analytics dashboard data and not event data.
5th ranked -
Flurry's real-time data is delayed
Fabric's analytics dashboards and event data showed up in real-time. Flurry's data was always delayed, specifically event data (12-24 hours). This needs significant improvement.
5th ranked -
Fabric dashboard UI was amazing
Flurry should work towards making their UI even better. It is better than Firebase overall but not as good as Fabric was.
5th ranked -
Flurry documentation is good and features match up to Mixpanel.
Decided to switch to Flurry after visiting the Flurry site and reading the docs; “Flurry has all the features of Mixpanel and it’s free; the SDK is super simple to integrate”; “all I really care about is events”
5th ranked -
Price is an important factor in decsion making for analytics tools
Looking for a Firebase replacement and Flurry & Mixpanel were identified as alternatives. Mixpanel was eliminated from his short list because it’s “too expensive” costing “several hundred $ per month”.
5th ranked -
Need to anonymize user IP to comply with GDPR
Flurry does not support the ability to anonymize user IP to comply with GDPR. This a a feature that Firebase allows and was the main reason to decide against Flurry.
5th ranked -
Data speed for Flurry is a real limitation
Flurry consistently showed reporting delays; known events were slow to appear in Flurry
5th ranked -
Flurry integration is simple
Flurry’s integration was simple; “it’s just one line”
5th ranked -
Better push notification reporting/analysis
Push reporting was a weakness in Airship and he’s found same problem now with Firebase; “delivery of push notifications is a black box”; he has to query and report from their own database on sent and open numbers (Android accurate but not iOS); workaround has been building their own “push received” event
5th ranked -
Deliver push notifications in recipient's local time zone
Another weakness of Firebase has been scheduling delivery in recipient’s local time zone
5th ranked -
Push API to automate push triggering
Push API to automate push triggering is not supported by Flurry. See Firebase which supports it.
5th ranked -
Track & report revenue data better
track and report revenue events (Countly best because it had been easy for CTO to take a chart and put into his Board report; Flurry worst - revenue events tracked just fine but revenue report did not sum iOS and Android into one total)
5th ranked -
A/B Testing capabilities
A/B testing (a new requirement from product team) (Firebase best because of familiarity with it; Countly worst because doesn’t offer)
5th ranked -
Flurry needs to support Push notifications better. Either with documentation or onboarding marketing teams better.
marketing team able to create targeted (push) campaigns (Countly best because they help Marketing team with everything; Flurry worst because Braden didn’t want to teach Marketing; no hand holding available for marketing team)
5th ranked -
Need to make integration simple
quick and easy integration (Firebase best because Braden and team have already been using Firebase’s push notifications component; Clevertap worst because of React Native issues)
5th ranked
- Don't see your idea?