Unity Analytics gives you at-a-glance insight into how users interact with your game or application and enables you to drill down for more detailed information. Some information is generated automatically simply by user interaction, and some is detailed by events. Events are notifications you get when certain actions happen in your game; they must be triggered by code or a GameObject with an attached Analytics Event Tracker component. There are standard events, such as a player completing a level or watching an ad, and custom events. Custom events are great for answering specific questions about your game and seeing how a design decision plays out. For example: Can the player find the warp zone hidden in the water temple? Who do they save when forced to choose between a family member and a large number of strangers?
When you enable Unity Analytics, you are asked to assign it to an organization. By default, your account has one organization: your user name. Organization names must be unique. You can add (but not delete) more, or rename an account at will, as long as the name is available. You might wish to have one organization for your solo projects, and one for your team.
In this workflow, we’ll cover how to connect a project to Unity Analytics from within the Unity Editor, how to send a standard event with the Unity Analytics Tracker, and how to find the Operate Dashboard to view collected data. For more information on using Analytics in code, see the Scripting Reference.