See the traffic. Know the site is up.

WebTrackNext counts page views, referrers, campaigns, and events on domains you control, then checks uptime and SSL from our server. One public script. No private secret in the page.

Start tracking How it works

Public key only
No raw IP stored
One-minute live window
Reports in Asia/Kolkata

Sample overview

Page views Visitors

Illustrative chart. Your dashboard uses the events collected for your sites.

A count you run yourself

A large analytics suite is built for audiences, ads, and modeled users. WebTrackNext is the observed visit: which page, which source, which device, and whether the site answered.

The script on your site

Paste one tag. The browser receives a public site key. Events from another origin are refused.

The reports in your workspace

Pages, countries, devices, referrers, campaigns, and custom events. A single site uses its timezone. All sites use Asia/Kolkata.

The checks our server makes

HTTPS probes, incidents, certificate days, and response time. A down site cannot report itself through the visitor script.

What we collect

Page path, referrer origin, and campaign tags
Device type, browser, and operating system
Country when the host sends an edge header
Visitor and session ids hashed with a per-site salt
HTTPS status, response time, and certificate expiry

What we do not collect

Raw IP addresses
Search queries from the referrer
A private secret inside the browser script
A profile that follows someone across your other sites

You can honor Do Not Track, and you can skip a path or an IP address. Read the privacy notes.

Who it is for

Site owners

People who want visitors, sources, and live traffic on one page, without a report builder.

A portfolio

One workspace for every domain you register. Switch the site from the top bar, or read them together.

A later plugin

The same public key can be loaded by a WordPress connector. Server keys exist for that plugin and are shown once.

How a visit is counted

The script sends a page view, then a heartbeat. A new session starts after 30 minutes of quiet. A repeated event id is stored once. Known bots are dropped before the row is written.

How live traffic works

A visitor stays in the live count for one minute after the latest event. The overview and the live screen refresh every ten seconds. A quiet site shows zero, which is the point of a short window.

How uptime is separate

Our server requests the registered URL about every five minutes. HTTP answers below 400 count as up. An incident opens on failure and closes when the site answers again.