Analytics

Have feedback or questions on this section? Just click the Help tab on the right side of your screen.

Analytics/FAQ

Welcome to Flurry Frequently Asked Questions

Contents


Where’s my data? How often is data updated on the Flurry portal?

Flurry Analytics processes real data several times a day. If you just implemented Flurry Analytics you should expect to see data reporting to your project's analytics page every few hours from when you first launched your application integrated with the SDK. The first place your data will appear is the Event Logs section, located in the Events menu. From there, the remaining metrics and associated charts will subsequently be populated with this data.

How are sessions counted?

If the app pauses or moves to the background for more than 10 seconds, the next time the app runs, Flurry agent will automatically create a new session and end the previous session. Otherwise, Flurry agent will continue the same session. This can be updated via the setSessionContinueSeconds method. If the app is terminated, a new session will be created when the app runs again.

What happens with my data during maintenance?

We continue to collect data from mobile applications even during maintenance. If you are using Flurry Analytics to monitor your mobile applications you will not lose any data due to this maintenance period.

Is there a way to ignore "test" data or specific devices for analytics?

We currently do not have a way to "reset" data at this time. You may want to try the following approach to prevent test data from appearing in your stats: create two projects, one for development/testing and one for consumers. When you are ready to send the application to the public, you can swap to the project key that points to the consumer project.

Another alternative is to set the custom time frame at the top right of the page in the analytics view of the application to start on the date the application is released. That way, no previous data from testing/development will show in this timeframe.

Is Flurry Analytics iPhone SDK compatible with the iPhone 5.0 OS?

While Flurry Agent version 2.7 and up are compatible with iOS 5, we strongly recommend you upgrade to version 3.0 and up to get the latest Analytics features.

How do I know if a new version of my SDK/Agent code is available?

View the project you are currently working on. If there is a new version of the SDK available you will notice the NEW SDK Upgrade Available link located next to the Create New Version and View Changes Logs links on the bottom of your project.

Click on the NEW SDK Upgrade Available link to download the latest SDK.

If you are using the JavaME Agent version you will have to re-upload your Java application for the new Flurry Analytics changes to take place.

For Windows Phone, although the newest version of the SDK will be shown for all Windows Phone projects, the newest version is compatible with Windows Phone 8 applications only.

What should I do if I want to create a new Windows Phone 7 project? What will happen to my existing Windows Phone 7 project?

You may continue to use your existing Windows Phone 7 project, and you may also create a new Windows Phone project and continue to use it with your Windows Phone 7 applications. If you already have the WP7 SDK, there is no need to update your current SDK to maintain compatibility.

However, if you do need a new copy of the WP7 SDK, please contact support@flurry.com, and we will provide one to you.

Can I track Events (e.g. pressing of a button) with Flurry Analytics if my app is a wrapper to my mobile website? The actions take place on the site server that the app is wrapping.

Yes, you can track these Events. If the action you want to track (e.g. button pressing) exists in the app code, then simply log an Event on the app side. If the button exists on the mobile webpage shown in a Web View, you will need to inject a Javascript function that will fire off an additional custom URL when the button is pressed. This URL will have a custom scheme, for example, “myapp://buttonclicked”. Then in the app code, you will need to capture that URL before your Web View fires it. When you see that the URL is your specified URL (“myapp://…”), you can log an Event on the app side.

There are several ways to capture the custom URL before it is loaded by the Web View. In iOS you would need to implement the UIWebViewDelegate method webView:shouldStartLoadWithRequest:navigationType:. On Android, you could implement a WebViewClient with the shouldOverrideUrlLoading method.

I've looked through all the relevant areas of the Support Center and read the FAQ, but I still have questions.

We'd love to hear from you. Please send us an email to the appropriate address below:

Publishing support
publishers@flurry.com
Integration support
integration@flurry.com