Event Browser
Use the Event Browser feature in Analytics to debug events coming in from your game. You can access a list of up to 100 of the latest events sent by your game over the last 48 hours.
You can toggle between valid events that are processed successfully and invalid events that are not. This might be due to setting up events in your game incorrectly, such as sending the wrong data type, wrong format, or invalid enumeration values.
Note: Event processing time varies. It can take up to 10 minutes for events to appear in the Event Browser.
You can filter by Event Name, User ID and Unity Player ID:
| Filter | Description |
|---|---|
| Event Name | The name of the event. |
| User ID | Every event must contain a userID, which is a unique string that identifies the player and is consistent across their subsequent play sessions. |
| Unity Player ID | An optional parameter. The authenticated player ID is provided by the Unity Authentication service. This can be useful to link analytics data to player accounts if you're using other Unity services (such as Cloud Save). If you're not using the Unity Authentication service, this field remains blank. |
The list is currently view-only and cannot be exported. Contact support if you require a bulk raw data export.
The Event Browser shows the following information for both valid and invalid events:
| Column | Description |
|---|---|
| Loaded timestamp (UTC) | When the event was received. |
| User ID | The user ID sent by the SDK. |
| Unity Player ID | The authenticated player ID is provided by the Unity Authentication service. If you're not using the Unity Authentication service, this field remains blank. |
| Event Name | The name of the event. |
To view the event payload in the flattened JSON format, select <> at the end of the row.
Note: Nested events (for example, transaction) are flattened (have their nesting removed) by splitting the event into multiple, separate events. These events have the same Main Event ID value, with the parent event having an "eventLevel": 0 in their JSON, and the child events having "eventLevel": 1. Only the parent event contributes towards user metrics.
The Event Browser shows the following information only for valid events:
| Column | Description |
|---|---|
| Main Event ID | The generated ID assigned to the event when it came in. Useful for bulk event uploads; the user can see all events contained in a single bulk event call. |
The Event Browser shows the following information only for invalid events:
| Column | Description |
|---|---|
| Reason | The headline reason for why this event is considered invalid. |
For a detailed breakdown of an invalid event, select the arrow at the end of the row. Notices inform you of errors and warnings. For example, if there is no format on a parameter such as a UUID, you receive an invalid notice.