> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/intelligence/tasks/create-a-task-in-the-editor.md).

# Create a task in the Editor

How to create a task in the Editor, define actions by type, convert a guide into a task, and activate tracking.

This article covers how to create a task from scratch or from an existing guide, define actions using the four action types, and activate the task to start tracking.

{% hint style="info" %}
For what tasks are, how they differ from tags, and when to use each, see [Tasks](/intelligence/tasks.md) in Intelligence.
{% endhint %}

A task is a sequence of actions that maps to a real workflow in the application. Each action represents one step the user takes, and the task tracks whether the sequence is completed. Tasks are built in the Editor[^1] and, once activated, produce analytics on the [Tasks](/intelligence/tasks.md) page in the portal.

## Create a task from scratch

A task needs at least two actions before it can be activated: one in the **Starting Actions** zone and one in the **Completion Action** zone. Between them, the **Actions** zone holds any intermediate steps. Together, these three zones define the path from start to finish.

{% stepper %}
{% step %}

#### Open the Editor and select Tasks

Open the Editor on the application and select **Tasks** in the sidebar.

<div data-with-frame="true"><figure><img src="https://259567114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF6bxg8i3T6U4vZ3k7PHi%2Fuploads%2FtswjCHXHy9tjJH4nDwhd%2Ftasks%20editor.png?alt=media&#x26;token=307abf06-38da-4c31-ac48-b2465e151b59" alt="The Tasks overview in the Editor sidebar"><figcaption><p>The <strong>Tasks</strong> overview in the Editor.</p></figcaption></figure></div>
{% endstep %}

{% step %}

#### Start a new task

Click **Create**. In the **Create Task** dialog, choose **Create from scratch**. Userlane generates a default name with the date and time. Replace it with something descriptive so the task is easier to find later.

<div data-with-frame="true"><figure><img src="https://259567114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF6bxg8i3T6U4vZ3k7PHi%2Fuploads%2FJO5cCjhVFCufxvmXgXcE%2Fcreate%20a%20task.png?alt=media&#x26;token=26d923f9-144f-43c6-a214-0c8db7018b7a" alt="The Create Task dialog with the Create from scratch option"><figcaption><p>The <strong>Create Task</strong> dialog.</p></figcaption></figure></div>
{% endstep %}

{% step %}

#### Record actions

Add actions to each zone. Click **+ Record** to select an element on the page, or **+ Page Action** to match a URL pattern. Each action you record is placed in the zone where you clicked the button.
{% endstep %}

{% step %}

#### Set the action type for each action

Use the dropdown on each action card to set its type. The four types are described in [Action types](#action-types) below.
{% endstep %}

{% step %}

#### Configure page scoping

By default, a task tracks everywhere its action selectors match. To limit tracking to specific pages, open the **Choose Where the Task Is Tracked** dropdown and select a page rule[^2] instead of **Everywhere**. Page rules are created and managed in the portal, and the **Go to Page Rules** link opens that view directly.

Tasks support page-based scoping only. User-based or audience-based scoping is not available.
{% endstep %}

{% step %}

#### Activate tracking

Click **Activate Tracking** at the bottom of the editing panel. The task becomes public and actions begin producing analytics events.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
The task is activated and tracking. Data appears on the Tasks page in the portal after the next refresh.
{% endhint %}

## Action types

Each action has one type, set from the dropdown on the action card. The type determines what triggers the action at runtime.

<div align="left" data-with-frame="true"><figure><img src="https://259567114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF6bxg8i3T6U4vZ3k7PHi%2Fuploads%2F5EbUfV5WqsKiz7dFvKVW%2Ftask%20detail.png?alt=media&#x26;token=59f9348d-d9c6-4382-8f60-800714166608" alt="An action card with the action type dropdown open" width="280"><figcaption><p>Setting the action type on an action card.</p></figcaption></figure></div>

<table><thead><tr><th width="129.567626953125">Type</th><th>Fires when</th><th>Best for</th></tr></thead><tbody><tr><td><strong>Click</strong></td><td>The user clicks the target element</td><td>Button presses, link clicks, menu selections</td></tr><tr><td><strong>Input</strong></td><td>The user types into the target field and leaves it (blur with a non-empty value)</td><td>Form milestones, without recording what was typed</td></tr><tr><td><strong>Page load</strong></td><td>The browser URL matches the configured pattern</td><td>Starting or ending on a specific page</td></tr><tr><td><strong>Element</strong></td><td>The target element appears on the page (in the page's live structure, the DOM)</td><td>User interface state changes with no direct user action</td></tr></tbody></table>

**Click**, **Input**, and **Element** actions each store a selector[^3] that identifies the target element. When you record one of these actions, the Editor opens a visual picker: hover over the application and click the element you want. If the element sits inside a dropdown or modal that closes on click, use the pause button to freeze the picker, open the dropdown or modal, then resume and select.

Page actions work differently. Instead of an element, a page action stores a URL pattern. Enter the pattern when you add the action. Wildcards are supported, so `*/orders/*` matches any page whose address contains `/orders/`.

## Create a task from a guide

When a guide already covers the workflow you want to measure, you can create a task from it in one step instead of recording from scratch. The guide's steps are converted into task actions automatically, and the resulting task is independent: editing or deleting the source guide has no effect on the task.

{% stepper %}
{% step %}

#### Start the conversion

There are two entry points. From the **Tasks** overview in the Editor, click **Create** and choose **Create from an existing Guide**. Or, from the **Guides** overview, open the three-dot menu on any guide row and select **Create Task**. All guides are eligible regardless of their status.
{% endstep %}

{% step %}

#### Review the converted actions

The conversion maps eligible guide steps to task actions: click steps become **Click** actions, input steps become **Input** actions, and next-button steps become **Element** actions. First steps (intro), last steps (closing), hover steps, and specific-value input steps are skipped because they do not represent discrete workflow actions.

Conversion produces no page actions. If the workflow needs one, add it manually.
{% endstep %}

{% step %}

#### Activate

The converted task starts as private. Review the actions, add any missing ones, then click **Activate Tracking** to start.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
A conversion that produces fewer than two actions cannot be activated. Add actions manually to meet the minimum.
{% endhint %}

## Deactivate or delete

To stop tracking, open the task and click **Deactivate Tracking**. The task returns to private. Historical data is preserved and remains visible on the Tasks page in the portal.

Deleting a task removes it from the Editor entirely. Historical analytics remain accessible in the portal, but you can no longer edit or reactivate the task.

## Relevant articles

{% content-ref url="/pages/nJSkeXwSmCTopscQ7Fmx" %}
[Tasks](/intelligence/tasks.md)
{% endcontent-ref %}

{% content-ref url="/pages/v7SOlgVUQT5Cd3NHaTih" %}
[Task Success](/intelligence/heart/task-success.md)
{% endcontent-ref %}

{% content-ref url="/pages/DbuU3EtVubYDfoPt5F6W" %}
[Create a tag in the Editor](/intelligence/tags/create-a-tag-in-the-editor.md)
{% endcontent-ref %}

{% content-ref url="/pages/1S0Ysrf45iMPMs4rp5yk" %}
[Creating guides](/assistance/in-app-guidance/creating-guides.md)
{% endcontent-ref %}

## FAQ

<details>

<summary>What action types can a task use?</summary>

**Click**, **Input**, **Page load**, and **Element**. Each action has exactly one type, set from the dropdown on the action card.

</details>

<details>

<summary>Can a task be created from a guide?</summary>

Yes. The guide's steps convert to actions automatically. The task is independent after conversion, so editing the guide does not change the task.

</details>

<details>

<summary>Which guide steps are skipped during conversion?</summary>

First steps (intro), last steps (closing), hover steps, and specific-value input steps. These do not map to discrete workflow actions.

</details>

<details>

<summary>Can tasks be scoped to specific users?</summary>

No. Tasks support page rules only. User-based or audience-based scoping is not available.

</details>

<details>

<summary>What happens when a task is deactivated?</summary>

Tracking stops. Historical data is preserved on the Tasks page in the portal. The task returns to private and can be reactivated.

</details>

<details>

<summary>How many actions does a task need?</summary>

At least two: one in the **Starting Actions** zone and one in the **Completion Action** zone.

</details>

[^1]: The Editor is the workspace where Userlane content is built, separate from the portal where content is targeted and analytics are viewed.

[^2]: A page rule is a URL-based rule that defines a set of pages. Page rules are created in the portal and can be applied to tasks, tags, and other content types to control where they are active.

[^3]: A selector is the rule Userlane uses to find an element on the page. If the application changes, the selector may need refining so it still matches.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.userlane.com/intelligence/tasks/create-a-task-in-the-editor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.