We have a strange thing going on with some of our boolean values. When I look up the event property in Amplitude, it shows values that are uppercase (True/False) as well as other values are lowercase (true/false).
We have 3 clients -- iOS, Android, and Web. The iOS one is sending mostly lowercase values, while Android and Web tend to show uppercase values.
Event properties have clear cut behavior -- Android/Web is purely uppercase boolean, iOS is purely lowercase. However with User Properties, it seems cross-platform behavior will make some bleed between these rules, although the overarching trend is the same -- Android/Web is upper, iOS is lower.
I can’t quite believe this is our doing. Android and Web both use languages that are, by default, lowercase booleans. So there would be no reason for us to change the value sent to Amplitude.
Has anyone else ran into this issue? Anything we can do about it?
Best answer by MikkoKarvonen
Have you verified that this is not related to the way the event property values are set on each platform? I.e. that they are not actual booleans, but instead strings that are set as “True” and “False” on web and Android, and “true” and “false” on iOS.
The mixing of the values in user properties sounds, as you suspected, simply a result on cross-platform activity, and each platform is actually setting the values in one way only.