Skip to content
Try the admin demo 0

Admin module

Analytics that needs no consent

Every other module in ModularPress helps you publish something. This one tells you whether anybody read it — counted on your own server, without a cookie, without an IP address and without a third party in the middle.

No cookie

Nothing is stored in the visitor's browser, so the cookie banner has nothing to ask about. The numbers are the same whether someone accepts or refuses.

No IP address

There is no column for one. A visitor is recognised within a single day by a hash made with that day's random key, and the key is deleted when the day ends.

No one else

The count is written to your database by your server. No request leaves for anyone, so there is nothing to put in a data processing agreement.

The whole module is one screen

Three numbers, a chart, and the lists underneath. Pick a period and read it. Click a screenshot to see it full size.

Analytics screen with page views, unique visitors, average per day and a bar chart by day.
Page views, visitors unique per day and the average, over 7, 30, 90 or 365 days, with a bar for every day of the period.

Which pages people actually read

The Pages table is ordered by views and shows the visitors for each address next to them, so a page read once by fifty people is easy to tell from one read fifty times by one. Every row links to the page itself.

This is the list that tells you which of your posts earn their place and which categories nobody opens.

Where the visits come from

Referrers are grouped into direct, search engines, social networks and other sites, with the host beside each one. It is enough to see whether an article was picked up somewhere, without following anyone around the web.

What is broken

Every address that answered 404 is listed with how often it was asked for and when it last happened — and each one links straight to the Redirects module, where you turn it into a redirect in two fields.

A 404 list nobody acts on is decoration. This one is a work queue.

Devices, browsers and languages

Mobile against desktop, the browsers in use, and which language version people read. On a site that serves more than one language, that last one decides where the next translation effort goes.

How it counts, exactly

The hit is recorded after the page has been sent, so the visitor never waits for it. Bots are not counted, and neither is anything that is not an ordinary page request.

A payment link is stored without its token, so the address /pay/… appears in the list without becoming a way to reach somebody's order. Raw rows are deleted after 400 days, automatically, without a scheduled job to forget about.

If you would rather not count at all, one setting stops it. Nothing else in the panel changes.

Analytics tables: pages by views, where visits come from, devices, browsers and languages.
The lists under the chart: pages with views and visitors, where the visits came from, and the split by device, browser and language.