Traffic for every WordPress site you manage, on one screen
Visitors and pageviews per site and across the whole portfolio, counted on the site itself without setting a cookie, and reported over 7, 30 or 90 days in each site’s own time zone.
Available now in early access. Included on every plan.
Analytics that lives somewhere else, thirty times over
Every site has analytics. That is not the problem. The problem is that answering "how did the site do last month" means finding the right property, in the right account, for the right client, and doing it again for the next site. At thirty sites the question stops getting asked.
The second problem is consent. A cookie-based analytics tag is gated behind a banner, so the numbers you report are already a subset of reality, and a subset that varies by how the banner was worded. For a maintenance report you usually want the simpler thing: how much traffic this site actually got.
What this is for
- Answering a client question without opening their analytics
- Seeing which sites in the portfolio are growing and which are flat
- Knowing which pages on a site actually receive traffic
- Reporting traffic alongside uptime rather than in a separate tool
- Having a number that is not shaped by a consent banner
Counted on the site, without a cookie
Counting happens in the connector on each page request, so it does not depend on a visitor’s browser running a script or accepting anything.
Counted where the request lands
The connector counts on the WordPress request itself rather than from a tag in the page, so an ad blocker, a script that fails to load or a declined banner does not silently remove the visit.
Machines and staff filtered out
Admin, AJAX, cron, REST and CLI requests, feeds, robots and sitemaps, previews, 404s, prefetches, bots and headless browsers are all excluded. So are logged-in users who can edit posts, because your own team browsing a site is not audience traffic.
Identity that is not a cookie
A unique visitor is a short non-reversible hash of IP, user agent, the date and a per-site salt. No cookie is set, no personal data is retained, and the salt rotates every day.
Rolled up per site and across the fleet
The same numbers appear on a single website and aggregated across every site you are authorised to see, over 7, 30 or 90 days, with days bounded by that site’s own time zone.
What you get
Visitors and pageviews
Both metrics per site, over your chosen window, with the trend rather than a single number.
Fleet-wide totals
Every connected site aggregated into one view, filterable down to a single website when a client asks about theirs specifically.
Per-page breakdown
Which pages and posts actually receive traffic on a site, so a content conversation starts from data rather than from what someone assumes is popular.
Site-local days
A day boundary follows the site’s own time zone, so a store in Sydney and a studio in Denver both get days that match their trading, not the server’s.
No cookie, no PII
Nothing is stored that identifies a person. There is no cookie to disclose, no consent banner dependency, and no cross-day identifier retained.
No second plugin
This rides the connector that is already installed. There is nothing extra to install, license or keep updated on the site.
Read the visitor figure correctly
Because the visitor hash re-salts every day, the same person visiting on three days is three different hashes. A multi-day visitor total is therefore a sum of daily uniques, not a deduplicated count of distinct people. Over a month, a loyal returning reader counts more than once.
That is a deliberate trade. True cross-day deduplication requires keeping a stable per-person identifier, which is exactly what a cookieless design refuses to do. The dashboard says so rather than implying a number the data cannot support.
The practical consequence is that this figure will usually read higher than a cookie-based tool’s monthly unique users, and lower than its pageviews. It is consistent with itself over time, which is what makes the trend meaningful, but it is not interchangeable with a Google Analytics number.
Worth knowing
- Multi-day visitors is a sum of daily uniques, by design
- Not a drop-in replacement for a full analytics suite
- No referrer, campaign, funnel or conversion tracking
- Regular logged-in members count; users who can edit posts do not
- A site’s history can be reset if you need a clean baseline
Related
Questions about traffic analytics
No. A unique visitor is identified by a non-reversible hash of IP, user agent, the date and a per-site salt, deduplicated on the site. Nothing is written to the visitor’s browser and no personal data is retained.
For maintenance reporting and portfolio overview, usually yes. For marketing analysis, no. There is no referrer, campaign, funnel or conversion tracking here. Many people run both: this for the operational picture across every site, a full analytics suite on the sites where marketing decisions get made.
Two reasons. Counting happens on the site rather than in the browser, so visits that a blocked or declined tag would miss are included. And because the identifier rotates daily, a multi-day visitor figure sums daily uniques rather than deduplicating people across the period.
No measurable amount. The count is a small write on a request WordPress is already serving, and the connector adds nothing to the rendered page.
Ordinary logged-in members such as subscribers and customers do count, because they are genuinely audience. Users who can edit posts do not, because that is your team working on the site.
Answer a traffic question without opening another dashboard
Visitors and pageviews for every connected site, counted without cookies and reported next to the rest of the operational picture.
Free during early access. No credit card required.