Privacy choices

This site may send the owner a minimal page-visit notice with page, browser, device type, and resolution. If you accept analytics, it can also remember an anonymous visit/session ID and collect richer engagement signals.

Read the privacy notice
AlexPersonal Operating System
Alex OS Online
Back to Projects
LinkedIn
ProjectJuly 13, 2026

Visitor Analytics & Live Alerts

First-party visitor analytics built into the CMS — anonymous session and page-view tracking, a live traffic dashboard, and real-time Slack/email alerts when someone visits or converts.

Category
cms_web
Tech stack
Next.js, MySQL, Slack webhooks, Nodemailer
Metrics
Zero third-party trackers, Real-time Slack + email alerts
Role
Design + build

Content

A tracking beacon in the public layout writes anonymous sessions, page views and conversion events to the CMS database (migration 0014). The Traffic tab on the analytics dashboard shows live visitors, uniques, views, bounce rate, and breakdowns by device, browser, country, referrer and top pages. A notification layer pushes new-visitor and conversion alerts to Slack (incoming webhooks) and email, with per-channel enable flags and graceful failure handling.

Problem

Third-party analytics are blocked by ad-blockers, over-collect data, and live outside the CMS. I wanted to know who is on the site right now and get pinged when it matters — without shipping visitor data to anyone else.

Outcome

Full visibility of site traffic with zero third-party trackers, plus real-time Slack pings on visits and conversions.

analyticsprivacyslacksystem

Explore with Alex OS

First-party analytics built directly into the CMS — no third-party trackers, real-time Slack pings on visits and conversions.

Visitor Analytics & Live Alerts

Anonymous session and page-view tracking built into the CMS database, a live traffic dashboard, and real-time Slack and email alerts when someone visits or converts. Stack: Next.js, MySQL, Slack webhooks, Nodemailer. Role: design and build.

The Problem Worth Solving

Third-party analytics tools get blocked by ad-blockers, over-collect visitor data, and live outside the CMS — meaning gaps in coverage and no ownership of the data. The specific need: know who is on the site right now and get notified when a conversion happens, without sending visitor data to any external service.

How It Works

Key Tradeoff

Building first-party means owning the schema, the query load, and the alerting infrastructure — more to maintain than dropping in a script tag. The payoff: full data ownership, no ad-blocker blind spots, and alerts that fire on real events rather than polling a third-party dashboard.

Outcomes

Zero third-party trackers on the site. Real-time Slack and email alerts on visits and conversions. Full traffic visibility — sessions, uniques, bounce rate, device and geo breakdowns — stored and queryable inside the same CMS database. System status: active.