Flurry Analytics, basic analytics issues

Question

Does anyone have experience using basic analytics services with the Flurry Analytics SDK?

I have two applications with which I am testing this. Both are existing applications, to which I added the Flurry SDK and set up tracking of major events - the applications were updated and went live in the application store about 16 hours ago. I know that there were users, I myself widely used the updated version.

The problem is that there are no new users on the Flurry dashboard, there are no monitored events. The only information on my Flurry panel is the 1 new user that I tested the service the week before I sent Apple.

I have the appropriate files and library imported in my project for Flurry. In my appDelegat.m didFinishLaunchingWithOptions method, I have:

[FlurryAnalytics startSession:@"MY_APP_KEY"]; 

When I want to log events, I use:

 [FlurryAnalytics logEvent:@"EVENT_NAME"]; 

Pretty standard stuff, but it never seems to track it or update it. Does anyone have any experience? How often does it update the web dashboard? Am I doing something completely wrong?

Answer 1

He may someday accept Flurry long before he first updates the new data. When I first set up my application with Flurry, it took several hours before my first test data was reflected.

I suggest waiting a little longer, and if there is still no data, contact Flurry Support.

In fact, you can contact them right now and ask about problems, there is no harm. But I think they will only ask you to wait.

Answer 2

I encountered the same problem when testing Flurry using a simulator or device from Xcode. The problem was that I killed the application with Xcode right after testing and sending events, and no data was sent to the Flurry server.

Data is sent only to the server when the application goes into the background, so click the "Home" button and wait 10 seconds before killing the application.

You can also turn on the debug log and see when the data is sent, and if the answer is correct (http code = 200):

 [Flurry setDebugLogEnabled:YES]; 

This can take a couple of hours for the data to be visible in Flurry reports.

Hope this helps.

Answer 3

I use a flurry in my game. Wait 3 or 4 days and you will see the data.

Answer 4

I had the same issue and contacted support. They said:

Although the Flurry SDK sends data from devices to our servers almost in real time, there may be a delay of 5 minutes to 7 hours depending on network traffic and demand on our servers.

Event logs are displayed for 5-7 minutes on the device.

Other indicators may take up to 6-7 hours to process and display.

Hope this clarifies.

After 5 hours, it reflects and works normally.

Answer 5

In my experience, Flurry is updated at least twice a day. I’m used to updating Google Analytics much faster, but I can’t complain much. Flurry is pretty decent as far as google analytics goes.

Answer 6

I had the same problem, and I decided to replace it, replacing all the space characters with underscores in the event names, and they appeared after 5 minutes.

Invalid Log

[FlurryAnalytics logEvent: @ "EVENT NAME"];

Correct magazine

[FlurryAnalytics logEvent: @ "EVENT_NAME"];

This naming convention is not mentioned in the FlurryAnalytics documentation, but it worked for me.