anyone have simple tutorial in integrating analytics in corona sdk?? like flurry cause mine is not work well 
i got a flurry sample in corona but it was not working… i was very confuse specially in flurry site…
Im new here 
anyone have simple tutorial in integrating analytics in corona sdk?? like flurry cause mine is not work well 
i got a flurry sample in corona but it was not working… i was very confuse specially in flurry site…
Im new here 
Hi @dominicdev,
Which sample are you using to test? Did you try the most current Corona sample app located in your local Corona SDK application directory?
Corona SDK > SampleCode > Analytics > FlurrySample
If so, what error are you receiving? Can you tell me a specific problem that’s occurring?
Thanks,
Brent Sorrentino
shall i recieve immediately the info in the flurry site??
Unfortunately no, Flurry doesn’t publish analytics for your app in real time. It’s usually delayed by about 24 hours.
oh… Ok Thanks
I already have data in Flurry site but nothing in Events… is thier a specific in naming the event to anable to show in flurry site?or it will automaticaly show what u named in ur event? cause i use the sample flurry code in corona sdk…
This was tha actual code im using to test flurry if it is work… the Sessions was working fine but nothing in Event…
Event should show automatically in your Flurry dashboard with whatever you named them. There’s no special naming required. You should see them in the dashboard under the Events section.
I vaguely recall reading once that events take a bit longer to show up than session data, but I can’t seem to find where I read that. If they don’t show up after another day, then we can look into it more to figure out what’s wrong.
Andrew,
I’m also seeing a problem with LogEvent on Android, with an older Corona build 971 as well as the latest build 1076. The sessions/users do show up in the Flurry dashboard (for both iOS and Android), but the Android stats are lacking events entirely. This leads me to think my code is ok, but there’s a problem with the flurry API w.r.t logging events.
Any ideas?
(edit: I should clarify, I do* see the expected events listed for iOS, so the problem is specific to Android)
Never mind. My problem turned out to be that I detected Android incorrectly and initialized with an iOS flurry app id.
Hi @dominicdev,
Which sample are you using to test? Did you try the most current Corona sample app located in your local Corona SDK application directory?
Corona SDK > SampleCode > Analytics > FlurrySample
If so, what error are you receiving? Can you tell me a specific problem that’s occurring?
Thanks,
Brent Sorrentino
shall i recieve immediately the info in the flurry site??
Unfortunately no, Flurry doesn’t publish analytics for your app in real time. It’s usually delayed by about 24 hours.
oh… Ok Thanks
I already have data in Flurry site but nothing in Events… is thier a specific in naming the event to anable to show in flurry site?or it will automaticaly show what u named in ur event? cause i use the sample flurry code in corona sdk…
This was tha actual code im using to test flurry if it is work… the Sessions was working fine but nothing in Event…
Event should show automatically in your Flurry dashboard with whatever you named them. There’s no special naming required. You should see them in the dashboard under the Events section.
I vaguely recall reading once that events take a bit longer to show up than session data, but I can’t seem to find where I read that. If they don’t show up after another day, then we can look into it more to figure out what’s wrong.
Andrew,
I’m also seeing a problem with LogEvent on Android, with an older Corona build 971 as well as the latest build 1076. The sessions/users do show up in the Flurry dashboard (for both iOS and Android), but the Android stats are lacking events entirely. This leads me to think my code is ok, but there’s a problem with the flurry API w.r.t logging events.
Any ideas?
(edit: I should clarify, I do* see the expected events listed for iOS, so the problem is specific to Android)
Never mind. My problem turned out to be that I detected Android incorrectly and initialized with an iOS flurry app id.