# RUM actions

An action corresponds to a user activity such as a click, a tap, a scroll etc. From the observability perspective, an action has quite a few important properties that can provide insights into users' behaviour patterns. They also inherit properties from the active parent view.

## Action.id

Unique identifier for every action.

### Usage

Distinguish actions, even ones with the same name

### Example

`f58b24dd-d781-47be-ad6c-0f89af469e46`

## Action.name

Concatenation of the user activity and the UI element (target) it was performed on. Many distinct actions may have the same name e.g., a user clicking the same button twice or two different users clicking on the same button in separate sessions.

### Usage

Group actions by name to see the count of the most frequently performed action.

### Example

Click **Trace Analytics**

## Action.loading_time

The loading time of the action. It is calculated from the time the user interacts with a UI target to the time that the page has no more activity.

### Usage

Filter actions that have loading times in a certain time range, or perform percentile analytics to profile the slowest or critical ones.

### Example

165 ms

## Action.long_task.count

Any browser task that blocks the main thread for more than 50ms is a `long_task`.

### Usage

Filter actions that have `long_task.count` in a certain range.

### Example

2

## Action.resource.count

A resource event is triggered for a resource fetch such as images, XHR, Fetch, CSS, or JS libraries loaded on a webpage.

### Usage

Get the median (percentile 50) count of resource fetches per action.

### Example

10

## Action.error_count

UI error emitted by the browser.

### Usage

Get the actions with the most errors to isolate workflows and steps that lead to frequent errors.

### Example

0