New Flurry Analytics plugin now available

12 April 2016

New Flurry Analytics plugin now available


Corona SDK, News & Announcements, Plugins

flurrybannerCorona Labs is pleased to announce the availability of the new Flurry Analytics plugin. Flurry is a popular analytics tool for measuring the actions users take in your app. It can also tell you how much time people spend doing tasks and record errors that occur. Armed with this data, you can improve how your app flows and provide a better experience to your users.

If you are migrating from the previous Flurry plugin, there are a few things to be aware of. Everything is covered in our migration guide, but most importantly:

  • You need to update your build.settings file and change the plugin provider from ["CoronaProvider.analytics.flurry"] to ["plugin.flurry.analytics"].
  • For Android users, the ["plugin.google.play.services"] plugin must now be included. Previously you were required to use the Google Play Game Services plugin (["CoronaProvider.gameNetwork.google"]). Note that if you are using any ad provider plugins on Android, you may already have this additional plugin included.

Other important additions to this plugin include a required listener function for analyticsRequest events, specified as part of the flurryAnalytics.init() call. You can also enable crash analytics and set logging levels in the same function. Finally, new functions have been added to measure timed events — see flurryAnalytics.startTimedEvent() and flurryAnalytics.endTimedEvent().

If you are new to Flurry, you will need to sign up here and get an API key. Once you’re registered, you can use the same site to see your app’s statistics as they are collected.

The complete documentation for the Flurry Analytics plugin can be found here.

Want to discuss further? Please join us in the Corona forums.

Tags:
, , ,
Rob Miracle
[email protected]

Rob is the Developer Relations Manager for Corona Labs. Besides being passionate about helping other developers make great games using Corona, he is also enjoys making games in his spare time. Rob has been coding games since 1979 from personal computers to mainframes. He has over 16 years professional experience in the gaming industry.

11 Comments
  • Nicolas
    Posted at 14:10h, 12 April

    Great job 🙂

  • Marcus
    Posted at 15:09h, 12 April

    Great but could you guys take a look at the issue with Google Analytics for iOS? If it cannot be resolved, I would need to consider switching to Flurry.

    https://forums.coronalabs.com/topic/61785-google-analytics-producing-idfa-error/

    Thanks.

  • Junhyun
    Posted at 15:36h, 12 April

    Good.
    When can enterprise users can use this updated plugin?

    • Rob Miracle
      Posted at 15:39h, 12 April

      It should be in the next daily build’s Enterprise plugin tar.gz file. If it doesn’t remind me in the forums and I’ll make sure it gets added.

  • Rémi
    Posted at 04:13h, 13 April

    With the update we can send table (params (event.data.params) (table) ), the table can be of many dimension? (tab[][][]…)

    • Ingemar Bergmark
      Posted at 08:25h, 14 April

      Hi Rémi,
      No, the table can only be a simple key-value table. This is a limitation enforced by Flurry’s SDK.

  • JL
    Posted at 11:17h, 14 April

    I’m developing for Amazon’s app store where Google’s Play services aren’t available. Will the Flurry plugin work without [“plugin.google.play.services”]?

    • Rob Miracle
      Posted at 11:38h, 14 April

      Many android devices even if they come from Amazon will have Google Play installed if I understand correctly. It’s the Kindle Fire devices that won’t be supported.

  • Rémi
    Posted at 03:25h, 19 April

    The plugin don’t work on android 4.2 and previous!
    On buildsetting is it possible to add an exclusion on the plugin for different type of Android

  • Rémi
    Posted at 03:45h, 19 April

    I think I find a way to correct this bug.

    local function timerlong(event)
    analytics =require( “plugin.flurry.analytics” )
    local function timerlong1(event)
    if analytics~=nil then
    analytics.init(“…”)
    analytics.logEvent(“lancement”)
    end
    end
    timer.performWithDelay(5000,timerlong1)
    end
    timer.performWithDelay(5000,timerlong)

  • J. A. Whye
    Posted at 16:03h, 25 June

    Does the legacy version still work?