Skip to content
UmamiEngine logoUmamiEngine
Features Pricing Comparison FAQ
For Shopify Sellers For Bloggers For WordPress
Blog Tools About Log in Start free
Log inStart free

Umami v3.5: Browser Error Tracking, Improved Session Replays and Major Security Updates

Updated: November 2026

Privacy-first analytics without the DevOps. Managed Umami from $5/mo — 14 days free, no card required.

Start free trial

Umami v3.5.0 is now available, bringing a substantial set of new features and improvements to the open-source web analytics platform.

This release introduces built-in browser error tracking, improved session replay navigation, expanded reporting and tracking configuration, API updates, major security improvements, and numerous bug fixes.

Whether you use Umami to understand website traffic or to debug application behavior, version 3.5 makes the platform considerably more capable.

1. Browser Error Tracking

One of the most significant additions in Umami v3.5 is built-in browser error tracking.

Instead of relying on a separate error-monitoring service, Umami can now capture JavaScript errors that occur in visitors' browsers and present them alongside your analytics data.

Automatic capture of uncaught errors

Umami v3.5 can automatically capture uncaught JavaScript exceptions and unhandled promise rejections. Enable this by adding data-errors="true" to your tracking script.

Captured errors are grouped into issues with stack traces, occurrence counts, and associated session information. Issues can be resolved, ignored, or reopened.

Manually capturing handled errors

Not every application error results in an uncaught exception.

Modern applications frequently use try/catch blocks and promise rejection handlers to recover from errors gracefully. While this is good application design, it also means that some errors would otherwise go unnoticed by automatic error capture.

Umami v3.5 addresses this with the new umami.captureException() method.

Developers can use this method to explicitly report handled exceptions, allowing important application errors to be tracked even when the application successfully catches them.

This is particularly useful for monitoring failed API requests, application-specific exceptions, and other problems handled by custom error-handling logic.

2. Improved Session Replays and Navigation

Session replays are another area receiving attention in Umami v3.5.

Understanding what visitors do on a website is important, but navigating recordings efficiently becomes increasingly important as the number of sessions grows.

Previous and next replay navigation

Users can now navigate between session replays using dedicated previous and next controls.

Keyboard shortcuts are also supported:

  • Left arrow: Previous replay.
  • Right arrow: Next replay.

These small improvements make reviewing multiple recordings faster and reduce the need to repeatedly return to the replay list.

Distinct visitor identification

Visitor identification in replay lists has also been improved.

Umami v3.5 introduces distinct visitor IDs in replay lists, making it easier to distinguish visitors when reviewing recorded sessions.

Additional navigation improvements

The website switcher now makes team websites available even when users are outside a team context.

Mobile navigation has also been improved with direct dashboard access.

Together, these changes make the application easier to navigate, particularly for users managing multiple websites and reviewing analytics on different devices.

3. Improved Tracking Configuration and Preferences

Umami v3.5 introduces additional flexibility in how the tracker and session recorder are configured.

Centralized configuration with window.umamiConfig

The tracker and recorder can now be configured through window.umamiConfig.

This provides a centralized way to configure tracking behavior without relying exclusively on individual script attributes.

An important detail is that script attributes take precedence over the corresponding configuration settings.

This allows developers to maintain general configuration centrally while still overriding individual settings when necessary.

Client-provided session salts

Another important addition concerns session salt management.

Umami v3.5 introduces support for optional client-provided session salts.

Client-provided salts can be used with hourly, daily, weekly, or monthly rotation intervals.

This functionality requires server-side enablement through the ENABLE_CLIENT_SALT configuration option.

The server-side SALT_ROTATION configuration has also been expanded to support additional options, including fixed salts.

These changes give administrators more control over how tracking identifiers are generated and rotated.

For self-hosted installations, it is important to review the server-side configuration before relying on these options.

Trusted proxy configuration

The new TRUSTED_PROXIES configuration option improves client IP detection when Umami operates behind multiple proxies.

This is particularly relevant for deployments using reverse proxies, load balancers, and other intermediate network infrastructure.

Correct proxy configuration helps ensure that Umami identifies visitor IP addresses using the appropriate forwarded information.

12-hour and 24-hour clock preferences

The application also introduces a clock preference supporting both 12-hour and 24-hour formats.

This is a relatively small usability improvement, but it makes the interface more adaptable to different user preferences.

4. Reporting and Dashboard Improvements

Umami v3.5 includes several reporting enhancements designed to make analytics data easier to explore and compare.

Zoom into chart date ranges

Users can now click a bar in a website chart to zoom directly into its corresponding date range.

This makes it easier to investigate specific periods without manually configuring a new date selection.

Improved custom date selection

Custom date selection has been redesigned around a single two-month calendar.

This simplifies selecting date ranges, particularly when comparing periods that span multiple months.

Better comparisons of ongoing periods

One particularly useful improvement concerns comparisons involving incomplete reporting periods.

Umami v3.5 can compare an ongoing period against the equivalent elapsed portion of the previous period.

For example, when reviewing an ongoing reporting period, comparisons can use the same elapsed portion of the preceding period rather than comparing incomplete data against an entire previous period.

This provides a more meaningful basis for evaluating current performance.

More accurate comparison charts

Comparison charts have received improvements covering:

  • Chart alignment.
  • Timezone handling.
  • Daylight-saving transitions.

These changes help avoid inconsistencies when comparing analytics data across different periods and timezones.

Retention reporting improvements

Retention reports now use cell shading relative to the highest visible value.

This makes differences between retention cohorts easier to recognize visually.

Additional reporting information

The release also introduces:

  • Session referrers in Session Overview.
  • Active visitor indicators in the realtime log.
  • Faster attribution queries.
  • Faster funnel queries.
  • Faster paginated queries.

These changes improve both the usability and responsiveness of the analytics experience.

5. Security Improvements

Security is another major focus of Umami v3.5.

The release includes several changes that affect administrator authentication, team permissions, sharing, and API access.

Mandatory administrator password change

Fresh installations using the seeded administrator account must change the initial administrator password before continuing.

This helps prevent installations from remaining accessible with a default administrator password.

Stronger two-factor authentication enforcement

Two-factor authentication enrollment is now enforced on the server.

The verification process has also been hardened against concurrent attempts and reuse of authentication codes.

These changes strengthen authentication beyond interface-level restrictions.

Improved shared dashboard security

Umami v3.5 revalidates share tokens against current sharing settings.

Consequently, deleting a share or changing its permissions takes effect when the token is checked again.

Board shares have also been restricted from exposing sensitive underlying information, including:

  • Raw event data.
  • Session data.
  • Revenue information.
  • Realtime activity data.

This provides better separation between sharing dashboard insights and exposing the underlying analytics information.

Additional security hardening

The release also tightens:

  • Team permission checks.
  • Password update handling.
  • API key route validation.
  • Link destination validation.
  • Collection input validation.

These changes collectively improve the security of self-hosted and team-based Umami deployments.

6. Performance, Reliability and Bug Fixes

Beyond the headline features, Umami v3.5 addresses a considerable number of issues affecting tracking, reporting, and application reliability.

Tracking and session management

Several improvements address problems involving:

  • Session resets.
  • Identity attribution.
  • Concurrent anonymous-session claims.
  • Redis-backed login sessions expiring during active use.

These changes are particularly relevant for websites with frequent visitor activity and deployments using Redis-backed authentication sessions.

Cache consistency

The release fixes stale website, link, and pixel caches following updates or deletions.

This helps ensure that changes made in the application are reflected correctly without outdated cached information interfering with the interface.

Performance measurement

Performance measurement has been improved for background tabs and prerendered pages.

These scenarios can complicate browser performance measurements, so handling them more reliably improves the quality of collected performance information.

Heatmaps and replay improvements

Additional fixes address:

  • Heatmap overlays in Safari.
  • Snapshot sizing.
  • Tracking inside preview frames.

These changes improve compatibility and consistency across different browser environments.

Reporting and filtering fixes

The release also fixes several reporting-related problems, including:

  • Retention cohort dates.
  • Full-month navigation.
  • Invalid custom date selections.
  • Search text being overwritten by delayed navigation.
  • Custom wildcard selections.
  • Missing values in negative filters.

Other fixes cover board ownership when transferring websites, Docker and Podman server binding, translations, accessibility, and responsive layouts.

Although these changes may not be immediately visible to every user, they contribute to a more reliable analytics platform.

7. API and Developer Updates

Developers integrating Umami with external applications and services will also benefit from the v3.5 API changes.

Optional period parameters

Analytics endpoints now support optional period parameters, including:

  • today
  • 24h
  • 7d
  • 30d

This provides a more convenient way to request analytics data for common reporting periods.

Visit identifiers in event responses

Website event responses now include visitId.

This provides additional context for integrations that need to associate events with individual visits.

New error tracking endpoints

The release introduces new API endpoints for error tracking.

API client types have also been refreshed to reflect the updated functionality.

MCP tool improvements

Event-filter handling in MCP tools has been corrected.

This is particularly relevant for developers and AI-assisted workflows that interact with Umami through its Model Context Protocol integration.

8. Important Upgrade Requirements

Before upgrading an existing Umami installation to v3.5, administrators should review several compatibility and configuration changes.

Requirement Details
APP_SECRET Must now be explicitly configured
Node.js Version 20.19 or newer required
Recommended Node.js Node.js 22 LTS
Database migration PostgreSQL migration 27_add_error_tracking
Administrator security Seeded administrator password must be changed
Password settings Now located under Settings → Security
Public configuration API /api/config has been removed

Explicit APP_SECRET configuration

One of the most important changes is that Umami no longer supports falling back to DATABASE_URL when APP_SECRET is missing.

Administrators must explicitly configure APP_SECRET.

Make sure this environment variable is present in your deployment configuration before upgrading.

Node.js compatibility

Umami v3.5 requires Node.js 20.19 or newer.

Node.js 22 LTS is recommended.

Check your deployment environment, Docker configuration, or build pipeline to ensure that the required version is available.

Database migration

This release includes the PostgreSQL migration:

27_add_error_tracking

Administrators should account for database migration requirements when planning their upgrade.

Make sure you have a valid database backup before performing the update.

Removed public configuration endpoint

The public /api/config endpoint has been removed.

If you have external integrations or custom scripts relying on this endpoint, review them before upgrading.

9. Who Should Upgrade to Umami v3.5?

Independent developers and small website owners

Browser error tracking is particularly valuable for developers who want to monitor website behavior without maintaining separate analytics and error-monitoring tools.

SaaS developers

The ability to capture handled and unhandled JavaScript errors, inspect stack traces, and associate issues with sessions provides useful debugging context for web applications.

Agencies managing multiple websites

Improved website navigation, session replays, reporting, and team permissions make the platform more practical for managing multiple properties.

Self-hosted Umami administrators

The expanded configuration options and security improvements are valuable, although administrators should pay particular attention to the new environment requirements and migration changes.

10. Frequently Asked Questions About Umami v3.5

What is new in Umami v3.5?

Umami v3.5 introduces native browser error tracking, improved session replay navigation, expanded tracking configuration, reporting enhancements, security improvements, API updates, and numerous bug fixes.

Does Umami v3.5 support JavaScript error tracking?

Yes. It can automatically capture uncaught JavaScript exceptions and unhandled promise rejections using data-errors="true". Developers can also capture handled exceptions through umami.captureException().

Can Umami group JavaScript errors?

Yes. Captured errors are grouped into issues with stack traces, occurrence counts, and associated session information. Issues can be resolved, ignored, or reopened.

Does Umami v3.5 improve session replays?

Yes. It introduces previous and next replay navigation, left and right keyboard shortcuts, and distinct visitor IDs in replay lists.

What Node.js version does Umami v3.5 require?

Node.js 20.19 or newer is required. Node.js 22 LTS is recommended.

Do I need to configure APP_SECRET when upgrading?

Yes. APP_SECRET must now be explicitly configured. Umami v3.5 no longer falls back to DATABASE_URL when APP_SECRET is missing.

Does Umami v3.5 require a database migration?

Yes. The release includes the PostgreSQL migration 27_add_error_tracking. Administrators should account for this migration and maintain a database backup before upgrading.

Is Umami v3.5 suitable for self-hosted installations?

Yes. The release includes improvements for self-hosted deployments, including additional tracking configuration, security hardening, and bug fixes. However, administrators should check the Node.js requirement, APP_SECRET configuration, and database migration before upgrading.

Conclusion: Umami Is Becoming More Than a Website Analytics Tool

Umami v3.5 is a substantial update that extends the platform beyond traditional website analytics.

Browser error tracking is the standout addition, giving developers a way to investigate JavaScript errors alongside visitor and session information. Combined with improved session replays, reporting, and API functionality, it makes Umami more useful for understanding both website traffic and application behavior.

The security improvements and reliability fixes are equally important, particularly for organizations running their own Umami infrastructure.

If you are already using Umami, v3.5 is worth evaluating, especially if browser error tracking is something you currently handle through a separate service.

For website owners who want to benefit from Umami without managing the underlying server infrastructure, UmamiEngine provides managed Umami hosting, helping you focus on your analytics rather than server maintenance.


Get Started with Managed Umami

Ready to try Umami without the DevOps hassle? UmamiEngine provides fully managed Umami analytics that runs the latest Umami version, including the new features described above such as browser error tracking and improved session replays. No servers, no databases, no maintenance, just privacy-first analytics in minutes. Get started today and take control of your analytics data.

Get fully managed Umami in minutes

Keep reading

  • Umami 3.4: Annotations, MCP & API Updates
  • Umami MCP: Connect Analytics to AI Assistants
  • Umami Heatmaps: Visual Analytics
UmamiEngine logoUmamiEngine

Hosted by Hetzner · Data in Germany/EU

Product

Home For Shopify Sellers For Bloggers For WordPress About

Resources

Blog Tools Self-Hosting Cost Calculator Contact

Legal

Terms of Use Privacy Policy Impressum

© 2026 UmamiEngine. All rights reserved.

$5/mo · 14 days free · No card Start free