Custom analytics

Custom analytics

Understanding how a site is doing without tracking people.

The problem

Anyone with a website wants to know if it works: how many people arrive, from where, and whether they then get in touch. The most common tools collect a lot of personal data and force banners and consent requests.

I wanted an alternative inside the CMS that answers the useful questions without storing data about people.

Stock image for the project “Custom analytics”: it does not show the project.

What I built

  1. 01

    Visits without IP addresses

    Page views are counted without storing the IP address or the user agent.

  2. 02

    Estimated visitors

    A hash valid for one day makes it possible to estimate visitors without recognising them on later days.

  3. 03

    Sessions and funnel

    Sessions are reconstructed and you can see the path from visit to contact.

  4. 04

    Search Console and comparison

    Google searches come from Search Console and every figure is compared with the previous period.

  5. 05

    Third-party analytics, only with consent

    For clients who want them, Google Analytics 4 and other tools start only after consent.

  • My role

    Design and development inside base-cms. At Space IT I also migrated a site's statistics from Matomo to Google Analytics 4.

  • Technologies

    Python · Django · ECharts · Search Console · Google Analytics 4

A few carefully chosen measures are enough to decide. Privacy depends on what is not stored, so there is no banner to explain.

What I learned

Statistics for your site

Write to me: I will tell you which numbers you need and how to get them while respecting privacy.

Get in touch

Stock image: page views graph by Joe Sutherland, CC0 (Wikimedia Commons), cropped. It does not show the project.