Raw Data custom event fields used to be numeric, now string

LiveOps Analytics
1

Hi!

I’ve been going through the event manager and noticed that ~80% of my what used to be numeric custom event parameters are now treated as strings. In some cases they are even duplicated in the data manager (1 numeric field, 1 string field with the same name).

From what I can see in the Data Manager (see below), the change started around the 11th of January.

2938656--217435--Capture.PNG
2938656--217435--Capture.PNG1411×645 71 KB

It seems like the data manager handles this pretty well as it looks like the purple curve corresponds to the sum of the green curves.

Where it gets weird, though, is in the raw data. Where I used to have long or double JSON fields for numeric values:
"custom_params": {"waveId": "Wave15", "waveSuccess": 0.0416666679}
I now have strings:
"custom_params": {"waveId": "Wave15", "waveSuccess": __**"**__0.0416666679__"__}

I might be overthinking this, but this seems like a pretty drastic data contract change that has the potential to mess up with some data analysis pipelines…

It looks like this is related to the recent change in data processing limits.

But is this a bug or a feature? :slight_smile:

2

@Mangatome ,

This is a feature. It is a benefit of our changes to our back end processing that we made recently. So if you send us a levelNum parameter, we won’t just give you the average of those values (since that’s not really useful data), will will show you the count of each value sent. You can read more about the changes here:

https://forum.unity3d.com/threads/new-data-processing-limits.450266/

That does not sound like a feature. The changes we made should not have affected Raw Data Export in any way. We are going to investigate this a bit further. Could you DM your project ID?

3

@ap-unity

Edit: Actually, looking further back in the data, it seems like these fields were always exported as strings (even by the v1 API). So, my bad, sorry for undue alarm!

1 Like