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 Expertise
LinkedIn
Expertise

Product Analytics & Visitor Intelligence

Building first-party analytics into products — session tracking, conversion events, live dashboards and real-time alerting — without third-party trackers.

Problems I solve
No visibility into who visits and what they do, Ad-blockers killing third-party analytics, Wanting real-time notification of high-intent visits, Analytics data trapped outside the product database
Approach
First-party by default — data stays in the product DB, Anonymous sessions, no invasive fingerprinting, Dashboards close to where decisions are made (the admin), Alerts pushed to where the owner already is (Slack, email)
Strengths
Full pipeline ownership: schema to dashboard to alert, Reusing analytics data for AI features (journey narration)

Full description

I build analytics as a product feature rather than a bolt-on script. On this site that means anonymous first-party tracking of sessions, page views and conversions written straight into the CMS database, a live traffic dashboard with device/browser/country/referrer breakdowns, and real-time Slack and email alerts. The same data feeds the AI layer: the assistant can narrate a visitor’s journey back to them from their actual session path.

Capability statement

I can add privacy-respecting, first-party analytics and real-time alerting to a web product end to end — schema, beacons, dashboard and notifications.

Current focus

Feeding visitor behavior back into Alex OS so the site adapts to what visitors actually care about.

Explore with Alex OS

First-party analytics built into the product database — no third-party scripts, no ad-blocker blind spots, real-time Slack and email alerts included.

What This Solves

Most sites bolt on a third-party tracker and lose visibility the moment a visitor runs an ad-blocker. Alex builds analytics directly into the product's own database — session tracking, page views, and conversion events — so the data is always captured, always owned, and always queryable alongside the rest of the product.

How It's Built

The Key Tradeoff

Keeping data in the product database means more schema work upfront and no off-the-shelf vendor dashboard. The payoff: data survives ad-blockers, stays private by default, and is immediately available to other product features — including the AI layer — without an API call to a third party.

Verified on This Site

This portfolio runs the same stack: anonymous first-party session tracking written to the CMS database, a live traffic dashboard with device/browser/country/referrer breakdowns, and real-time Slack and email alerts. The assistant can narrate a visitor's own session path back to them because the analytics data feeds directly into the AI layer.