Event catalog

Rename, recolor, and exclude events in Cohortum. Switch between Project and Personal scope to control what your whole team sees.

The Events screen lists every event name Cohortum found in your loaded sources. This is where you turn raw event names into a vocabulary your team recognizes, before you build a chart: give them readable names, pick colors, and hide the junk. You're looking at the current project, with events rolled up from every source loaded into it. Switch projects and you get a different catalog.

Come here when your analyses are full of cryptic names like page_pagination_clicked, or when debug and internal events are cluttering your Steps, Journey, Transitions, and Clusters views. Clean the catalog once and every visualization picks it up.

Event catalog columns

Each row is one distinct event name in the project. The header shows the total count — for example, Events — 142 events. Here's what each column tells you:

Every header sorts — click once for ascending, again for descending. To narrow things down, use the All / Active / Excluded pill filters and the search box, which matches both the original and display names.

Count, First seen, and Last seen always cover all the data in the project. The analysis filters you set elsewhere don't touch these numbers.

Rename an event

Raw event names are rarely fit to show anyone. Rename one and the new label shows up everywhere — chart legends, side-panels, insights.

An italic display name means the event is still riding on its original name — you haven't renamed it yet. Give it a custom label and it switches to solid text. The Original name never changes, so you can always trace a display name back to the raw data.

Activate or exclude events

Not every event belongs in your analyses. Debug pings, internal health checks, and sheer high-volume noise can bury the behavior you actually care about. Excluding an event drops it from every visualization and count but keeps it in the catalog, so you can bring it back whenever you want.

To toggle a single event, click its Status badge — Active flips to Excluded and back. Excluded rows are grayed out, so you can spot them at a glance.

To change a bunch at once, tick their checkboxes. A bulk action button shows up:

• Exclude (N) — hides the selected events when they're currently active.
• Activate (N) — restores the selected events when they're all excluded.

New loads mark every event they discover Active by default. That means a later upload can quietly resurrect a name you excluded before, as a fresh Active event. If you're relying on exclusions to keep noise out, re-check the catalog after big uploads.

Set an event color

A consistent color keeps an event recognizable as your eye jumps between the Steps chart, the Transitions graph, and the Clusters view. Click any row's color swatch to open the picker. Pick from the palette, or type a custom #RRGGBB hex value and click Set.

Project scope vs. Personal scope

Your edits can land for the whole team or just for you. If you have edit rights, a toggle sits below the header:

• Project — edits affect everyone in this project. This is the shared, canonical catalog, and keeping it tidy keeps analyses consistent across your team.
• Personal — edits affect only what you see. Reach for this to override a name, color, or status for your own workflow without touching what teammates see.

Personal overrides sit on top of the project defaults. Say the Project scope renames an event but you never renamed it yourself: in Personal scope you'll still see the Project's name. Personal shows only your own overrides, layered on the Project defaults.

Reset your personal overrides

Drifted too far from the shared catalog? You can snap everything back. In Personal scope, click the reset button (the circular-arrow icon next to search) to open Reset all events to project defaults. Confirm and every personal override you have in this project — name, color, and status — returns to the project defaults. Nobody else is affected. The button stays disabled when you have no overrides to clear.

Next steps