Web Analytics for Developers: API-First, Privacy-First

Most analytics tools were built for marketers. They assume you want funnels, heatmaps, session recordings, and A/B testing dashboards. For developers, the requirements are fundamentally different. You want data you can programmatically access, scripts that don't degrade page performance, and privacy guarantees that mean you never have to think about consent banners.

After surveying hundreds of developer-focused teams, the same requirements come up again and again:

The tools that meet these criteria are a small subset of the analytics market. Let's walk through the four best options for developer teams.

Copper Analyticswas designed with developer ergonomics as a first-class concern. The tracking script is a single async tag, the REST API covers every metric visible in the dashboard, and the entire platform works without cookies or personal data collection.

Full REST API

Query pageviews, visitors, referrers, top pages, devices, browsers, and countries. Filter by date range, path, or referrer domain.

AI crawler tracking

See which bots (GPTBot, ClaudeBot, Perplexity, Bytespider) are crawling your site, how frequently, and which pages they target.

Core Web Vitals

LCP, CLS, INP, FCP, and TTFB tracked automatically — no separate performance monitoring tool needed.

Data export

Export any time range as CSV or JSON via the API. Connect to your own data pipelines. See thedata export feature page.

Lightweight script

Under 4 KB, async-loaded, no cookies, no personal data, no layout shift.

Free tier

Not a trial — a permanent free plan for smaller sites and side projects.

Plausibleis the go-to open-source privacy analytics tool. Its tracking script is under 1 KB — the smallest in the industry — and the Stats API lets you pull aggregate data for any metric and time range. The self-hosted option (via Docker) gives you complete data ownership.

Stats API

Query timeseries, aggregate, and breakdown endpoints for visitors, pageviews, bounce rate, visit duration, sources, pages, and more.

Sites API

Programmatically create, update, and delete sites — useful for agencies or SaaS platforms managing many domains.

Self-hosting

AGPL-licensed, Docker-based deployment. Full data sovereignty on your own infrastructure.

Custom events

Track button clicks, form submissions, or any user action with theplausible()JavaScript function.

Plausible's main limitation for developers is the lack of user-level or session-level data — everything is aggregate. If you need individual user tracking (for product analytics), you'll need a different tool.

Umamiis a fully open-source analytics tool built with Next.js and PostgreSQL (or MySQL). It appeals to developers who want a modern tech stack they can understand, fork, and extend. Umami offers both a cloud-hosted service and a self-hosted option with one-click deployment to Vercel, Railway, or Docker.

REST API

Comprehensive endpoints for websites, sessions, events, pageviews, and metrics. Token-based authentication.

Modern stack

Built on Next.js, Prisma, and PostgreSQL. Easy to contribute to or customize if you fork the repo.

One-click deploy

Deploy to Vercel, Railway, DigitalOcean, or Docker Compose in minutes.

Event tracking

Track custom events with theumami.track()function, including event properties for segmentation.

Umami's weakness is scale. Self-hosting with PostgreSQL requires careful tuning at high traffic volumes, and the cloud offering is relatively new compared to Plausible's managed service.

PostHogis the heavy hitter. It goes far beyond web analytics into product analytics, feature flags, session recordings, A/B testing, and surveys — all self-hostable. If your team needs to understand not just traffic but in-product user behavior, PostHog is the most developer-friendly option in that category.

Comprehensive API

Query events, persons, insights, feature flags, and experiments programmatically. HogQL for ad hoc SQL-like analysis.

Self-hosting

Deploy with Docker or Kubernetes on your own infrastructure. Open source under MIT license.

SDKs everywhere

Official SDKs for JavaScript, React, React Native, Node.js, Python, Go, Ruby, PHP, Android, iOS, and Flutter.

Feature flags

Roll out features to a percentage of users and measure impact without a separate feature-flag service.

The tradeoff: PostHog's tracking script is significantly larger (around 60–90 KB depending on features loaded), and the self-hosted deployment is complex (Kubernetes recommended for production). It also uses cookies by default, though cookieless mode is available.

Developers expect two installation paths: a script tag for static sites and an npm package for frameworks like Next.js, Nuxt, Remix, or SvelteKit. Here is how each tool handles installation.

Every tool on this list supports a single script tag in your HTML . For most sites, this is the fastest path to working analytics:

For React-based frameworks, you can load the script dynamically or use an official package. Here is a Next.js example using the Copper Next.js integration:

Plausible, Umami, and PostHog all follow a similar pattern. PostHog offers a dedicatedposthog-jsnpm package with React hooks for feature flags and event tracking. Umami provides@umami/trackerfor framework integration.

The real power of API-first analytics is programmatic access. Below are practical examples for fetching data from each tool's API.

Fetch your site's top pages for the last 7 days:

Query aggregate visitor stats for a specific date range:

Retrieve website metrics from a self-hosted Umami instance:

Run a HogQL query to get pageview counts grouped by path:

A growing pattern among developer teams isheadless analytics— deploying a tracking script and consuming data exclusively through the API, without ever opening the vendor's dashboard. This approach treats analytics like any other data source: something you query, transform, and display in your own tools.

Slack bot integration

A cron job queries the analytics API every morning and posts a summary (visitors, top pages, top referrers) to your team's Slack channel.

CI/CD gating

After deploying a new feature, query the API to check if error page views spike or if a specific conversion event drops below a threshold.

Custom dashboards

Build a Grafana panel, a React dashboard, or a CLI tool that pulls data from the analytics API and displays exactly what your team needs.

Weekly email reports

A serverless function queries the API, renders an HTML email template, and sends it to stakeholders via SendGrid or Resend.

Data warehouse sync

Pipe raw analytics data into BigQuery, ClickHouse, or a Postgres table for cross-referencing with product or revenue data.

The key requirement for headless analytics is a comprehensive, well-documented API. All four tools covered in this guide support this pattern, butCopper Analyticsand Plausible offer the simplest API surface for pure web analytics use cases.

Here is how all four tools stack up on the criteria developers care about most:

The right analytics tool for your dev team depends on the scope of what you need to track and how much infrastructure you want to manage.

For most developer teams building websites, blogs, documentation sites, or SaaS marketing pages, a lightweight web analytics tool (Copper Analytics, Plausible, or Umami) is the right fit. PostHog enters the picture when you cross the line from “I want to know my traffic” to “I want to understand in-product user behavior.”

For a deeper look at setting up Copper in a Next.js project, read our Next.js analytics setup guide. To explore data export options, visit the data export feature page.