DEV Community


Discussion on: Server-Side Analytics with Jamstack Sites

iamschulz profile image
I am Schulz • Edited

But as long as you're acting in good faith, as I believe we are, analytics benefits viewers as much as anyone else.

This seems problematic. Even if we as developers act in good faith (which is a stretch), the people were coding are definitely not.
Trying to work around an ad blocker or privacy tool never has any advantages for your user. You actively oppose their decision not to be tracked.

lukeocodes profile image
@lukeocodes 🕹👨‍💻 Author • Edited

I disagree.

Historically, ad blockers were primarily designed to improve user experience, because trackers have a negative impact on page performance. They have a privacy point now, but it isn't their main function. Most people use them to avoid adverts on videos more than anything else, with the side-effect that they leave no footprint on the sites they visit.

Data, like what links are clicked on, how far folks scroll down a page, what elements are ignored altogether, and what UX changes have a negative impact on conversion, is important for a site owner to know so that they can invest their time accurately.

Ultimately, if a site owner can use this data to make improvements, it is better for the user. If the experience is better for the user, perhaps they learn more (on a blog) or sign up (on a marketing site). Which, is a win for the user and the business (they find their product, the business finds its sale).

Data-driven changes are what made the biggest sites you know easier and more enjoyable experiences.

Aside from all this, you can track a lot of usage at the edge now, prior to the blocker being able to do anything. It can often be linked with Google Analytics, and to an individual user once they've logged in. This post helps you achieve something close to server-side/edge analytics on platforms that don't natively link with Google (for reasons only known to them).

Some comments have been hidden by the post's author - find out more