Mixpanel is deep product analytics, built on per-user tracking to model cohorts and journeys. analyticshq is privacy-first web analytics: how your site and marketing perform, counted exactly, with no cookies, no consent banner, and data you own.

[0m

analyticshq vs Mixpanel

Two different jobs. Pick the one you actually have.

Get your script tag How the privacy works

Mixpanel vs analyticshq

Point for point.

What it is Product analytics: per-user journeys, cohorts, funnels. Web analytics: traffic, sources, and lightweight conversions.

Cookies and identity Cookies and a persistent user identity across sessions. Cookieless. A daily rotating hash, no cross-session profile.

Consent banner Personal data, so a consent banner and DPA are required. No personal data, so no banner and nothing to consent to.

Script weight A full JavaScript SDK, tens of KB before you send an event. Under 2 KB, first-party, loaded once and deferred.

Where your data lives In the Mixpanel cloud. In your own PostgreSQL database, and nowhere else.

Open source and self-host Proprietary and hosted only. MIT-licensed and self-hostable on your own box.

Pricing Free tier, then usage-based pricing that climbs with events. Free tier, flat Pro, and free forever if you self-host.

Where Mixpanel leads: for genuine product analytics it does things analyticshq deliberately does not. Cross-session funnels, cohort retention, per-user profiles, and experimentation are its whole point. If you need to follow individual users through a product, Mixpanel is the right tool, and analyticshq is not trying to replace it.

See what events we do track

Why teams pick analyticshq instead.

Most teams do not need per-user tracking

Mixpanel profiles every visitor to build cohorts and journeys. If your real question is how your site and marketing are doing, that machinery is overkill and a privacy liability. analyticshq answers it without identifying anyone.

No consent banner, no SDK weight

Because analyticshq stores no personal data, there is no banner to bolt on and no DPA to sign. The whole script is under 2 KB, versus a product-analytics SDK that loads before it does anything.

Your numbers stay yours

Events land in a PostgreSQL database you control instead of a vendor cloud, priced per event. Nothing is sampled, and nothing is metered against a plan.

< 2 KB

First-party script versus a full product-analytics SDK of tens of KB.

Cookies set, user profiles built, or consent banners shown.

Flat

A predictable Pro price instead of usage-based billing that climbs with events.

Measuring a website, not profiling its visitors.

Get your script tag See a live dashboard

[1m[31m╭──────────────────────────────────────────────────────────────╮[0m [1m[31m│[0m [1m[41m ERROR [0m [31mInclude Error[0m [1m[31m│[0m [1m[31m╰──────────────────────────────────────────────────────────────╯[0m [36m[1mFile:[0m [2mmixpanel.stx[0m [33m[1mMessage:[0m Error loading include file site-footer: ENOENT: no such file or directory, open '/var/www/analyticshq-main/releases/1ee3824/resources/partials/site-footer.stx'