{"id":823,"date":"2022-09-17T00:01:42","date_gmt":"2022-09-16T22:01:42","guid":{"rendered":"https:\/\/www.bellingo.de\/blog\/?p=823"},"modified":"2023-05-12T17:44:52","modified_gmt":"2023-05-12T15:44:52","slug":"devblog-why-i-ditched-unity-analytics","status":"publish","type":"post","link":"https:\/\/www.bellingo.de\/blog\/devblog-why-i-ditched-unity-analytics\/","title":{"rendered":"DevBlog: Why I ditched Unity Analytics"},"content":{"rendered":"\n

I just finished compiling the privacy policy statement for Network Traders<\/a>. With the alpha release coming up next Friday<\/a>, September 23rd, that was about time. On my game server, I try to store as little data as necessary, and none of it should be personal. Unity, on the other hand, is rather nosy. That is ok, as they need most of the data to run their services. With Unity Analytics<\/a> however, there is additional data collection involved, and one specific risk I did not want to bear.<\/p>\n\n\n\n\n\n\n\n

Unity Analytics is part of Unity Gaming Services<\/a> (UGS), a collection of useful tools which help you manage your game. Analytics captures data about the state of your game, and provides lots of useful statistics. Those Key Performance Indicators<\/a> (KPIs), on one hand, include simple values such as the daily and monthly active users (DAU and MAU), and more complex ones such as the average revenue per paying user (ARPPU). On the other hand, Unity Analytics helps you get insights about your player’s progress and behaviour. Certain events are captured during gameplay and can be evaluated later.<\/p>\n\n\n\n

\n