Tracked Events

Tracked events let you capture behavioral data about your users—for example when they use a feature, view a page, or complete an action. You can use this data to segment users and to trigger feedback at the right moment (e.g. show a survey after a specific event).

Events are created in two ways:

• Automatically when your app or backend sends event data (e.g. via SDK or API), if Allow new events from clients is enabled for the project.
• Manually in the Tracked Events table by clicking Create Event, so you can define events before sending data or use them in segments.

You can view and manage all tracked events for a project under User Data → Tracked Events in the dashboard.

How to track events

Events are sent from your application using the Encatch SDK or API (e.g. a trackEvent-style method). You must identify users with a unique identifier (user ID or email) so that events can be associated with the right user.

Whatever method you use, the event is identified by a slug (e.g. button_click, page_view, form_submit). If that slug does not exist yet and Allow new events from clients is on, a new tracked event is created automatically.

How to use event data

Tracked events are used mainly for segmentation and for triggering feedback.

Segmenting users

When building a data-driven segment, tracked events appear as available data fields. You can group users based on actions they have performed—for example “users who performed feature_used in the last 7 days” or “users who never performed checkout_completed”.

Triggering feedback

You can configure feedback forms to show when a user performs a specific tracked event. Use the targeting and trigger settings for your form to select a Tracked Event as the trigger, so the survey appears right after that action.

Event properties

Each tracked event has:

Allow new events from clients

At the top of the Tracked Events page, Allow new events from clients controls whether new events can be created automatically when event data is sent from your app or API.

• Enabled – Any event slug you send can create a new tracked event if it does not already exist.
• Disabled – Only existing event slugs are recorded; unknown events are ignored. Use this when you want strict control over which events are tracked.

You can still create events manually regardless of this setting.

Managing events

Create an event

1. Go to User Data → Tracked Events for the project.
2. Click Create Event.
3. Enter:
   • Slug – Lowercase, letters, numbers, and underscores only. Must be unique in the project (including deleted events). Examples: button_click, page_view, form_submit.
   • Name – Human-readable label (e.g. "Button Click", "Page View").
4. Click Create.

Rename an event

Edit the Name field in the table and save. The slug (system identifier) does not change.

Usage information

The In Use column shows whether an event is used in segments (e.g. in segment filters). Click the indicator to see which segments reference it. Events that are in use cannot be disabled or deleted until they are removed from those segments.

Disable an event

Use the Pause (disable) action. Disabled events are ignored for new incoming data and are not shown in other parts of the dashboard (e.g. trigger or segment options). Use Play to enable again. Events that are in use in segments cannot be disabled until removed from those segments.

Delete an event

Use the Delete action for events that are not in use. Deleting removes the event from the project; if new data is later sent with the same slug (and new events from clients are allowed), an event with that slug can be created again. Events that are in use cannot be deleted.

Best practices

• Slugs: Use clear, stable slugs (e.g. signup_completed, plan_upgraded). Keep naming consistent between your app and the dashboard.
• Allow new events: Turn Allow new events from clients off if you want to restrict which events are stored and avoid accidental event proliferation.
• Last usage: Use the Last Usage column to spot events that are no longer sent from your app and clean them up or disable them if needed.