Tracking page views with the Flurry SDK?

Question

I have built-in mobile analytics in my iPhone application using Flurry analytics, but I can’t track page views.

I used the following code in my delegate deletion and passed an instance of UINavigationController instead of navigationController
[FlurryAPI logAllPageViews:navigationController];

But when checking page views on the Flurry website, it displays the following message:

You are not currently viewing the View Data page.

Is there something I should include on the website itself?

Answer 1

If this question is still open or relevant, you might want to make sure that you add a navigation controller that is responsible for your navigation. Try posting some code with your questions, this will give better answers.

It also takes a little time to see the results published in Flurry.

Answer 2

It’s good that now you see your data.

On Page Count: Flurry Analytics SDK counts the number of page views. If you want to see which pages in your application are visited by users, I suggest creating events for each of your screens. A report on user tracks in the events section of your dashboard will give you a clear idea of ​​how your users navigate your application.

Answer 3

The "logAllPageViews" method increases the number of page views for a session based on crawling the UINavigationController or UITabBarController. If you want to track screens with the screen name, just use the logEvent method of the FlurryAnalytics class, for example

[FlurryAnalytics logEvent: @ "screen name"];

source (check for logAllPageVeiws and logPageView): http://support.flurry.com/sdkdocs/iOS/interface_flurry_analytics.html#adb7d3bd888a40343269c53f65acf7720

Answer 4

Another advantage of using events is that they were recorded for several minutes , displaying in Flurry event logs long before they accumulate in the resume. This quick turn can be vital for debugging, as described below.

Pay attention to other information, if you don’t see anything, in case of using iOS I ran a lot of tests, and events were not even shown.

It turned out that the code was initialized with

 [Flurry setSessionSReportsOnPauseEnabled:NO]; [Flurry setSessionSReportsOnCloseEnabled:NO]; 

They presumably fill in your path data before the next session. However, some side effects of debugging meant that buffering was not saved, so my events were never dispatched.

(I have inherited a large code base recently, so things still amaze me.)

Answer 5

You can also use Localitics for this purpose: http://www.localytics.com , unlike the other services mentioned, you will immediately see your results so that you can integrate, test and complete this process in less than 10 minutes.

The easiest way to track page views with Localytics is to mark an event when each page loads. You can do this with a single API call (a modified version of the example in the docs: http://wiki.localytics.com/doku.php?id=iphone_ios4_integration ). To track the page, code: [[LocaliticsSession sharedLocalyticsSession] tagEvent: @ "Start Page"];

Another useful thing you should do is add an event to your application, WillEnterBackground, which marks the application exit event, which records what screen the user was on: NSDictionary Dictionary * [NSDictionaryWithObjectsAndKeys Dictionary: @ "Exit Screen", current_screen_name, zero]; [[LocaliticsSession sharedLocalyticsSession] tagEvent: @ "Exit the application", attributes: dictionary];

This way you can quickly see the distribution of the most common exit pages.