Platform

A Users page for the people using your product

See every end user your app identifies, with their sessions, errors, requests and MCP activity on one page.

Analyze → Users lists the end users of your product: everyone your SDKs identify, through identify() in the browser or user.id / enduser.id on spans. It is now on for every organization.

  • The directory shows each user’s sessions, errors and requests, when they were last seen, and where their requests come from (web, mobile, API or MCP). Filter to users with errors or with replays, and group users by the group you pass to identify(), such as their company.
  • A user’s page shows their identity, traits and devices, and tabs for activity, session replays, product events and the MCP sessions they ran, merged into one timeline.
  • Issues show how many users an error affected, and a user shows the errors they hit.

Use it to answer a support ticket (“what did this customer see?”) or to check who a bad deploy reached. The same data is available from the /v2/users API and the list_users and inspect_user MCP tools.

See your first trace today.

Add the SDK, point your OTLP exporter at Maple, and traces arrive.

maple.dev: observability on OpenTelemetry