Thoughts on privacy, analytics, and building a better web.
A step-by-step walkthrough for replacing Google Analytics GA4 with cookieless, privacy-first analytics. Covers what to export, how to remove GA4, and what changes after the switch.
Most 'privacy-first' analytics tools hash your IP and store the hash. We process it transiently, destroy it irreversibly, and store nothing that can identify anyone. Here's how — and what it means under GDPR.
Most analytics tools ship one bloated script to everyone. INSG lets you pick exactly which modules you need — core under 1 KB, ~2 KB with defaults.
Most analytics tools either protect privacy or track revenue. INSG does both — with truly anonymous visitor counting and Stripe revenue attribution, no personal data stored.
Ad blockers hide 25-40% of your real traffic. Here's how analytics bypass works, why it's different from ad tracking, and how INSG does it ethically.
Google Analytics is overkill for most websites. A simpler, privacy-first alternative gives you everything you actually need — without the baggage.
You can track website analytics and stay GDPR compliant without a cookie consent banner. Here's how cookieless analytics makes it possible.
An honest comparison of Plausible Analytics and INSG — where each one wins, where each falls short, and who should use what.
Cookieless analytics measures website traffic without setting cookies or collecting personal data. Here's what that actually means and why people are switching.
You don't need Google Analytics. Here's what indie devs, bloggers, and side project builders actually need from their analytics tool.
Google Analytics adds 45KB+ to every page load. Script size matters more than you think for performance, SEO, and user experience.
Plausible, Fathom, Umami, GoatCounter, Pirsch, Simple Analytics, and INSG — what each costs, what each does well, and which one you should actually pick.