Traffic and traffic sources for every WordPress site you manage
Visitors, page views, sessions and traffic sources 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.
Updated
What is cookieless analytics for WordPress?
Cookieless analytics counts visitors, page views and traffic sources without storing a cookie or any personal data in the visitor's browser, so the count does not depend on a visitor accepting cookies. It answers how much traffic a site got, which is usually the question a client asks.
WPCentrify counts traffic this way on every WordPress site you connect and reports visitors, page views, sessions and traffic sources for each site and across all of them, with bots and your own team filtered out. It is built to sit alongside Google Analytics, and can line its figures up with a Google Analytics export day by day. To check traffic without any tool, see our guide on how to check website traffic on WordPress.
WPCentrify traffic analytics at a glance
- No cookies set and no personal data stored.
- Visitors, page views, sessions and traffic sources grouped into channels.
- Crawlers, monitoring tools and your own team filtered out.
- Per site and across every site, with days in each site's own time zone.
- Counted by the connector already installed, with no second plugin.
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, which is what we found fixing cookie consent across thirty sites. 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 on the site itself, in the visitor's own browser. There are no cookies and nothing for a visitor to consent to. For the tools that do set them, cookie consent across every site is handled from the same dashboard. We explain the approach, and why the figures differ from Google Analytics, in WordPress traffic analytics you can actually trust.
Counted on the site, not in a third party
Counting happens on your own site rather than through a third party's script, so the visits an ad blocker or a declined consent banner removes from Google Analytics are still counted here. It keeps working on cached pages, which plain server logs miss.
Machines and staff filtered out
Crawlers, monitoring tools, prefetches, automated browsers and our own checks are excluded, and so is your own team once you add your office or client addresses. The totals of what was removed are shown next to the totals that were kept, so you can see the bot traffic filtering working.
No cookie, no personal data
No cookie is set and no personal data is stored, so there is nothing to disclose in a banner and nothing to ask a visitor to accept. Privacy-friendly analytics for WordPress by construction rather than by configuration.
Rolled up per site and across the fleet
The same numbers appear on a single website and aggregated across every site you are authorized to see, over 7, 30 or 90 days, with days bounded by that site's own time zone.
What you get
Visitors, page views and sessions
All three per site, over your chosen window, defined the same way Google Analytics defines them. A pause of thirty minutes starts a new session, which is the rule Google Analytics uses.
Where visitors came from
Website traffic sources grouped into channels: Direct, Organic search, Organic social, Referral, Email, Paid search, Paid social, Display and Affiliate, with the busiest individual sources and campaigns. What those visits produced arrives separately, as contact form submissions from every site.
Distinct visitors
How many different browsers came across a whole period, each counted once rather than summed day by day. Shown as an estimate.
Compare with Google Analytics
Paste a Google Analytics export and see, day by day, where the two agree and why they differ. A Google Analytics alternative for WordPress that is built to sit alongside it, not replace it.
A definition behind every number
Every figure links through to a plain definition of what it counts, written so a client can read it without a call.
Fleet-wide totals
Every connected site aggregated into one view, filterable down to a single website when a client asks about theirs specifically. That view is the same maintenance dashboard the rest of the portfolio is run from.
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, read against the content record of what exists in the first place.
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 and no consent banner dependency, which is what makes this privacy-friendly analytics for WordPress rather than analytics you have to configure into being private.
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 figures correctly
Visitors are the different browsers that loaded a page on a given day. Somebody who comes back tomorrow counts again tomorrow, so adding up a month of daily visitor figures gives you visits, not people.
When the question is "how many different people came this month", use Distinct visitors. It counts each browser once across the whole period rather than once per day, and it is labeled as an estimate because that is what it is.
The daily figure usually reads higher than a cookie-based tool's monthly unique users and lower than its page views. It is consistent with itself over time, which is what makes the trend meaningful. Where you need the two reconciled, paste a Google Analytics export in and the difference is shown day by day. A sudden dip in the trend is worth checking against uptime for that site before you look for a marketing explanation.
Worth knowing
- Distinct visitors over a period is shown as an estimate
- Built to work alongside Google Analytics, not to replace a full analytics suite
- Traffic sources and campaigns are reported; funnels and conversion tracking are not
- 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. No cookies are set and no personal data is stored, so there is nothing to disclose in a consent banner and nothing for a visitor to accept.
It is built to work alongside Google Analytics rather than replace it. Use this for the operational picture across every site and for the traffic section of a client report, keep Google Analytics for deeper marketing analysis, and use the comparison to explain any gap between the two.
Because the two count different things. Ad blockers and declined consent banners stop Google Analytics and do not stop us, so our page views are usually a little higher. We also count a visitor once per day and forget them overnight, while Google Analytics remembers them for far longer, so compare day by day or use Distinct visitors. Paste a Google Analytics export in and the comparison is shown for you.
No measurable amount. Counting happens in the visitor's browser and is designed to stay out of the way of the page, and it keeps working on cached pages.
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.
Yes. Website traffic sources are grouped into channels such as Direct, Organic search, Organic social, Referral and Email, with the busiest individual sources and campaigns listed alongside them.
Yes. Visitors on cached pages are counted, which is exactly the case plain server logs miss, and no cache exclusion rules are needed.
Yes. Cookieless analytics counts page views and visitors without storing anything in the visitor's browser. WPCentrify counts traffic this way on every connected site, with no cookie set and no personal data stored.
WPCentrify shows visitors, page views, sessions and traffic sources for every connected site in one view, and narrows to a single site when a client asks about theirs.
It depends on whether you need marketing funnels or a clear count. For a count of visitors, page views and sources on every site you manage, WPCentrify counts traffic without cookies or personal data and sits alongside Google Analytics rather than replacing it.
Answer a traffic question without opening another dashboard
Visitors, page views, sessions and traffic sources 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.