Game analytics just got a whole lot better at Clay.io!
The beauty of HTML5 games is they are cross-platform by nature — you’re not limited to a single app store. You have a multitude of options like The Chrome Web Store, Mozilla Marketplace, Facebook, Windows 8, Clay.io, and many more — all of which you should be using. With such a variety, you do need to know which marketplaces are performing the best, so you can focus your effort.
Ideally you want to:
- Get your game in as many places as possible (it’s easy, we make it easier)
- Track how your game(s) perform on each platform, and put more focus where your game gets the best conversions. Our API is now perfect for this!
We’ve offered analytics as part of our API for quite some time, but prior to today it was minimalistic. Analytics are incredibly important for games, so we decided to improve that aspect of the API, and make it something HTML5 game developers absolutely need in their games. Since we’re dealing with HTML5 games, we also put a focus on displaying the stats on a per source basis, so you can see which app stores / portals are worthwhile.
Statistics We Track Automatically
If you’re using the Clay.io API, we’re already tracking a variety of statistics for you — things like high score postings, achievements earned, payments processed, time played, etc… There’s no need to do anything extra to get these stats working if you have already implemented those API features. If you aren’t using our API for those features, have a look at our documentation.
To take it one step further, you can define your own custom statistics to log various metrics within your game. For example, you can log the number of users that are able to finish each level in your game. All of this is tracked per platform/marketplace/app store (whatever you want to call them), expanding the possibilities of what you can do by quite a bit! Documentation for custom statistics can be found here.
Normalizing By Other Metrics
Each app store is going to send a very different amount of views for your game, and sometimes what you care about is the effectiveness of that source — so, rather than total views, you might care about engagement per view (time spent playing per view, per source), or payments processed per view (which app store is making you the most money). Understanding these metrics is pivitol in determining where you should focus your efforts.
Using the API Helps, But Isn’t Necessary
You don’t even have to be using the API to take advantage of certain parts of our analytics. If your game is hosted on Clay.io (see the documentation here), we’ll track the views from each source. Of course, if you want more advanced tracking like payments processed per view, you’ll need to be using our API (which just so happens to be very easy to install).
Our API, Modularized