Author: rosswintle

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

Tracking return visits with The Anonymous Cookie

I’m still working through the pros and cons of using cookies. On the one hand, they seem like they will allow some super-useful things at relatively low cost, such as tracking a returning visitor in order to show “visitors” and “unique visitors”. But adding non-essential cookies (analytics are classed as non-essential) means that, in theory,…
Read more

Adding “simple” features

I recently added a “simple” toggle so I can show information from different time periods. BUT…this is one of this things that seems trivial but really isn’t because of the kinds of engineering decisions you might make. In this case I’m building and learning test-driven development as I go, and I wanted to use this…
Read more

Competition

In which I feel truly validated. I know work on Kownter has stalled – there are other things afoot – but then an “excitable nerd” with 22,000 followers on Twitter says this: What if website analytics software didn't take your users data to line their pockets from advertising? What is website analytics software was simple…
Read more

Why am I doing this, again?

I’m totally open to the idea that I will probably end up realising that there are too many problems to solve here and I’ll end up using an off-the-shelf, open source tool instead. But I’m plugging on because it’s fun. I actually now have a very very basic working system that is collecting data from…
Read more

Should I aggregate counts, if and so, when?

As I build this thing I’m constantly thinking about performance. I need registering a page view to be as fast and efficient as possible because on a busy site you don’t want to clog the server up with logging views and you want to avoid race conditions where two page views are updating the same…
Read more

Difficult Dates

I had an interesting thought about dates which led to me learning something and then feeling a bit stupid. The thing to bear in mind here is that I’m thinking a lot about how this tool could accumulate a LOT of data, and how I can make reporting fast.  Perhaps I should jus trust MySQL,…
Read more

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