-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
better analytics #8
Comments
Okay, I think we're now tracking most of the data on the statistics screen. Stats verified to be working and visible in realtime:
It's possible that I'm logging too much here and may need to pull back if I'm hitting any analytics limits. Throttling the total-purchased stat would be fine. Custom dimensions/metrics that are now logged, but not available in realtime reports - we can verify these in ~24 hours:
Total unit count is not tracked, only purchased units - so, ex. drones built by queens don't appear in the metrics. That's fine, more interested in what tier they're at. It's common to buy the first unit in a tier to unlock twin upgrades though, so that might throw the metrics off a bit - they buy one of tier n then continue building tier n-1. Meh, close enough. |
app version is working. save file size and click log size are not. looks like scoping in ga was wrong: product instead of the only other option, hit. changed, let's take another look tomorrow. |
This is now logged, but not in a useful way! GA only seems to want to tell me the total for all players, or show me how many sessions had exactly the same total. |
#58 makes click log size obsolete, and save file sizes are relatively small - way less than 10k - so I'm not going to sweat this. I'm satisfied with our analytics for now. |
once people start playing, make the analytics better. we have a few basics, (player count, session length, button clicks), but still missing a lot. at a minimum, to know how fast people are progressing:
extra credit:
do this sooner rather than later, we need this info to balance the game
The text was updated successfully, but these errors were encountered: