Release: Google Analytics module

Solar2D General Questions/Discussion
#61

I got it working!  Looks like it was an ID 10 T error.

But I have another question.  How can I specify screens?  I see in Google analytics that it tracks screens, but how do I tell it when it’s hit a new screen?

Thanks!  This REALLY helps me!

#62

You use:

ga.enterScene("my screen name")

So with composer you could do:

[lua]function scene:show( event )

    if ( phase == “will” ) then

     

    elseif ( phase == “did” ) then

        ga.enterScene(“my screen name”) – or ga.enterScene(composer.getSceneName( “current” ))

    end

end[/lua]

#63

Thanks JonJonsson for this great plugin!

Here’s something to be aware of if you are having a problem with the analytics working fine in the simulator but not working on devices. It is not a problem with the plugin. It is something that can happen in the GA dashboard quite easily if you click on the wrong thing.

When you test in the simulator and look at the Real-time events or Overview in GA, you’ll see something like this:

ga1.png

That means it is working fine from the simulator.

If you happen to click the red-orange square next to DESKTOP or click the 100% bar , GA will create a FILTER to view ONLY Desktop users. Any subsequent testing you do on real mobile/tablets will NOT show up until you dismiss the filter.

Here is what the filter looks like:

ga2.png

Events from Mobile or Tablet devices will not show up until you click the X in the blue button to dismiss the DEVICE CATEGORY: Desktop filter.

This drove me crazy for a couple of hours, so I thought I’d share.

Cheers!

#64

 It is works for me! 

ga.init({ &nbsp; &nbsp; isLive = false,&nbsp; &nbsp; &nbsp; testTrackingID = "UA-0000000", &nbsp;-- \<-- Replace with your tracking code. If code is wrong it fails silently. &nbsp; &nbsp; debug = true, })

In alpha and beta tests, this work only “Real time”?

And this “debug =true”, I need change to “debug=false”, when the app will go to production?

Thanks! 

#65

For production, you will need to change debug to =true and you will want to add productionTrackingID = ‘[your real tracking code]’

If you have been using your production tracking code to test with, then the testTrackingID and the productionTrackingID would be the same. JonJonnson has provided the option to use different codes for testing and production as a convenience, but using the same one works fine too.

#66

i was putting GA into a new app i’m finishing now and managed to test this again.

It is only a problem of running on the Corona Simulator in Windows environment.

if it’s Corona on Mac Os X, it does show up in GA normally… just in windows…
but no problem, since I know this, it doesn’t bother me anymore :slight_smile:

#67

 It is works for me! 

ga.init({ &nbsp; &nbsp; isLive = false,&nbsp; &nbsp; &nbsp; testTrackingID = "UA-0000000", &nbsp;-- \<-- Replace with your tracking code. If code is wrong it fails silently. &nbsp; &nbsp; debug = true, })

In alpha and beta tests, this work only “Real time”?

And this “debug =true”, I need change to “debug=false”, when the app will go to production?

Thanks! 

#68

For production, you will need to change debug to =true and you will want to add productionTrackingID = ‘[your real tracking code]’

If you have been using your production tracking code to test with, then the testTrackingID and the productionTrackingID would be the same. JonJonnson has provided the option to use different codes for testing and production as a convenience, but using the same one works fine too.

#69

i was putting GA into a new app i’m finishing now and managed to test this again.

It is only a problem of running on the Corona Simulator in Windows environment.

if it’s Corona on Mac Os X, it does show up in GA normally… just in windows…
but no problem, since I know this, it doesn’t bother me anymore :slight_smile: