Custom events explorer

Explore every custom event with completions, unique visitors and conversion rate, pivot event properties, aggregate numeric values, and rename or merge events.

# Custom events explorer

> Explore every custom event with completions, unique visitors and conversion rate, pivot event properties, aggregate numeric values, and rename or merge events.

**Events** lists every custom event name for the range with:

- completions (total times it fired),
- unique visitors and visits with the event,
- conversion rate (visits with the event ÷ all visits),
- first and last seen.

Search the list by name. The same list is available as JSON from the
`events_list` API operation.

## Event detail

Click an event for:

- a chart over time,
- a **property pivot**: choose up to three properties as rows or columns,
- for number properties, the **sum, average, median and p90**,
- the pages where it fired and the sources of visits that fired it.

## Managing events

From Events, or **Site settings → Events & properties**:

| Action | Effect |
|---|---|
| Rename | Shows the event under a new name, for all history (applied at query time) |
| Merge | Combine several names into one (`Sign up` + `signup` → `Signup`) |
| Hide | Hide an event from lists without deleting data |
| Delete | Permanently delete the event **including its history**. Confirm by typing the name |
| Currency override | Treat an event's revenue as a given currency |

## Property settings

Click **Property settings** on the Events page, or **Site settings →
Events & properties → Manage properties**. The page lists the
[property](/docs/events/properties) keys of the site's custom events:

- every key seen in the last 30 days (up to 200), most used first, with
  the number of events that carried it,
- keys you saved a setting for earlier, even when no event carried them
  in the last 30 days.

Each row has three settings and its own **Save** button:

| Setting | Effect |
|---|---|
| **Label** | A display name shown in place of the key in an event's property list and pivot (up to 64 characters). Clear it to show the key again |
| **Hidden** | Leaves the key out of the property list on the [event detail](/docs/dashboard/events#event-detail) page |
| **No personal data** | Confirms the key never holds personal data. Only keys marked this way are included in raw event exports and warehouse syncs |

Labels and hiding are applied when a report is built. Stored data is not
changed, and the key itself stays the same, so filters and the API still
use it as `prop:<key>`.

> **Note:** Row-level data leaves the product without any property you
> haven't marked. To get `plan` into a raw event export (Pro and up) or
> a warehouse sync (Business), tick **No personal data** for `plan`
> first. See [Exports](/docs/reports/exports).

Seeing the page needs `analytics.read`. Changing a setting needs
`sites.manage` (Owner, Admin, Editor). Other members see the labels and
flags without the form.

Free: 10 distinct property keys per site. Paid plans: unlimited. On
Free, keys already in use keep working, and an event that brings an 11th
key is stored without that property. The list of keys in use is rebuilt
every day from the most used keys of the last 30 days, so a key you stop
sending frees its place.

## API

Events are under `/sites/<site id>/events`, with MCP tools named
`events_*` (`events_list`, `events_get`, `events_update`, `events_merge`,
`events_delete`).

Property settings are `GET /sites/<site id>/events/properties` (MCP:
`event_properties_list`, with an optional `event` to list only the keys
seen on one event name) and `PATCH /sites/<site id>/events/properties`
(MCP: `event_properties_update`, with `key`, `display_name`, `hidden` and
`export_safe`).

The [API reference](/docs/api) lists every input.

查看 Markdown

Events lists every custom event name for the range with:

completions (total times it fired),
unique visitors and visits with the event,
conversion rate (visits with the event ÷ all visits),
first and last seen.

Search the list by name. The same list is available as JSON from the events_list API operation.

Event detail#

Click an event for:

a chart over time,
a property pivot: choose up to three properties as rows or columns,
for number properties, the sum, average, median and p90,
the pages where it fired and the sources of visits that fired it.

Managing events#

From Events, or Site settings → Events & properties:

Action	Effect
Rename	Shows the event under a new name, for all history (applied at query time)
Merge	Combine several names into one (`Sign up` + `signup` → `Signup`)
Hide	Hide an event from lists without deleting data
Delete	Permanently delete the event including its history. Confirm by typing the name
Currency override	Treat an event's revenue as a given currency

Property settings#

Click Property settings on the Events page, or Site settings → Events & properties → Manage properties. The page lists the property keys of the site's custom events:

every key seen in the last 30 days (up to 200), most used first, with the number of events that carried it,
keys you saved a setting for earlier, even when no event carried them in the last 30 days.

Each row has three settings and its own Save button:

Setting	Effect
Label	A display name shown in place of the key in an event's property list and pivot (up to 64 characters). Clear it to show the key again
Hidden	Leaves the key out of the property list on the event detail page
No personal data	Confirms the key never holds personal data. Only keys marked this way are included in raw event exports and warehouse syncs

Labels and hiding are applied when a report is built. Stored data is not changed, and the key itself stays the same, so filters and the API still use it as prop:<key>.

Note: Row-level data leaves the product without any property you haven't marked. To get plan into a raw event export (Pro and up) or a warehouse sync (Business), tick No personal data for plan first. See Exports.

Seeing the page needs analytics.read. Changing a setting needs sites.manage (Owner, Admin, Editor). Other members see the labels and flags without the form.

Free: 10 distinct property keys per site. Paid plans: unlimited. On Free, keys already in use keep working, and an event that brings an 11th key is stored without that property. The list of keys in use is rebuilt every day from the most used keys of the last 30 days, so a key you stop sending frees its place.

API#

Events are under /sites/<site id>/events, with MCP tools named events_* (events_list, events_get, events_update, events_merge, events_delete).

Property settings are GET /sites/<site id>/events/properties (MCP: event_properties_list, with an optional event to list only the keys seen on one event name) and PATCH /sites/<site id>/events/properties (MCP: event_properties_update, with key, display_name, hidden and export_safe).

The API reference lists every input.