Skip to content

Events

/dashboard/<siteId>/events — a master list of every named event on the left, and a detail pane with four tabs on the right.

Only named events appear: types custom, outbound and revenue. A plain pageview has no name and is never here.

Up to 100 events, ranked by volume. Per row:

Column Meaning
Name The exact string you sent
Type custom, outbound or revenue
Events Occurrences in the range
Visitors Distinct visitors who fired it
Per visitor Events ÷ visitors. 3.4 means people repeat it
Δ Percentage change in volume against the previous period
Last seen Most recent occurrence in the range
Sparkline One zero-filled point per bucket

The search box above the list is client-side — it narrows the 100 rows you already have, it does not re-query.

Selecting an event gives a time series (events and visitors per bucket) plus a summary:

Figure Meaning
Events, Visitors Totals in range
Visitor share Percentage of the range’s visitors who fired it at least once
Per visitor Events ÷ visitors
Visits Distinct sessions it occurred in
Median per visit Typical repeats inside one visit — a mean hides the few visits that spam
First seen / Last seen Within the range
Previous, Δ The same four totals over the preceding window

Visitor share deliberately drops the event and property selections from its denominator; measured against itself it would always be 100%.

Who fired the event, by dimension: pages (30 rows), referrers (30), countries (30), devices (8) and browsers (10). Clicking a row adds that filter to the whole screen.

Two columns. On the left, every property key the event carries:

Column Meaning
Key The property name
Events Occurrences carrying it
Values Distinct values seen, across text, number and date columns
Type The dominant stored type
Coverage Share of the event’s occurrences in range that carried the key

For a number key you also get sum, average, min, max and median, and a histogram of equal-width bins when the value list is too long to be useful.

On the right, the values of the selected key, ranked, with the share each holds.

Property data is stored with its own site and timestamp and is never joined back to the event row, which is what makes these queries fast. One consequence: dashboard filters do not narrow the property panels. Coverage is measured against the event’s unfiltered volume in the range.

The raw feed behind the aggregates: every hit of the selected event, newest first, 25 a page. Each row shows the time, the path, the title, the visitor, the referrer, the location, the browser and up to four property chips.

Filters do apply here.

Appears as soon as at least one non-custom event exists.

  • Destination hosts and Links — see Outbound links.
  • Revenue — what the revenue events reported, split by currency, with a link to the Revenue screen. Revenue events in the occurrence feed show their amount. See Revenue events.
  • Create goal — opens the goal dialog prefilled from this event, by navigating to /dashboard/<siteId>/goals?new=event:<name>.
  • Filter dashboard by this event — goes to Overview with event=<name>, so every tile and breakdown reads “for people who fired this”.
Parameter Values Default
range the nine range keys 30d
all 26 filter keys see Filters none
event an event name the busiest event
tab breakdowns, properties, occurrences, links breakdowns
propKey a property key the busiest key
propValue a value of propKey none
page integer ≥ 1 1

tab=links falls back to breakdowns when every event on the site is custom. An unknown propKey falls back to the busiest key.