Event tracking & ingest
Every track() call is a billable line item, so your data team spends meetings deciding what NOT to instrument.
What people actually say
✕Event-based pricing forces teams to constantly think about which events to fire — some teams moved to Amplitude because user-based pricing felt less punitive.
Source: OpenPanel, Mixpanel pricing 2026 ↗✕Costs jump rapidly if teams track low-value interactions or hit a user-base growth spurt, so a clear data-tracking plan is essentially required to avoid surprise bills.
Source: Userpilot, Honest Mixpanel Reviews 2026 ↗✕The underlying event-collection API has been criticised for how it handles user identity, leading to schema problems that compound without a dedicated data engineer.
Source: Crazy Egg, Mixpanel review ↗
A typed Postgres event table fed by a tiny Next.js /collect route, batched through Inngest. No $0.28 per 1k meter — your bill is RDS plus the EC2 it takes to ingest. Instrument every click without a finance meeting first.