Skip to main content
Each row on Events is one event we received. A row is not an attributed conversion, and it is not a successful ad-platform delivery.

Columns

The table has seven columns, in this order. Select a cell in event, source, page, device, or distinct id to filter on that value.

Find an event

1

Set the range

Select a range in the header. The default is last 24h.
2

Add a filter

Select the event or source chip. Select + filter for the other five.
3

Narrow the window

Select a bar in the volume chart. A time: chip appears. Select Clear zoom to undo it.
4

Open the row

Select the row to expand it. Select the sheet button for the full record.

Date ranges

Filters

The last seven arrive as URL parameters. Overview breakdowns and Live both link into Events using them. The search box filters the rows already loaded in your browser, so use a filter chip to reach an event outside them. Search matches event_name, distinct_id, page_path, geo_city, and utm_campaign.

Loading and totals

Events loads 500 rows at a time. Scroll to load the next 500. The toolbar counter reads <loaded> / <total> events. The total covers the whole range, so it’s larger than the number of rows in the table.

The event record

The expanded row shows event_id, event_name, received_at, distinct_id, user_id, source, url, referrer, browser, os, device, and location. It also shows properties and user_properties as JSON. The full sheet adds utm_source, utm_medium, and utm_campaign. Select copy event to put the whole record on your clipboard. An event with no properties reads no properties.
Never send passwords, access tokens, payment card details, or health information in an event name, a URL, or a property. We store the payload exactly as you send it.

Verify a new event

  1. Open a private browser window.
  2. Perform the action once.
  3. Filter on the exact event name.
  4. Open the row and confirm the properties you sent.

When it does not work

Next, open Users to follow that distinct id across its journey, or Conversions to check whether a rule matched the event.