Month: February 2018

Simple, private, self-hosted, cookie free website day...maybe

More thoughts on HOW to track

There seems to be a few possible ways to do the tracking and I think it broadly falls into two categories: use JavaScript to send a request request a resource (image, CSS) using an HTML tag or a CSS property I talked before about the fact that requesting a resource wouldn’t send the details of…
Read more

Thoughts on WHAT to track and report

I’ve been thinking about not just HOW to track, but WHAT to track. And these are related. My tracking method will, to some extent, dictate what I can track.  For example, using a simple pixel image or reference to a URL in HTML or CSS will not be able to send me the URL of…
Read more

Getting going

I’ve now got a fresh install of Laravel, which will be the framework I’ll try to build this on – it’s both the framework I’m most familiar with, and the one I’m trying to learn more about. I’m going to try to take an approach called “Test Driven Development” (TDD) – which I’m also trying…
Read more

Choosing how to track

I’ve been trying to work out how best to do the tracking.  There seem to be two options: Request a resource using CSS or an image Make a JS call The main disadvantage of the CSS/image approach is that it won’t be able to send a referrer so we won’t be able to see where…
Read more

First steps

Today I was thinking about the new GDPR data protection regulations. I realised that I use Google Analytics a lot, and make use of hardly any of the features of it. And I have concerns about what the GDPR means for use of Google Analytics. So I had the idea of simpler, open-source, self-hosted, privacy-aware,…
Read more