> 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/changelog/2026/expanded-analytics-api-tasks-endpoints.md).

# Expanded Analytics API: Tasks endpoints

Two new Tasks API endpoints for aggregated task data and step-level action events.

*22 June 2026*

## What is new

The Tasks API has been added to the Analytics API export functionality, making it possible to pull task adoption data into a BI tool (Power BI, Tableau, Looker, etc.) and combine it with data collected in other systems.

The Tasks API has two endpoints, serving two levels of detail:

* **Aggregated Tasks API:** Per-user, per-day starts, completions, and time to complete, across all tasks in a property. Use it to track completion rates over time and spot tasks with high drop-off.
* **Task Actions API:** The raw, step-by-step action event stream for a single task. Use it to see exactly which step within a task users complete or abandon, for funnel and friction analysis.

<div data-with-frame="true"><figure><img src="https://290240774-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUt7Gm0hAq4YBDq7JbHIf%2Fuploads%2FkUmuD7imOdHZllWDFfoS%2Fimage.png?alt=media&amp;token=33046624-bb60-4ed6-b6e3-17998e2cc1ac" alt=""><figcaption></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="https://290240774-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUt7Gm0hAq4YBDq7JbHIf%2Fuploads%2FSSv2ItqPU1lGnh7k2Z2I%2Fimage.png?alt=media&amp;token=0d183db1-9298-4744-9a91-90da1a0a9c3b" alt=""><figcaption></figcaption></figure></div>

The typical workflow is to start with the aggregated endpoint to find the tasks worth investigating, then use the actions endpoint to understand where users drop off inside a specific task.

Combined with the existing HEART, NPS, Surveys, Tags, Guides, Guide Progress, and Announcements APIs, this provides a complete picture of how users move through and complete key tasks in an application.

<figure><img src="https://290240774-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUt7Gm0hAq4YBDq7JbHIf%2Fuploads%2FH02tFjK32lom7wFuGgLW%2Fimage.png?alt=media&amp;token=4b37d1b9-46ff-483b-945f-14929dbc353a" alt=""><figcaption></figcaption></figure>

## How to find it

The new endpoints are documented in the developer reference:

* [Getting started with the Tasks API](/developer-reference/export-heart-nps-survey-tag-and-task-data-via-api.md)

For setup guidance and to see examples of what the endpoints return, see:

* [Export HEART, NPS, Surveys, and Tags data via API](/developer-reference/export-heart-nps-survey-tag-and-task-data-via-api.md)

## What to build with it

By combining the Tasks API with user data from other systems (role, region, department, licence type), segment-level dashboards can answer questions like:

* Which tasks have the highest drop-off, and at which step?
* Are certain departments or roles completing onboarding tasks faster than others?
* Did a task redesign actually improve completion rates?
* How long does it take users to complete key setup tasks, and is that improving over time?
* Which tasks are started often but rarely finished?

{% hint style="info" %}
Both endpoints return a user ID. To enrich the data with user attributes such as role or region, join the responses with the source user system using the `applicationUserId` field, or use the Enduser API for Userlane-side attributes. Task and action names are not included in the response; export them from the Userlane Portal and join on `taskId` and `actionId`.
{% endhint %}

{% hint style="info" %}
Task data is available from 8 July onwards. Each request can cover a date range of up to 30 days.
{% endhint %}


---

# 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/changelog/2026/expanded-analytics-api-tasks-endpoints.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.