A GOOD START, AND NUMBERS YOU CAN EXPLAIN

Meet your traffic.

Visitor Tracking is free during beta, with unlimited websites and pages. It uses the open-source Umami engine for cookie-free analytics.

Install in a few minutes

Create your account, then open Websites and select Add website.
Give your site a name and enter its domain, such as example.com. You can also paste the full address, such as https://example.com/.
Copy the generated tracking tag into your site’s shared <head>. Install it once per page, including pages rendered by your site’s router.
Visit your published site with a normal browser. Return to the installation panel and select Check installation. Your first visit should appear in Realtime.

You register websites, not individual pages. Every page that loads the tag is recorded automatically, including supported single-page app navigation. Each separate website gets its own tag.

Single-page apps: the default script detects pushState and replaceState navigation. Bare browser Back/Forward (popstate) needs a router integration that reports those pageviews. If you use manual pageviews, disable automatic pageviews and handle every transition consistently to avoid duplicates. Use the same integration in both trackers when comparing.

What the numbers mean

Metric	How it is counted
Visitors	Distinct anonymous identifiers in the selected period. The identifier uses the website, visitor IP, browser user-agent, and a salt that rotates each month. Raw IP addresses are not saved in the analytics database.
Visits	A more granular identifier inside a visitor’s activity. Umami uses an hourly salt and an in-memory cache that expires after 30 minutes; visits can span an hour boundary. It is not a conventional sliding 30-minute cookie session.
Views	Recorded pageview events. Custom events are reported separately.
Bounce rate	The percentage of visits with one matching pageview and no custom event in the selected period. A custom event makes a visit non-bouncing.
Visit duration	The gap between the first and last matching pageview in each visit, averaged across visits. Single-page visits contribute zero; this does not measure time after the last pageview.

Cookie-free visitor numbers are estimates of distinct browser and network combinations, not an exact count of people. Shared networks can merge visitors, while IP or browser changes and the monthly reset can split them.

Compare with Umami fairly

Install both tags on exactly the same pages, at the same time, and let them collect together. Existing Umami history is not imported automatically.
Use identical start and end times, reporting timezone, country exclusions, bot settings, and filters. Start with a completed UTC day wholly within one month.
Compare pageviews first, then visitors, visits, bounce rate, and duration. Unique visitor totals across chart buckets or page rows cannot be added together.
Check a small set of deliberate visits: first load, refresh, another page, browser back/forward, a second browser, and a new visit later.
If the totals differ, compare the browser Network requests to both collection endpoints. Ad blockers, content security policies, failed requests, and different IP geolocation databases can explain differences.

For custom JavaScript events, call window.visitortrack.track('event-name'). When comparing with Umami, call window.umami.track('event-name') separately for the same action. Each tag has its own API, regardless of loading order. Automatic pageviews and data-umami-event attributes are handled by both tags.

Matching the measurement engine reduces differences; it does not guarantee identical delivery or geolocation to Umami Cloud. Location exclusions can be particularly sensitive to the database used by each service.

Filter the traffic that matters

Open a website and select Filter. Choose a field and operator, select one or more values, and apply. For your example, select Country → Is not → Singapore, United States. Use All to match every condition or Any to match at least one. Saved segments let you reuse filters.

Privacy and the beta

The default pageview tag does not set tracking cookies or persist a visitor ID in browser storage. Dashboard sign-in uses browser storage to keep you signed in. Avoid putting personal information in page URLs, event properties, or custom identifiers; those values can be collected if you send them.

Session recording is an optional, separate installation. It is not enabled by the standard tracking tag. Use only the collection features appropriate for your site.

All available features are free during beta. Paid plans are not implemented. There are no application limits on sites or pages; hosting and database capacity still determine the service’s practical limits. Keep your password safe: email verification and self-service password recovery are not yet available.