Unity collects Analytics data by dispatching events when someone uses your application or game. Unity dispatches a set of core events automatically. You can dispatch additional events to collect richer and deeper information about how users play your game or use your application.
The types of Analytics events include:
Unity dispatches Core Events automatically. You must dispatch the other types of events at the appropriate times. You can dispatch Standard and Custom Events from an Analytics Event Tracker Component or from a script.
Your Unity game or app sends Analytics events to a Unity web service. The Analytics system collects the raw events and processes them for display on your project’s Analytics Dashboard. If the computer or device running the application cannot connect to the web service, Unity caches the events locally until the connection becomes available.
Note: If you have a Unity Pro subscription, you can download the raw event data directly. You can import this raw data into your own analytics tools and perform ad-hoc analyses that may not be supported by the Unity Analytics Dashboard.
Standard Events are a form of Custom Event. The difference is that Standard Events are standardized. Each Standard Event has a predefined event name and a set of required parameters. Standardization provides several benefits:
Because of these benefits, you should use Standard Events rather than Custom Events whenever possible. Only use Custom Events when no Standard Event is appropriate.
2018–03–02 Page published with no editorial review
2018–06–04 - Service compatible with Unity 5.2 onwards at this date but version compatibility may be subject to change
New feature in 5.2
2018–06–04 - Demographics event removed