Search Unity

Aggregation for ints (maybe floats)

Discussion in 'Unity Analytics' started by mcarriere, Dec 9, 2015.

  1. mcarriere

    mcarriere

    Joined:
    Sep 14, 2012
    Posts:
    106
    Howdy!

    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?
     
  2. mpinol

    mpinol

    Joined:
    Jul 29, 2015
    Posts:
    317
    Hi @mcarriere,

    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, https://analytics.cloud.unity3d.com/support 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.
     
  3. marc_tanenbaum

    marc_tanenbaum

    Unity Technologies

    Joined:
    Oct 22, 2014
    Posts:
    637
    Might be worth your time to watch this video, which covers Analytics best practices, including management of Analytics Points.
     
    mpinol likes this.
  4. mcarriere

    mcarriere

    Joined:
    Sep 14, 2012
    Posts:
    106
    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?
     
  5. mpinol

    mpinol

    Joined:
    Jul 29, 2015
    Posts:
    317
    Hi @mcarriere,

    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!