Skip to content

Flurry



This forum is for you to make product suggestions and provide thoughtful feedback. We’re always trying to improve our products and we can use the most popular feedback to make a positive change.

This forum is not monitored for any support-related issues. If you need assistance of any kind, please send an email to support@flurry.com.

Tell us how we can improve your Flurry experience. The more specific your feedback, the more useful for us.

If you would like to remove your posts, comments, votes, and/or profile from the Flurry product feedback forum, sign in and follow these steps.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

288 results found

  1. Data speed for Flurry is a real limitation

    Flurry consistently showed reporting delays; known events were slow to appear in Flurry

    5th ranked

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Flurry integration is simple

    Flurry’s integration was simple; “it’s just one line”

    5th ranked

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Push API to automate push triggering

    Push API to automate push triggering is not supported by Flurry. See Firebase which supports it.

    5th ranked

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Providing user's path preceding the crash

    Flurry does not provide details about a user's path preceding a crash.

    5th ranked

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Flurry does not support multi-tenancy

    Intellective is a “development studio” that helps enterprises build web and mobile apps on the ServiceNow Now Platform. On Intellective’s setup, multiple clients share the same app, and the different clients point it to their own servers. This creates the need for an analytics tool that supports multi-tenancy. Previously used Firebase, but Firebase does not support multi-tenancy which a “must have” criterion. Flurry also does not support multi-tenancy whereas Amplitude & Mixpanel both do.

    5th ranked

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Add game specific Event types. See Game Analytics.

    Event types - Game Analytics has event types Manifesto likes to use such as business event (purchases) and player’s resources; can this be replicated in Flurry?

    5th ranked

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. There are advance analytics capabilities in DeltaDNA and we are willing to pay for them.

    Once a game reaches an informal threshold of revenue and usage, they will add DeltaDNA which is a paid tool to support more analysis

    5th ranked

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Better funnel analysis. Look at Game Analytics

    From 2011 to 2015/16, Manifesto used Flurry exclusively; “Flurry was the standard; best tool to use if you needed to share data with a partner”. Then they had trouble with funnel analysis and found that funnels in Game Analytics were better than Flurry’s, so they began using both Flurry and Game Analytics, and then by 2017 they used just Game Analytics.

    5th ranked

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. A custom event with multiple parameters is recorded by Flurry as multiple events

    Custom events not integrated - an event with 3 parameters is recorded by Flurry as 3 separate events which requires extra processing by the dev team

    5th ranked

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  Bug  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Old events that have been deleted continue to show up in Explorer

    Old events not deleted in the backend (Flurry queries returned data for custom events that had been deleted on the front end)

    5th ranked

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  Bug  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Real-time data in Flurry is delayed and slow.

    Real-time data (Firebase better because there is just a 5-10 minute delay; Flurry data is delayed 8-10 hours

    5th ranked

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Explorer & User Segments limitations

    Liveperson (LP) may switch to another tool because Flurry doesn’t support their need to provide Sales with a report of registered users who haven’t logged into the app. LP sells their app and will lose revenue from unused accounts. Explorer & User Segments are limited.

    5th ranked

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Xamarin SDK integration

    Liveperson's apps are developed using Xamarin.

    5th ranked

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Adjust attribution integration

    Wants attribution integration with Adjust, they do not use AppsFlyer.

    5th ranked

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base