Skip to content
Tracking live preview
All projects

Tracking

Add analytics to a new project with one script tag, not a fresh setup each time.

Every new project needed its own analytics integration, repeated 100+ times with no shared, maintainable setup.

Tech Domain · Book Dev|Published|Evidence: Live|Next.js, TypeScript

A public deployment is available to try.

Case Study

Before

Each portfolio project needed analytics tracking, but embedding Google Analytics or Plausible in every project was repetitive and hard to maintain consistently across 100+ deployments.

After

Reduced analytics setup from per-project configuration to a single script include. The centralized tracking manager provides consistent data collection across the entire portfolio with one maintenance point.

How it's solved

Built a unified tracking pixel that provides a single script tag for all projects. Handles page views, custom events, session tracking, and error reporting through a centralized endpoint with a privacy-first architecture.

Trade-offs

Privacy-first means less granular data than a full analytics suite — some cross-session attribution isn't tracked.

Related Articles

Further reading on related topics from the blog

Related Projects

More in Tech Domain · Book Dev

Tracking - Chaowalit Greepoke Portfolio