Web analytics · Cloud & on-premise

Session replay with console and network logs

Replay, browser logs and heatmaps in one tool, with session data ready for your AI agents through MCP. Personal and financial data is masked on the user's device.

  • Websites and PWAs
  • Our cloud or your servers
  • Ready for AI agents (MCP)
  • GDPR-ready
uxTrace session replay: the user's sessions, the recording and the event list

AI agents · MCP

Early access

Session data, ready for your AI agents

The uxTrace MCP server gives AI agents structured access to sessions, errors and user behaviour. Ask in plain language and get answers with links to the sessions.

  • Search sessionsBy user, URL, device, custom event or period.
  • Find abnormal sessionsRage clicks, console errors, failed requests and other problems.
  • Read a session timelineActions, events, console and network as structured data.
  • Summarize errors and requestsTop errors, failing endpoints and affected users.
  • Page stats and heatmapsSessions and clicks for any page and period.
AI agent · connected to uxTrace MCP
Why couldn't users save the form yesterday?
uxTrace · search sessionserrors on /forms, last 24 hours → 37 sessions
uxTrace · read session timeline3rd click on Save → POST /api/forms/save · 500
37 sessions failed with a 500 on POST /api/forms/save after the third click on Save. The console shows TypeError reading 'id'. Most affected: Chrome on Android.
Example conversation
Cloud modelsClaude, ChatGPT and other MCP-compatible assistants connect to uxTrace in our cloud or on your server.
Local modelsQwen and other open models run next to on-premise uxTrace. No data leaves your network.

Agents see only what uxTrace stores: masked fields stay masked. AI agents and MCP

Problem

A user reports a problem. Nobody can reproduce it.

  1. Day 1
    User

    "I clicked Save and nothing happened."

    The description is vague.

  2. Day 2
    Support

    "Please send a screenshot and your browser."

    Nobody knows what was on screen.

  3. Day 3
    Engineering

    "No errors in the server logs."

    The error happened in the browser.

  4. Day 5
    Ticket closed

    "Cannot reproduce."

    The problem is still there.

Today
days of back-and-forth
With session replay
one minute to watch the session

Product

One session, five data layers, one timeline

Recording, actions, custom events, console and network share one timeline. Jump to the moment of the error and see every layer at once.

Recording1x–8x, pauses skipped
screen recording
Actionsclicks, input, scroll
Eventsyour custom events
Consolewarn, error
Network2xx–5xx, no response
8:06 — the error appears in the video and the technical data at once
RecordingThird click on Save — the form doesn't close
Eventform_save_attempt · attempt 3
ConsoleTypeError: Cannot read properties of undefined (reading 'id')
NetworkPOST /api/forms/save · 500 · 312 ms

Market

Full diagnostics and full control of your data

Most teams choose between depth and data control. uxTrace gives both.

Session recording tools compared
CapabilityMass-market session recordingCloud services with logsuxTrace
Replay of user actionsYesYesYes
Browser console and network requestsNoYesYes
Cloud or your own infrastructureNoNoYes
Record only the users you needAll trafficAll trafficBy rules

Deployment

Our cloud or your infrastructure

uxTrace Cloud

  • Add one script tag and start the same day.
  • We handle hosting, updates and operations.
  • Sessions kept 90 days by default, adjustable to your policies.
Cloud

Your infrastructure · on‑premise

  • User data never leaves your infrastructure. We have no access.
  • Kubernetes, Docker or VM image, with your domain and certificates.
  • Runs without internet access on a corporate network.
  • Basic deployment in one business day.
On-premise

Same product and SDK. Move on-premise later without changing the integration.

Security

Sensitive data stays masked

  • Masking on the deviceAccount details, amounts, ID documents and contacts are replaced before data leaves the browser.
  • Sampling and country limitsRecord 0–100% of traffic, include or exclude countries, stop collection with one switch.
  • Always and Never recordRules by User ID or Device ID give the security team control over what is stored.
Security details

Use case · Internal support

From support ticket to root cause in five steps

An employee can't complete an operation in the corporate portal.

  1. Report. The employee tells support the form won't save.
  2. Find. Support opens their sessions by User ID, covered by an Always record rule.
  3. Watch. The recording shows three clicks on Save.
  4. Diagnose. The console shows an error; the network log shows a 500 response.
  5. Hand over. Engineering gets the replay and the technical cause.

Get started

Book a 30-minute demo

We'll show uxTrace on a demo environment and discuss a pilot for your team.