Great work on the Analytics system! Just a question about how best to track level times with the scene names.
Here’s what Im hoping to get out of this:
List of completion times in graph form (not averages) to see common completion times.
be able to group this data by scene name.
Here’s the code Im using:
public void FinishLevel(float raceTime)
{
// get currently loaded scene name
string levelName = Application.loadedLevelName;
// convert float to string for better analysis
string raceTimeStr = string.Format("{0:00000}s", (int)raceTime);
//
Analytics.CustomEvent("FinishTrack", new Dictionary<string, object>
{
{ "Scene", levelName },
{ "RaceTimeStr", raceTimeStr },
});
}
I was submitting the times as strings so that they wouldn’t be averaged (as numbers are treated differently than strings). To keep the strings simpler, Im simply truncating the decimal point, whole seconds are enough information for my purposes.
Heres what Im finding, and please let me know if theres a better way to be doing this!
Completion times dont seem to be organized alphabetically.
I cant find a way to group the completion times by the scene name that is also stored in the dictionary.
Currently this sounds like the best way you could go about viewing this data. One thing you could do would be to send a unique Custom Event for each level completion so that each level’s completion times would be entirely separated. For example, ‘FinishTrack01’ would be the Custom Event that is sent after completing level 1.
Thanks for your reply! I was considering this as well, maybe this is the only option currently.
It would be great to keep the data packaged up neatly in one custom event and just filter the data, also wouldn’t adding additional custom events use up more of my allotted 1000 points? Ill give it a try for now though!
Was there a particular feedback item? The link just took me to the main analytics feedback page. Id be happy to vote for this!
Yes, making the extra Custom Events will use a lot more of your Analysis Points, but while we are in Beta if you hit your limit get into contact with us and we will check out the possibility of upping your limit.
I believe it was ‘Custom Queries’ that has gotten the most attention related to this issue.
If I do start using this method during beta and it does get fixed, it will add some complexity to change this after the app goes live. I hope this can be addressed soon. Is this currently something thats being looked into on the development side?