What is new
We've expanded our Analytics API export functionality with four new endpoints, so you can pull more Userlane data into your BI tool (Power BI, Tableau, Looker, etc.) and combine it with data you collect in other systems.
The four new endpoints are:
- Tags API: per-user, per-day interaction counts on tagged elements in your 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, you can now build a complete picture of how users engage with your application and how they feel about it.
How to find it
The new endpoints are documented in our 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 in the Help Center and to see examples of what our endpoints return, see:
- Export HEART, NPS, Surveys, and Tags data via API
- Export Guides, Guide progress and Announcement data via API
What you can build with it
By combining these APIs with your own user data (role, region, department, licence type), you can build segment-level dashboards that answer questions like:
- Which features are most used by which departments?
- Are promoters using a different set of features than detractors?
- Who are my biggest promoters?
- Who was using X feature the most?
- Is satisfaction improving in segments where adoption is growing?
BI Dashboard example you can build using the API export data:
Userlane provides the engagement and sentiment data; segment attributes come from your own user system, joined on the user ID we return in every response.
ℹ️ All endpoints return a user ID. To enrich the data with user attributes such as role or region, join the responses with your own user system using the applicationUserId field, or use our Enduser API for Userlane-side attributes.
