Everything VisitWatch does, on every plan.

Pick a metric and the chart below follows it. Under the chart, four breakdowns open in place — pages, sources, countries and devices — so the answer to "which page" is on the same screen as the number that prompted it.

Sessions arrive as they happen rather than on a refresh. The globe is drawn from the city resolved for the request; no coordinate is stored against a visitor.

Three questions about the same set of paths, so they sit on one report instead of three. Open a module and it goes from four rows to the full list without leaving the page.

Channels are the grouping — search, social, referral, direct — so a hundred referrer rows become five lines you can act on. Hostnames matter once a site has a blog on a subdomain and you need to know which one earned the visit.

The split between who visited and who converted is the useful one, and it is easy to lose when the two live on different screens. Here they are columns on one row.

Comparison is not a switch you have to remember. Change the range and the comparison moves with it, because a number with nothing behind it is not yet a result.

The window is in the URL, so a link to what you are looking at is a link to what you are looking at. Day boundaries follow the site's own reporting timezone, not the server's.

No extra instrumentation: a step is a path or an event that is already arriving. Each step shows how many reached it, what share that is, and the drop since the step before, with the worst one marked.

A drop-off rate says a step is losing people. This says which people, which is the difference between a number and something you can change.

The grid is the detail and the curve is the shape. Read across a row for one week's visitors, or down a column to compare the same week of life across cohorts.

An average is a blend of people who behave nothing alike. A segment is defined in one place and then applies to the reports you already know, rather than becoming a separate screen to learn.

An event is a name and nothing else by default. Nothing about the person is attached to it, because there is no identity layer here to attach anything to.

One goal per site, on purpose. A page with six conversion rates on it is a page nobody reads; a single rate, carried onto every breakdown, is one you can compare across sources and countries.

Sessions are counted with a key derived from the request and rotated daily. Nobody is asked to agree to something in order to be counted, because nothing was stored on them in the first place.

It is built from the same definition the tracker is, so it cannot drift from what actually happens — a field you switch on moves from never to pending to yes on that screen. Against each one it says what the field is for, including the ones that are never sent.

The country and, where the request carries it, the region and city are resolved at that moment. No coordinate is kept, and the address itself does not reach the database.

A visit ends at your domain. That is a property of what is collected rather than a setting somebody could turn off, which is why it is in the field list rather than in a policy.

Your numbers leave the way they came in. There is no export tier and no request to make; the control is on the report itself.

A side project costs nothing extra to watch, which is the point: the decision to add a site should be about whether you want the numbers, not about the bill.

Per-seat pricing ends with one person screenshotting a dashboard into a channel every Monday. Nobody is kept out of a report to save money.

The definition sits under the list of members rather than in documentation, because a role name four hundred pixels from its meaning is a role name nobody checks.

Settings shows whether the tracker is reporting and when the last event arrived, so installing it is something you can confirm rather than something you hope worked.

It is the same list the sidebar shows, reachable in two keystrokes from wherever you are.

A laptop that goes dark at sunset takes the app with it. The choice is yours rather than the workspace's, so it is stored in your browser and not against your account.