Get started

1. Creating an Event List

  • To ensure data integrity we require the events to be set up in the platform before the data can be sent from your game.  This makes certain that the data is as clean and precise as possible. See manage events.
  • The platform has 50 pre-defined events that cover the vast majority of behaviors in games
  • The ten basic events are pre populated for your game
  • Creating new events or adding parameters to existing events is also easy using the powerful event management interface.

2. Instrumenting the SDK

  • You now have the events set up to start collecting data. The next step is to add the data collection SDK to your game.
  • The deltaDNA platform accepts data in a JSON format. You can send us the raw JSON through the REST API or you can use one of our SDKs to help you send the data to us
  • If you are using a server based game where the data is being sent directly from your server you should use the REST API. If your game is on mobile you should include the Android SDK or iOS SDK. For those games that are using Unity as the platform there is a specific UNITY SDK
  • The first thing you must do is to get the dedicated URLs and environment keys for your game, you will need these to make sure the data is flowing to the correct place in the platform. These are available in the game details page.
  • Follow the quick Get Started tutorial for each of the SDKs, which walks you through implementing the basic 4 events that will get data flowing. This should take no more than an hour and you will be collecting the data to drive the dashboard.

3. Making sure the data is correct

  • From the front screen you can see what data is being sent and where data is coming through with errors
  • There is a set of QA tools that allow you to quickly validate the JSON that is being sent, these tools will give you in depth responses so you can see exactly what is wrong with the data that you are sending us
  • The Event Browser tool allows you to look at the last 100 events that have been received by the system in the last 2 hours. If the event has errors you can see what is wrong with the event. You can also track specific events or specific users to see that the right events are coming in as you would expect.

4. Going Live

  • You have two versions of the game, Dev and Live, to ensure that development data does not get mixed up with real data.  You should do all the testing on Dev to make sure the data is correct and the event definitions are exactly what they should be. Once you have them right you can push the events to live
  • Going live means swapping the app key and pushing the latest version of the events over to the live environment
  • Keeping QA to Dev makes it easier to see the events come through; you will only be working with a small number of users so it is nice and easy to track users and validate the event sequences.

5. Giving other people access

  • You can easily invite other users on to the system using the Invite User functionality
  • There is a set of default roles set up, but you can easily edit and add to these roles in the Roles tool.

6. Setting up other Games

  • Deltadna is a powerful system for one game, but adding in more games allows you to look across the games using the Slice & Dice tool
  • You can easily set up a new game by going to Account Overview in Setup and pick Games. This lets you add new games, change the package you are on to unlock more features as well as see the current game details
  • Each new game will appear on the main intro screen so you can see at a glance how each game is performing.