Event Tracking can be used to identify a wide range of occurences in your App. This can range from tracking how many times a level was played, which are the most popular In-App-Purchases, is a certain check point was reached, etc.



Event Tracking - for GameSalad®

Prerequisite: The BasicsX

Step 1.

Go to the "MY APPS" dropdown menu and click on the "My Event Triggers". Here you will define your Events by name. Defining the Event Names here, is important for selections when viewing analytics results later. Take care to use the exact same names in your projects.

It is advisable to plan out the types of Events you wish to track during the early stages of your project.

Find a good naming convention to clearly define the desired Events.




Step 2.

Go to any scene of your project and deside on an Event you which to track.

At the appropriate location we can either create a seperate actor or add to an existing rule. Start off by creating a Timer Behaviour with "After 0.02 seconds" and "Run to Completion" as properties.

We will now add a "Change Table Value" Behaviour into the Timer, choosing the appropiate analytics Table as defines in Tutorial 1.

Row and Column must both have the value 1.

In the "Value" Field, we will enter an appropriate Event Name (in quotation marks). This will let us identify and study this Event later during analysis.


Optionally, you may wish to associate a numeric qualifier with certain events. As an example, the length of a level, together with an "LevelCompleted" event.

To do this, click the plus sign on the right, next to the "Value" entry. This will allow you to enter a value for a second Column. In the "Column" Field enter 2.

In the "Value" Field, enter your integer value. The value may represent seconds, minutes, number of lives, etc.

Under Charts in the MyApps section, you may then view the distribution for a specific Event together with its numeric value.




Step 3.

Now we are going to drag a "Network Send Table To URL" Behaviour into the Timer. Pick the appropriate Attributes and Table as indicated in the image below. The Callback Attribute can be any integer attribute and will change to a value of "1" once the network send executed successfully.





Done!

This is all that is needed to implement Event Tracking.

Your project will now capture a data point every time this Event is reached and can later be studied in the analytics.

Continue adding more Event Triggers to your app, identifying each by their unique Event Name or using the same names for related events.

The tutorial on A/B Testing will show you how to use Events to perform A/B Testing in your Apps.