Event browser

In this article

On the Data Health page, the Event browser (platform-ca | platform-eu | platform-au) tab enables you to monitor the performance and health of your data by tracking the latest events sent to the database. It’s especially useful for when you want to focus on specific validation criteria affecting your data health.

The Event browser tab shows a list of the latest event types, regardless of their status. It indicates which event types passed the validation criteria and also the ones that have missing or incorrectly formatted information inside individual events.


The Event browser doesn’t detect errors associated to whole sessions or inconsistencies between events. For example, it won’t be possible to see if a click event is associated to a search event that doesn’t exist.

Event browser features

On the Data Health (platform-ca | platform-eu | platform-au) page, select the Event browser tab.

Event browser

Click any event listed in the browser. You can then do the following:

1 Use the date picker to narrow down the events by period.

2 Filter events by selecting the checkboxes under Status, Event type, Search hub, and Event source.

3 Filter events by client ID or visit ID by clicking the filter icon next to the desired ID.

4 Remove an ID filter by clicking the X icon.

5 Expand an event that’s marked as Invalid for more details by clicking the arrow.

6 Assess the error code and reason for the invalid event.

7 Open the Visit Browser page containing that specific event by clicking Show in visit browser.

8 View the complete event content on a new dialog by clicking Show event content.

Event source vs Event type

The Event source is the source of the event and helps refine what form the event type takes. It indicates where the event is originating from, such as Custom (UA), View (UA), Search (UA), Click (UA), and Collect.

The Event type section has a number of categories depending on the use case, such as detail, cardAdd, transaction, search, custom, and more. There are overlaps between events types, since one event type can originate from different event sources, except for the Collect event source, which contain specific event types such as detail, cardAdd, transaction, and pageview.