Standard Events
Discover predefined events you can use to track key player actions and game lifecycle events.
Read time 2 minutesLast updated 9 months ago
Standard Events are events that are ready to use without the need for instrumentation or developer configuration. Unity Analytics SDK sends some of these events automatically, but you need to populate and record others manually at an appropriate point in your game's lifecycle. These are used by out-of-the-box dashboards and in the Data Explorer.
Standard events are triggered when players perform key actions. You can find out things like: How engaged are your players? What are your best performing countries? Which audiences are underperforming?
The available standard events are:
Event Name | Description | Trigger type |
|---|---|---|
| Record information about the channel that the user was acquired from. This event should be populated with the information available from the attribution provider's SDK. | Requires manual triggering. For information about how to record this event, see the attribution support tutorial. |
| Recorded at the start of a session. A new session starts when the user launches an app and when the user ID changes. | Automatic. |
| Recorded at the start of a session if the user ID is different from the previous session. A new session starts when the user launches an app and when the user ID changes. | Automatic. |
| Recorded at the start of a session. A new session starts when the user launches an app and when the user ID changes. | Automatic. |
| Recorded at the start of a session. A new session starts when the user launches an app and when the user ID changes. | Automatic. |
| Recorded periodically when the app is running to detect session activity. | Automatically every 60 seconds, if no other events have been recorded since the last check. |
| Recorded when a player exits the game. | Automatic. Note that if the operating system does not give sufficient time for the game to shut down gracefully, this event may not be recorded, or may be cached to local storage and only uploaded if the game is started again later. |
| Recorded when a player opt outs of data collection. | Manually by calling |
| Available to be recorded manually when a player has been shown an ad within the game. | Requires manual triggering. For information about how to record this event, see the record Ad Impression events tutorial. |
| Recorded when a player makes an in-app purchase and tracks the purchase amount. Transaction validation can be done via the Unity IAP. | Requires manual triggering. For information about how to record this event, see the record transaction events tutorial. |
| Recorded when a player makes an unsuccessful in-app purchase transaction. Successful transactions are tracked by the | Requires manual triggering. For information about how to record this event, see the record transaction events tutorial. |