--- title: "Events" slug: "events" tags: ["Default Tracking", "Advanced Tracking", "event"] status: "update" updated: 2026-10-19T07:30:21Z published: 2026-10-19T07:30:21Z canonical: "support.whatfix.com/events" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.whatfix.com/llms.txt > Use this file to discover all available pages before exploring further. # Events An event represents an action performed by an end user within your application. Each event includes contextual data that helps you analyze and understand end-user behavior. For example, when an end user clicks **Submit** on a leave request form, that click is an event. You can track events using different methods and analyze them to extract meaningful insights. ### Types of events Whatfix classifies events into two types, based on how they’re captured: - **Guidance events or Default events**: Whatfix captures these events automatically when end users interact with [Whatfix content or widgets](https://support.whatfix.com/docs/creating-whatfix-content). For more information, see [List of Whatfix-related events](/product-analytics/docs/list-of-default-events). - **App events or Custom events**: These events are user-defined and enables you to capture end-user behavior on the application. They include User Actions and events captured using Whatfix API. When you select an element, choose how to track it: - Select **Default tracking** to track the element with the default selector. Default tracking includes historical data. - Select **Advanced tracking** to define custom tracking rules using [**Element Precision Rules**](https://support.whatfix.com/docs/visibility-rules-for-content) and [**Advanced Visibility Rules**](https://support.whatfix.com/docs/understand-advanced-visibility-rules-for-content). Advanced tracking doesn’t include historical data. --- ### Events Section Overview - [**Track an Event**](/product-analytics/docs/user-action): Track specific end-user interactions within your application, even if the user hasn’t interacted with Whatfix content. This enables you to analyze product engagement at a granular level. - [**Event grouping**](/product-analytics/docs/event-group): Combine multiple events into a single logical group to better understand end-user behavior. For example, group the **Flow completed** event with a Custom event that tracks clicks on **Save** to measure how many end users complete a process. - [**Attributes**](/product-analytics/docs/attributes-1): Add contextual information to both Default and Custom events. Attributes help you understand where and how the event occurred. Examples: Page title, URL, and user role. Guidance events include all events triggered when end users interact with Whatfix content or widgets within the application. App events include engagement with User Actions, Autocaptured events (Beta), or events captured using the Whatfix API. Whatfix User Actions enable you to track your end users' actions and behavior on your application