Not all events are equal. Some events represent actual product usage—actions actively taken by your users. Others are automatically triggered events, typically sent in the background without direct user interaction. These are often a result of a process or system running as intended.

System events (sometimes called "backend events" or "non-transactional events") are automatically generated to reflect something happening, but not necessarily something the user did. For example:

While these events are useful for ensuring processes run correctly, they don't represent active user engagement with your product.

Including system events in analytics can inflate user activity metrics and make it harder to identify meaningful engagement. For example, seeing a "digest sent" doesn’t tell you whether someone actively opened or interacted with your app.

June allows you to exclude system events in just one click. Instead of removing events manually or filtering them every time, you can mark an event as not user-triggered to exclude it automatically from "Any event" filters.

That’s it!

June will now exclude this event from "Any event" filters or metrics, ensuring your analytics focus on real user activity.

The "Last Seen" trait is a default computed trait in June that tracks the most recent activity for a user.

By default, this trait includes all events. When you untoggle system events in the "User Triggered" column, you update the last seen computed trait to remove these events too.

Here are some common examples of system events in popular SaaS tools:

By marking system events as not user-triggered, you keep your analytics clean and focused on user engagement. June makes it easy to exclude these events with one click, ensuring accurate insights into how people actually use your product.