When we originally designed our analytics, we did so in a way to optimize against the points system.
This meant that we used an int of 0 or 1 for “enabled”, or a float for the screen ratio, or an int that references an enum to define a particular type of match, or a difficulty setting for the AI.
All of these things really are meaningless to us in terms of viewing them as averages, counts, or sums, and they really need to be dealt with as something that can be viewed as an aggregation of the passed in values.
Changing this approach to a string based value is going to make some of our analytics “costs” (in terms of points) explode, which is pretty frustrating. Is there anything that can be done, or is being done, to view the data as an aggregation?
If you would like we can take a look at raising your total amount of Analysis Points. Can you please open a support ticket from your project dashboard here, Unity Cloud so we can take a look.
With the raised limit you should be able to send your string events to view them as aggregations rather than sums and counts.
Watched it, and implemented the suggestions. The only thing that I find somewhat annoying is the requirement to prefix numeric strings with a character. Is that going to be a long-term problem?
For the immediate future this requirement will remain. That being said, we are looking into/discussing making changes that will remove this requirement. I cannot give you any real information as to a timeline, but it is something that we are fully aware would be a great help to developers!
