> 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.md). # Tasks A defined multi-step process tracked automatically, how it differs from a tag, and when to use one. A Task is a measurement definition. It describes a multi-step workflow in your application, such as "Create a new deal" or "Submit a holiday request", and tracks whether end users complete it. Tasks are invisible: they show nothing on screen and end users never know a task is running. In the background, they send the analytics events that feed the [Task Success](/intelligence/heart/task-success.md) dimension of HEART[^1].
Tasks page in the Userlane portal

The Tasks page shows completion data for every task on the application.

Tasks are authored in the Editor[^2], but the analytics they produce sit in Intelligence. You can also create a task from an existing guide in one step, which makes it easy to add measurement to content you already have. {% content-ref url="/pages/iSW1aAIFYuiVThZ8DMfM" %} [Create a task in the Editor](/intelligence/tasks/create-a-task-in-the-editor.md) {% endcontent-ref %} ## How a task differs from a tag Tasks and [Tags](/intelligence/tags.md) are both invisible measurement tools, but they answer different questions. A task tracks a complete workflow from start to finish and measures whether users get through it. A tag marks a single interaction (one button, one click) and counts how often it happens. If you need to know whether people finish a process, define a task. If you need to know whether people use a specific button or feature, place a tag. ## When to use a task Tasks answer one kind of question: are people completing the workflows that matter? Define one whenever a process has a clear start and end and you need to know what share of users get from one to the other. Common examples: * **Onboarding workflows.** A new hire needs to complete a profile, accept terms, and set preferences. A task on that sequence shows how many new users finish onboarding and where the rest drop off. * **High-value transactions.** Creating a purchase order, submitting an expense claim, or closing a deal in a CRM. These are the processes the application exists to support, and completion rates are the most direct measure of whether people can use it. * **Processes targeted by a guide.** Before you deploy a guide on a workflow, a task on the same sequence captures a starting point. After the guide goes live, the before-and-after comparison in Task Success shows whether the guide made a measurable difference. * **Compliance-sensitive steps.** When a regulated process must be followed in order, a task tracks whether users complete every step rather than skipping to the end. Tasks are not the right tool for everything. Single interactions (did anyone click this button?) are better served by a tag. If the goal is to help someone through a process rather than measure whether they finish it, use a guide. ## Relevant articles * [Tags](/intelligence/tags.md) * [Task Success](/intelligence/heart/task-success.md) * [Efficiency](/intelligence/heart/efficiency.md) * [Creating guides](/assistance/in-app-guidance/creating-guides.md) ## FAQ
What is the difference between a task and a tag? A task tracks a multi-step workflow and measures whether end users complete a defined sequence of actions. A tag tracks a single interaction: one click on one element. Tasks feed the Task Success and Efficiency dimensions of HEART; tags do not feed HEART.
Do tasks show anything to end users? No. Tasks run in the background and send analytics events without showing anything in your application.
How often does task data update? Task data does not update in real time. The dashboard shows aggregated data that is refreshed periodically.
Can a task be created from an existing guide? Yes. The Editor offers a **Create from an existing Guide** option when you create a new task. The guide's steps are converted into task actions. After conversion, the task is independent of the guide.
Do tags feed HEART? No. Tags are standalone. Task Success is calculated from tasks, not tags. The Tasks page in the portal has a toggle to view tag data, but tags do not contribute to HEART.
What happens if no tasks are defined? Task Success shows no score and is marked **Input Needed**. Efficiency, which also depends on task data, is affected the same way. Defining and publishing tasks is the prerequisite for both dimensions to report a score.
[^1]: HEART is Userlane's five-dimension model for scoring how well an application works for the people using it: Happiness, Efficiency, Adoption, Risk, and Task Success. [^2]: The Editor is the workspace where Userlane content is built, separate from the portal where content is targeted and analytics are viewed. --- # 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.md?ask=&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.