New in Umami Cloud: Error Tracking, Search Console, and Revenue Integrations

Today we're rolling out a set of new features to Umami Cloud.

A few weeks ago we wrote about where Umami is heading: connecting acquisition, behavior, conversion, and revenue so you can answer more questions in one place. This update is a big step in that direction. You can now see the errors your visitors run into, the Google searches that brought them to your site, and the revenue they generate, alongside the analytics you already use.

Error tracking

Umami can now capture JavaScript errors from your website and group them into issues.

To turn it on, add data-errors="true" to your existing tracking script:

<script
  defer
  src="https://cloud.umami.is/script.js"
  data-website-id="your-website-id"
  data-errors="true"
></script>

Uncaught errors and unhandled promise rejections are captured automatically. To report an exception your code has already caught, call umami.captureException:

try {
  await submitOrder();
} catch (error) {
  umami.captureException(error, { tags: { feature: 'checkout' } });
}

Errors appear on a new Errors page under Monitoring. Each issue shows its occurrence count, the number of affected visits, and when it was first and last seen. You can search issues, filter them by status, browser, page path, release, and environment, and mark them as resolved or ignored as you work through them.

Because errors are collected by the same script as the rest of your analytics, each occurrence is linked to the visit where it happened. From an issue, you can open the session to see what the visitor did before the error, or watch the session replay if one was recorded. Seeing the error and the visitor's actions together often makes it much easier to find the cause.

Two optional attributes, data-release and data-environment, label errors with the version of your site and where it's running. This makes it easy to tell whether an issue started with a particular deploy.

Error tracking follows the same privacy approach as the rest of Umami. Collected URLs exclude query strings and fragments, and common patterns such as email addresses, tokens, and credentials are redacted before anything is sent. You can also remove application-specific data with your beforeSend hook. Stack traces are currently shown as the browser reports them; source map support is not available yet.

Google Search Console

You can now connect Google Search Console and see your search performance inside Umami.

A new Searches page under Traffic shows clicks, impressions, click-through rate, and average position for your website, broken down by query, page, country, and device. You can see which search terms people use to find you and which pages they land on, then follow those visitors through the rest of your analytics.

Search data is read from Google when you view it and is never stored by Umami. Google's data typically lags by two to three days and covers the past sixteen months.

Search Console is available on all paid Umami Cloud plans.

Revenue from your payment provider

Umami Cloud can now import payments and refunds directly from your payment provider. Supported providers are:

• Stripe
• Paddle
• Polar
• Dodo Payments
• WooCommerce
• Lemon Squeezy

Once connected, payments sync every hour and appear in your revenue reports. Refunds are imported too, so your numbers reflect what you actually kept, not only what was charged.

To connect revenue to the visitors who generated it, add the ID you pass to umami.identify() to the payment's metadata under the key umami_distinct_id. In Paddle this goes in the custom data. Umami then links each payment to that visitor's journey, so you can see which campaigns, referrers, and pages led to real revenue. Lemon Squeezy doesn't expose checkout custom data through its API, so Lemon Squeezy payments are imported without that link.

You can add several connections per provider and label each one as live or sandbox. Credentials are encrypted when stored.

A new home for integrations

All of these connections are managed from one place: Settings → Integrations. From there you can add a payment provider, connect Google Search Console with your Google account, choose which Search Console property belongs to each website, and disconnect at any time.

Thank you

Thank you to everyone who has been asking for these features and sharing feedback along the way. If you have questions or ideas, we'd love to hear from you.

Log in to Umami Cloud to try the new features today.