I recently watched the Unite talk on the new Unity Services and decided to try out Unity Analytics for our current in progress game. I'd like to preface this with some facts about our games and production, so that there is appropriate context for this feedback on our experience with setting up the package, and beginning recording of data. About Us (and Me, the dev implementing the Analytics package) - We have worked on multiple shipped titles on Steam, Switch, iOS, and Android with small teams. These include well received titles such as QuiVr and Marble It Up! on Apple Arcade. I mention this because some of the feedback I have is about the types of analytics we want to collect that don't seem to be a major focus of the package, but are still really important for games other than just indies making their first itch.io game (no offense intended) Additionally, we are not strangers to analytics services, having used systems like Google Analytics, Amplitude, Firebase, etc. as well as the Unity Analytics that was available many years ago that we switched away from due to some of the same missing features that I'll be talking about here. So without further ado, here are some friction points, issues, and good stuff I've found while investigating and implementing the most recent (4.3.0) Unity Analytics Service package and web portal.