Web Analytics

Know whether your site is fast. Install nothing.

Every visit to your app passes through the Vertra edge, and that is where we measure it. Open the Analytics tab to see traffic, errors and response times, in one dashboard that works for a quick look and for a deep investigation.

What it is

The question that matters: is my site fast?

Web Analytics answers that first, in plain words, and then shows the rest: how many people visit, where they come from, which pages take too long and where errors appear. The Summary fits in a glance. The details are one click away when you need to find out why.

How it works

Measured on the way in, not inside your app.

Every request to your subdomain or your custom domains goes through our edge network before it reaches the container. That is where the numbers come from.

Measured at the edge

Each request is recorded at the Vertra edge with its country, route, status and timing. The numbers show up in the dashboard a few minutes later.

Edge vs. container

You get two timings side by side: how long the visitor waited and how long your container took to answer. The gap tells you whether the bottleneck is your code or the path to the visitor.

Nothing to install

No script on the page, no SDK, no cookie and no new deploy. Once your web app is published, the Analytics tab already has data.

Features

From the summary down to a single request.

Five tabs, one period bar (from 5 minutes to 30 days, or any range you pick) and filters that apply to everything at once.

Summary

One sentence on how the site is doing and four numbers: visitors, requests, response time and error rate, each with its change over the period.

Summary view: status sentence, visitors, requests, p95 response time and error rate with their change, and the traffic chart with the previous period dashed.

Traffic and cross filters

Countries, routes, referrers, browsers, operating systems, devices, bots and status codes. Click any item and every panel narrows to that slice.

Traffic filtered to Brazil: the filter chip under the period bar, the figures for that slice and the requests-over-time chart.

Errors

Total 5xx, the time series, the routes that fail most and the split by status. Add 4xx when you want them, since bots and scanners make them noisy.

Errors with 4xx included: total, error rate, 5xx and 4xx, and the errors-over-time chart.

Performance by percentile and region

Edge and container at p50, p75, p90, p95, p99 and p99.9, by country and by network region, plus the slowest routes and the ones that concentrate problems.

Performance: edge and app time at p50 and p95, and edge vs. app bars for each percentile.

Requests

One row per request, with route, status, timings and the request ID. IP addresses and URL parameters stay masked until you choose to show them.

Request log with masked IP and URL parameters, plus the status, country, time and cache of each row.

Compare

Turn on comparison and every chart gets a dashed line for the previous period, with the change shown on each number.

Dashboard screens with sample data.

Plans

The Summary on every plan. The details from Pro up.

Every plan shows full traffic, errors, comparison and the response time in the Summary. Detailed performance, the request log and a longer history depend on the plan.

Web Analytics features on each plan
FeatureStarter1–2 GBPro4–8 GBBusiness12–24 GBEnterprise32–512 GB
Summary with response time (p95)
Traffic with every breakdown and cross filters
5xx errors, with optional 4xx
Compare with the previous period
Detailed performance: edge vs. container, percentiles, countries and slow routes
Request log
Queryable history7 days7 days30 days30 days

Each query covers up to 30 days, within your plan's history.

Compare all plans
FAQ

Frequently asked questions

Do I need to install anything in my app?

No. Measurement happens at the Vertra edge, before the request reaches your container. There is no script, SDK, cookie or code change. It covers your app's subdomain and the custom domains connected to it.

Are the numbers exact?

With low traffic, yes. With high traffic, the edge works from a sample: totals are estimated from it and the request list shows part of the requests. The dashboard tells you whenever the numbers on a screen are estimates.

How long until data shows up?

A few minutes. The most recent requests can take a few minutes to reach the charts, and the dashboard reminds you of that when you look at the last few minutes.

What do you store about my visitors?

We store nothing about your visitors; we store your site's totals: requests, visits, data sent, error rate and response time, with no one's IP, visited page or browser. The details are read from the edge on demand, with a cache of a few minutes. IP addresses and URL parameters are masked by default, and the Show data button reveals them on that screen only. Each account sees only its own apps, and inside a workspace the app's read permission applies.

How far back can I look?

7 days on Starter and Pro, 30 days on Business and Enterprise. Within that history you can pick any range, from 5 minutes to 30 days.

What is the difference between edge time and container time?

Edge time is how long the visitor waited before the response started to arrive. Container time is how long your app took to answer. If both go up together, look at your code or your database. If only the edge goes up, the delay is on the way to the visitor.

Web Analytics

Publish your app and see the numbers the same day.

The Analytics tab shows up on every web app, on every plan. No setup.