#free-ideas Minimal on-premise cookie-less analytics for landing pages
Personally I have a need for the tiniest possible analytics tool that:
?ref= / UTM params, and current page URL, to know where the user came from to my landing page or other page on the site;— and that’s it. All I care about is hits, not unique visitors or tracking their journey on the site; instead I want it to be as non-intrusive as possible. I’m using a static website hosting (Firebase in my case), so the tracking API must be something separate, but self-hosted (e.g. Firebase Functions + Firebase Firestore or Realtime Database).
I’m thinking of doing it myself, but I’m really poorly skilled in web dev and JS in general. Maybe someone wants to develop it as an open source side project? This is obviously not a SaaS and perhaps not even a paid product, but it can still be used to promote your main offer. E.g., @ecehanece could build this tool around his charts and promote Charts Factory with it, or make the integration with charts paid.
Cool idea! I'm thinking how to monetize Charts Factory for a few days. It can be a feature to be used in paid version of my product. Thanks man.
I need to research how to track HTTP referrer without storing cookies or something else and if it's feasible, it can be added as a feature.
Here’s a snippet from my landing page where I’m getting a referrer (either ?ref or HTTP one; UTM can wait)
all that needs to be done is to send a HTTP request (e.g. a GET request to get a 1x1px gif, like GA does for example) to a self-hosted API, sending that data along with
document.location.href, and save it to the DB on the server side. Doesn’t really sound hard, except for the "nice reporting" part.This gets trickier if you want to distinguish between unique users and returning visitors, which seems to be tables stakes for site analytics.
FWIW I switched browserless over to https://usefathom.com/, it's been a pretty good so far (I'm self hosting it atm).
I know about Fathom, and they do use cookies. And there seems no way to configure it otherwise (they claim it's a vital feature).
I don't care about unique vs returning, all I want is to count hits and track referrers. I guess, not being able to distinguish between unique vs returning is a lesser problem than getting only a fraction of data because people didn't care to consent to cookies. Friction is the last thing a landing page needs.
P.S. It's a LP for a mobile app. The app is where I care for full analytics, LP not so much. Hence my use case.
Just saw this post from our dashboard & wanted to clear things up. We don't use cookie & are fully compliant with privacy laws.