> 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-guide-progress-tags-nps-and-survey-endpoints.md).

# Expanded Analytics API: Guide progress, Tags, NPS and Survey endpoints

Four new Analytics API endpoints for Tags, NPS, Surveys, and Guide progress data.

*13 May 2026*

## What is new

The Analytics API export functionality now includes four new endpoints, making it possible to pull more Userlane data into a BI tool (Power BI, Tableau, Looker, etc.) and combine it with data collected in other systems.

The four new endpoints are:

* **Tags API:** Per-user, per-day interaction counts on tagged elements in an application. Use it to measure feature adoption, identify power users, and spot adoption gaps.
* **NPS API:** Individual Net Promoter Score responses (score, optional comment, timestamp, user ID). Use it to track sentiment trends and identify promoters and detractors.
* **Surveys API:** Individual responses to custom in-app surveys (score, optional comment, timestamp, user ID). Use it to measure feature-level satisfaction and gather post-task feedback.
* **Guide Progress API:** Per-user completion state for a specific Guide, plus aggregate completion statistics.

Combined with the existing HEART, Guides, and Announcements APIs, this provides a complete picture of how users engage with an application and how they feel about it.

## How to find it

The new endpoints are documented in the developer reference:

* Getting started with the Tags API
* Getting started with the NPS API
* Getting started with the Surveys API
* Getting started with the Guide Progress API

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

* Export HEART, NPS, Surveys, and Tags data via API
* Export Guides, Guide progress and Announcement data via API

## What to build with it

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

* Which features are most used by which departments?
* Are promoters using a different set of features than detractors?
* Who are the biggest promoters?
* Who was using a given feature the most?
* Is satisfaction improving in segments where adoption is growing?

<figure><img src="https://290240774-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUt7Gm0hAq4YBDq7JbHIf%2Fuploads%2F3PvazirFADYW0HpcbgVG%2Fimage.png?alt=media&amp;token=85639ca4-1065-4438-9a32-43b66df47b54" alt=""><figcaption></figcaption></figure>

Userlane provides the engagement and sentiment data; segment attributes come from the customer's own user system, joined on the user ID returned in every response.

{% hint style="info" %}
All 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.
{% 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-guide-progress-tags-nps-and-survey-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.