Track Page view count and last visited timestamp

1.7.1 2024-02-22 10:14 UTC


Release Downloads Build Status Coverage Status Maintainability Twitter

Track Page view count and last visited timestamp

Commercial Usage

Support open source!

This plugin is free but if you use it in a commercial project please consider to sponsor me or make a donation.
If my work helped you to make some cash it seems fair to me that I might get a little reward as well, right?

Be kind. Share a little. Thanks.

‐ Bruno
Github sponsor Patreon Buy Me a Coffee Paypal dontation Hire me


  • unzip as folder site/plugins/kirby3-pageviewcounter or
  • git submodule add site/plugins/kirby3-pageviewcounter or
  • composer require bnomei/kirby3-pageviewcounter


Echo the tracking a 1px x 1px-image or adding css anywhere in your template. Both techniques will increment the counter but technically they track in a different way.

A) via image, tracking scroll below first fold

<?php echo $page->counterImage(); ?>

B) via css, tracking mouse hover on body

<?php echo $page->counterCss(); ?>

How it works

The tracking image will be moved below the fold and trigger the counter with native lazy loading on first user scroll. Why? To avoid most of the bots. It will also work for cached pages using the pages cache (even when cached static).

SQLite database (default)

To view the tracked count and timestamp this plugin provides two optional fields.

in your page blueprint

    label: Page view count
    type: viewcount
    label: Page last visited
    type: lastvisited
    # format: 'DD-MM-YYYY'

Kirby has day.js built in which you can use to format your date output.

You do not have to add anything to you config files. But you could make some changes to the defaults, like the path to the sqlite file if you wanted to.


return [
    /* default 
    'bnomei.pageviewcounter.counter' => function () {
        return new \Bnomei\PageViewCounterSQLite();
    'bnomei.pageviewcounter.sqlite.file' => function () {
        $dir = realpath(kirby()->roots()->accounts() . '/../');
        return $dir . '/pageviewcounter.sqlite';
    // other options ...

Page Fields (alternative)

If you do not want to store your tracked counts in a sqlite file then add kirby text or hidden fields to your blueprint. I usually have blueprints for them and extend them in my target pages blueprints. like this...


type: number
min: 0
default: 0
disabled: true
label: Visit Count


type: hidden

in your page blueprint

    extends: fields/viewcount
    extends: fields/lastvisited


return [ 
    'bnomei.pageviewcounter.field.count' => 'viewcount',
    'bnomei.pageviewcounter.field.timestamp' => 'lastvisited',
    'bnomei.pageviewcounter.counter' => function () {
            return new \Bnomei\PageViewCounterField();
    // other options ...

NOTE: Be warned that Page Fields might not work well for concurrent requests.


bnomei.pageviewcounter. Default Description
field.counter fn() callback. returns instance of sqlite or field counter class
field.ignore-panel-users true boolean. if true will not increment count if session is by a panel user.
field.sqlite.file fn() callback. returns filepath to sqlite file
field.field.count viewcount string. name of field in page blueprint
field.field.timestamp lastvisited string. name of field in page blueprint
botDetection.CrawlerDetect true check for crawlers (~10ms)
botDetection.DeviceDetector true check for bots (~40ms)


This plugin is provided "as is" with no guarantee. Use it at your own risk and always test it yourself before using it in a production environment. If you find any issues, please create a new issue.



It is discouraged to use this plugin in any project that promotes racism, sexism, homophobia, animal abuse, violence or any other form of hate speech.