The Game Parameters manager shows all the game parameters that have been set up on the game and lets you add new ones.

Game Parameters are used to send information from the game to deltaDNA and back again. This includes information sent from the game in events and information sent back to the game in Engage campaign actions.

Add and edit game parameters

New game parameters can be added and existing parameters edited in the DEV environment by navigating to SETUP > Game Parameter Management and clicking on the edit button at the end of each parameter row or the Add Parameter button.

Each parameter can have metrics selected, which are then accessible through the user_metrics table and for metric segmentation.

Parameters can also be associated with Category Tags to make them easier to find when filtering some tools by category. You can also define your own Categories in the Category Manager tool.

Important: You cannot change the name or type of a parameter after it has been saved.

Number of parameters and metrics

For each added parameter a new column will be created in the events table. For each metric there will be a new column in the user_metrics table. Up to a total of 1500 columns can be created in these tables. This means that you can have up to 1500 different parameters and in total can keep track of 1500 metrics per user.

Note: Keep in mind that each time you enable a metric it will consume another column in your user_metrics table, so only enable the metrics that you know are going to be useful to your analysis or you will just bloat your tables and table legends for no obvious benefit.

Reserved names

Game parameters cannot be created using any of the following words as a name:

These names can be used for your parameters, however please make sure to import them through the custom event templates. Additionally some of these parameters are used for some internal features:

Avoid using parameters starting with either “ddna” or with “ga”. In general, it is a good idea to follow our naming convention and use descriptive names. We require the use of lower camelCase and suggest making sure that the name can’t be overloaded by a different meaning of the same word.