Event Browser
Debug and view your recent events to verify data collection and identify invalid events.
Read time 2 minutesLast updated 19 hours ago
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.
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 |
| 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. |
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. |
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. |
Column | Description |
|---|---|
| Reason | The headline reason for why this event is considered invalid. |