Track custom events and see every occurrence

Custom events let you record moments that matter in your own product, such as a plan upgrade or an export finishing. You define each event once in Releaseo, send it from your code, and then review every occurrence. The same events can also trigger Slack and Discord notifications.

In the dashboard, custom events live on the Notification triggers page. Releaseo calls each custom event a trigger there.

Define an event

1. Open Notification triggers in the sidebar.

2. In the Notification trigger catalog, select Create trigger.

3. Fill in the form:

   • Trigger key: the name your code sends. It cannot be changed after you create it.

   • Title: a readable name, for example "Release note opened".

   • Trigger type: pick from the list. These options come from Static data > Trigger types.

   • Trigger category: optional. Choose "No category" to skip it.

   • Description: optional.

4. Under Payload fields, add the data your event carries. Each field has a Field key, a Label, a Type, an optional Description, and a Required switch. The available types are String, Number, Boolean, Date, and JSON.

5. Select Create.

If Create trigger is disabled, you either lack permission to manage events or there is no active option under Static data > Trigger types.

Send the event from your code

The create and edit form shows a Trigger snippet with your key and fields filled in as you type. It looks like this:

releaseo.track('plan_upgraded', {
  // your payload fields
});

To copy it later, open the row's actions menu and choose Copy trigger snippet.

Read the catalog

The catalog table shows these columns: Title, Trigger key, Trigger type, Status, Unique sources, Trigger runs, and Last triggered.

• Unique sources counts distinct users or sessions that sent the event.

• Trigger runs counts how many times it was tracked.

An event is Active, Inactive, or Archived. Use Set inactive or Set active from the row's actions menu to pause an event, Edit to change it, and Archive to retire it. Archiving asks for confirmation. An archived event stays visible in history but should no longer be used.

Open the Event Profile

Choose View profile from a row's actions menu. The page describes itself as "Every occurrence of this event: source, page, and attributes." It has:

• Filters: a time period picker and a segment selector. The segment list only includes published user segments. If a segment is based on behavior, a short note shows when its membership was last refreshed, so counts can lag slightly behind the picker.

• Total occurrences: the number of times the event was tracked.

• Unique sources: distinct users or sessions.

• Occurrences: a table with Occurrence, Time, User, and Page. Scroll to the bottom to load more.

Select any row to open Occurrence details, which shows the source (email, user ID, session) and the event's Attributes.

Analytics keep up to 180 days of history. If your chosen period reaches further back, the page tells you it is showing the last 180 days.

If no one has sent the event yet, you see "No occurrences yet". Check that the key in your code matches the Trigger key exactly.

Send notifications for an event

Open the row's actions menu and choose Notifications to send the event to Slack or Discord. The article "Send Slack and Discord notifications with Notification triggers" covers the dialog in detail.

Troubleshooting

• No occurrences appear. Confirm the key matches your code exactly, and the time period and segment filters are not hiding data.