I would suggest generating a unique hash for each visitor. Maybe an MD5 hash of multiple values concatenated:
Store this hash as a cookie in the browser. When the person comes back later, your script can identify it's the same person.
Store the user hash with every interaction (even pageviews). Later, when you're analyzing an action (e.g. "user subscribed to the service"), you can get the user-hash and search every other interaction associated with it in the past.
About tracking the source of traffic, it's not going to be easy anymore. All major browsers are adopting strict "no-referrer" policies now. What this means is:
They're making this switch for privacy and security reasons. It's a good thing, but it will make it a lot more difficult to track sources with precision. Unless we use UTM parameters in the URL, there's no way to know from which page the visitor came.
Hash thats clever 🙂 I was thinking about just some unique user id. Thanks.
On URL. Privacy reasons I get and I know that UTMs are more reliable but what are the security issues of referrals?
It's possible for the origin to add user sensitive data in the URL. It's bad practice, but I'd say there's 99.99999% chance that at least a handful of sites is doing that right now.
In that event, the target site can access user data without its consent from the referrer header.
Alright yeah that’s problematic. Never thought of that 🤷♂️
Me neither!.. 😊
I was just pissed at Google Analytics recently and thinking about building something better and started researching, your article caught my attention 😄
Haha nice :D
My disagreement with Google Analytics got on this path to yeah. What encouraged me to start building my own analytics were those guys: usefathom.com
Before that I never thought that one could build reliable custom analytics. But apparently two developers did.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.