After a little more than two weeks of work, I just released version 2.0 of our game analytics API. This version is much more flexible than the previous one and allows storage of more custom data. The new API provides three resources:
Players - takes a unique identifier and multiple custom properties
Devices - takes a unique identifier and multiple custom properties
Events - takes a player and/or device identifier as well as multiple custom properties
Another big advantage of version 2.0 is that it is more asynchronous. Before, we were asking you to retrieve some unique identifiers from our service. Now, you go ahead and create your own identifiers and send data to us in any order that you want. You can send us the player first or the device or the event; it does not matter. We tie in everything together on the backend.
I also dropped the requirement to send events with JSON. Now, you just add as many custom parameters as you want to your request and they get added as properties to your event, player or device. This technique requires less code and drops the need for a JSON library. This is great because it drops the size of our Unity wrapper. Our Unity wrapper is now about 300 LOC not counting comments. This reduced size should be great for mobile games.
I encourage you to check out our new game analytics API at API Support
. If you have any questions about it or our service, please feel free to contact us or leave a comment below.
blog comments powered by