The Pulse of Modern Web Analytics 📊 - No cookies, no personal data - ~9KB script, one-line setup - Events, goals, revenue, vitals - Free up to 10K events/mo
Joined March 2026
- Tweets375
- Following134
- Followers16
- Likes195
Pinned Tweet
🚀 Introducing Pulzivo Analytics!
The Pulse of Modern Web & Product Analytics.
What we built:
✅ Privacy-first tracking (no cookies!)
✅ One script tag setup (5KB)
✅ Free forever plan (10K events/mo)
✅ GDPR & CCPA compliant
✅ Real-time dashboard
✅ Error & click tracking
Perfect for developers who care about user privacy 🔒
Try it free: pulzivo.com
GA4 tip: a spike in "Direct" traffic often isn't direct. Links opened from apps, PDFs, Slack, or an https-to-http hop drop the referrer, so GA4 files them as (direct)/(none). Tag shared links with UTMs before blaming SEO. What's your weirdest Direct spike?
Supply chain risk is mostly about how many third-party scripts run on pages that handle payments. Fewer, smaller scripts, with no cookies and no personal data, means less to leak when something upstream is compromised.
Who got compromised in Polymarket’s frontend supply chain?
Potential third-party exposure:
Google Tag Manager, Google Analytics, Amplitude, AppsFlyer, Segment, Plausible, Tinybird, Meta, TikTok, X, Reddit, Snapchat, LiveIntent, Google Ads, DoubleClick, Dub, Intercom, Customer.io, Braze, Pusher, Magic, FUN.xyz, WalletConnect, MetaMask, Coinbase, MoonPay, Daimo, Alchemy, QuickNode, Goldsky, Polygon RPC, Cloudflare, Vercel, AWS S3, DigitalOcean Spaces, jsDelivr, Datadog, Sentry, DebugBear, Jam.dev, LaunchDarkly, Cloudflare Turnstile, Vercel Speed Insights, Sportradar, Stats Perform, GRID, YouTube, Twitch, OpenWeather, Open-Meteo, ip-api, ipapi.co.
Our guess? A compromised third-party JavaScript dependency.
Who’s your bet?
Good checklist. Start with order count in the platform vs your backend. If that number is off, everything downstream (ROAS, attribution, consent modeling) is built on sand.
GA4 throwing traffic into "Unassigned"? Check your UTMs first. A utm_medium like "newsletter" or "social-post" doesn't match GA4's default channel rules, so it lands nowhere. Use mediums GA4 expects (email, social, cpc) and the channel report cleans up fast.
Owning your analytics and link data means you can drop the tracking wrappers and the extra scripts. Less third-party code on a page is better for speed and for visitors.
Just realized another crazy benefit of owning both my newsletter engine and my web analytics:
Normally newsletters wrap every link in an ugly tracking redirect (click.*.com/...) which hurts deliverability, gets triggered by corporate email scanners, and still doesn't connect to your analytics
Because both live on my own server, I keep clean direct links (*.com/?nl_c=...) with Resend click-tracking completely off:
1. Email bots/scanners don't run JS, so fake clicks are ignored automatically
2. When a real human lands on any of my 23 sites, my analytics script pings the newsletter DB in 1ms to mark the click
3. It identifies that visitor across all 23 sites before they even log in or pay on Stripe
4. You see the exact $ revenue each email and sequence made per subscriber, so Claude Code can see which emails actually printed money and write more of what converts
Trying to wire this between Beehiiv + DataFast APIs would be nearly impossible, when it's your own code it's 30 lines!
The scariest analytics failures still return numbers. A dead tag gets fixed in a day; a tag firing on half of checkouts quietly corrupts every decision for a quarter. Reconcile against orders regularly.
The scariest analytics failures still return numbers. A dead tag gets fixed in a day; a tag firing on half of checkouts quietly corrupts every decision for a quarter. Reconcile against orders regularly.
GA4 showing "(not set)" as a top landing page?
Usually a session started without a page_view: the 30-min timeout lapsed on an open tab, then a scroll or click kicked off a new session.
The report isn't broken. It's counting sessions you'd never call visits.
Lesson here: any third-party script on a checkout page is attack surface. Keep it small, keep it updated, and don't load analytics on payment steps at all.
Plausible showed there's room for analytics that just answers the basic questions: where traffic comes from and what people read. Most small sites don't need a 40-report console.
Plausible Analytics scaled past $3.5M a year in revenue with a core team of just two people.
They went head-to-head with Google Analytics and won a massive market share...
They didn't achieve this by building a hyper-complex dashboard with hundreds of configurations.
They did the exact opposite.
They stripped the product down to a simple, privacy-first, one-page dashboard and weaponized a "Build in Public" strategy:
• They blogged about every single engineering hurdle transparently
• They turned their transparency into their primary marketing funnel
• They proved that a 2-person operation can handle billions of monthly data points with zero corporate bloat
Software isn't expensive to run anymore.
It's expensive to manage. Keep your team tiny.
GA4 with Google signals on can withhold rows under "data thresholds" when user counts are low.
Small site, small numbers, and the report hides exactly what you wanted to see.
Pulzivo just shows the counts. No cookies, no personal data. pulzivo.com
Simplicity was the whole pitch. For most small sites, a few clear numbers beat a GA-sized report, and no cookies, no personal data keeps the setup light too.
For many, the appeal of products like Plausible was the simplicity compared to complex tools like GA.
Obviously I don't have inside knowledge, but I wonder how they are doing now that you can deal with GA with an agent and not care about the complexity.
I kind of think privacy as Plausible advertises it is a concern for visitors, but not for those who actually need analytics, ie the paying customers of Plausible.
Worth remembering: consent rates shape every number you see. If a metric depends on who clicked Accept, it's a sample, not the whole audience.
GA4 reported 12 leads. BigQuery counted 33.
The other 21 clicked "Reject All". Consent Mode v2 still sent a cookieless ping for each one. GA4 hid them below its modeling threshold. The raw BigQuery export kept every hit.
brillmark.com/bigquery-gdpr-…
Worth remembering when reading any channel report: the people who read an answer and then search your name show up as organic or direct, so those buckets quietly hold a lot of the credit.
if you're a marketer and you believe GEO is a waste of time, you're ngmi
the "studies" he cites:
> mhc - looks at GA4 referrals for AI traffic. that's like using judging a book quality by how many times it was returned to the library (you miss all ppl who bought the book, ebook downloads, borrowed from a friend, etc)
> seoworks - hmm an SEO services company that proports organic traffic to be higher in volume and quality...also looks at GA4
> an SEO substack - it doesn't name the 12 sites reviewed
> go fish case study - knocked for not giving a baseline for conversions which sure but where's this rigor for the other "studies"
GA4 "Direct" traffic jumped? Before blaming a campaign, check stripped referrers, consent-denied sessions, and redirects dropping UTMs.
Analytics shouldn't need a 40-minute audit to answer "where did visitors come from?"
pulzivo.com: no cookies, no personal data.
New pulzivo.com is live: a fresh home page with a sample dashboard, a rewritten Why Pulzivo page, and better docs. Still no cookies, no personal data. pulzivo.com
Privacy by default: Do Not Track and GPC are respected, there's a one-call optOut(), and emails and URL tokens are stripped from events.
The dashboard now shows time on page, scroll depth and a new Site Insights card. Reports load in about 0.2-0.5s. Free up to 10K events/mo, paid plans $9 / $29 / $99. pulzivo.com/docs