What is Ottertrail
Ottertrail collects data about your websites, apps, and servers, and shows it in one dashboard. It is for small software teams that want one tool in place of several.
What it does
Section titled “What it does”| Area | What you get |
|---|---|
| Web analytics | Pageviews, visitors, visits, referrers, campaign (UTM) tags, countries, devices, page speed (Web Vitals), and heatmaps of clicks and scroll depth. |
| Product analytics | Custom events, a funnel, a retention report, and goals. |
| Users | The activity of each signed-in user that your app names. |
| Errors | Browser errors and server exceptions, grouped, with source maps for minified code. |
| Session replay | A recording of the moments before an error, masked in the visitor’s browser. |
| Monitoring | Traces, logs, and metrics from your servers over OpenTelemetry, with services, database queries, and hosts. |
| Uptime and alerts | HTTP checks, and alert rules that send email or signed webhooks. |
How it collects data
Section titled “How it collects data”- From browsers. A small script, the tracker, runs on your pages. It sends pageviews, custom events, errors, and Web Vitals to your Ottertrail instance, and, when you turn heatmaps on, clicks and scroll depth. The tracker stores nothing on the visitor’s device: no cookies and no local storage.
- From your servers. Your servers send events, source maps, and OpenTelemetry data with the project’s secret key. Any OpenTelemetry SDK or Collector can send to Ottertrail. You do not install an Ottertrail agent.
How it treats visitors
Section titled “How it treats visitors”- Ottertrail does not store or log visitors’ IP addresses. It uses the address in memory to find the visitor’s country, region, and city, and then discards it.
- An anonymous visitor gets an ID that changes every day. Ottertrail cannot connect one visitor’s visits on two different days.
- Your app can name its signed-in users. Ottertrail then links their events by your own user ID. See Name signed-in users.
One instance for each customer
Section titled “One instance for each customer”Each customer runs an instance of Ottertrail of their own. No other customer shares its server or its data. You can run an instance on your own server: see Install Ottertrail.
An instance holds your projects and your team. See How an instance is organised.
Where to go next
Section titled “Where to go next”- Set it up. Get started lists the steps, from installing an instance to data in the dashboard. It also has a prompt that gives the same steps to a coding agent.
- Find your way in the dashboard. Read The dashboard.
- Send data from your app. The tracker reference lists every option. Send telemetry covers your servers.
- Run your instance. The Self-hosting pages cover the settings, updates, backups, and security.