Amplitude

What it is

Amplitude is the digital-analytics platform for behavioral data: event tracking, behavioral cohorts, retention curves, funnels, journeys, session replay, and experimentation, all sliced by who did what and when. It’s the depth-first product-analytics tool — the one you reach for when you need to answer “which behavior in week 1 predicts retention at week 12” rather than “how many sessions yesterday.” Closest comparable is Mixpanel on the pure-analytics side; Pendo and Gainsight PX sit adjacent but bundle in-app guidance that Amplitude historically left to partners, and PostHog covers similar ground for engineering-led teams that want analytics, flags, and replay in one open-source-rooted product.

Why it shows up in Customer Success stacks

• Product-health signal at the account level. CS teams running NRR and GRR plays need to know which accounts are deepening usage and which are coasting toward churn. Amplitude’s account-level cohorts and retention surface that signal before the renewal conversation, feeding it into a CSM’s health score.
• Adoption you can define, not guess. “Activated” stops being a vibe. You define the behavioral cohort (e.g. completed core action three times in first 14 days), then track what share of each account’s seats hit it — the actionable definition of adoption a CSM can act on.
• Seats are free on every plan. Amplitude’s 2026 pricing puts unlimited team members on Free, Plus, Growth, and Enterprise alike. Giving every CSM, support lead, and PM a login is no longer a licence conversation, which removes the usual reason CS ends up reading a screenshot of the product team’s dashboard instead of the dashboard.
• Agentic AI on the same data. Amplitude’s MCP server is generally available and included on every plan, including Free, alongside the AI Agents and AI Assistant that Amplitude now sells as core platform rather than a paid tier. Through MCP a CSM — or a Claude, Cursor, or Figma Make agent — can ask “which enterprise accounts dropped weekly active usage more than 20 percent this month” and get an answer from live Amplitude data.

Pricing

Amplitude repriced in 2026. The meter is now event volume rather than monthly tracked users on the self-serve plans, every plan carries unlimited seats, and the old $49/month Plus tier no longer exists.

• Free — $0, 2M events/month with no time limit and no credit card, unlimited seats, 1,000 session replays/month. Carries the whole platform at reduced volumes: analytics, session replay, feature flags, web experimentation, guides and surveys, activation, AI Agents, AI Assistant, and MCP.
• Plus — starts at $0; the first 2M events/month are free and the bill scales with event volume up to a ceiling of 700K MTUs or 70M events. Adds custom events, 20 behavioral cohorts, heatmaps, 2-year data retention, and 10,000 session replays/month. A credit card is required. Amplitude publishes no rate card for Plus — the figure comes from the estimator on the pricing page.
• Growth — custom, event-based. Advanced behavioral exploration, SSO and project permissions, 20,000 session replays/month with add-ons above that.
• Enterprise — custom, event-based. Unlimited projects, role-based access control, 50,000 session replays/month with add-ons above that.

For what the negotiated band actually looks like: Vendr’s marketplace reports an average and median annual contract value of $64,724 across 416 Amplitude purchases, spanning $24,625 to $370,790, with buyers saving 16% on average. The self-serve floor is a real $0, and the enterprise contract a mid-market CS org signs is five to six figures a year — there is not much in between once you pass the Plus ceiling.

Because the meter is events rather than seats, cost tracks how densely your product is instrumented and how heavily your audience uses it, not your CS headcount. Mixpanel made the same MTU-to-event switch in early 2026 and includes 1M events/month free, so Amplitude’s free allowance is twice the size at the entry point.

Best for

• CS and RevOps teams at PLG or hybrid SaaS where product-usage signal drives the health score and the expansion playbook.
• Product-led orgs that already own Amplitude for the product team and want CS to read the same behavioral truth instead of a parallel dataset — unlimited seats mean onboarding every CSM costs nothing.
• Small or pre-revenue teams that want real product analytics before they have a budget line: 2M events/month with no expiry covers a pre-PMF product outright.
• Teams that want depth — cohort math, retention analysis, experimentation — over the bundled in-app-guide convenience that Pendo and Gainsight PX lead with. Pick PostHog instead when the team is engineering-led and wants to self-host the whole stack; pick Mixpanel instead when you want a simpler report surface and a published per-event rate you can budget from without talking to sales.

Watch-outs

• The event meter rewards a lean tracking plan and punishes a chatty one. Auto-captured pageviews and high-frequency client events burn the allowance no matter how few people log in, so a quiet product with noisy instrumentation can cost more than a busy one with a disciplined taxonomy. Guard: audit event volume per feature before you upgrade, and sample or drop high-frequency events at the SDK rather than paying to store them.
• “Starts at $0” on Plus is an estimator output, not a list price. There is no published per-event rate for Plus; the only number you get is whatever the on-page slider returns for your volume, and it moves as your volume does. Guard: run the estimator at your projected 12-month event volume rather than today’s, and get that number in writing before you put a card on file.
• Plus stops hard at 700K MTUs or 70M events. Crossing the ceiling puts you in a Growth quote, where Vendr’s median lands at $64,724/year — a step, not a slope. Guard: if you are within roughly 2x of the ceiling, open the Growth negotiation while you are still a prospect with the option to leave, not after you have outgrown the plan you are on.
• It is analytics, not a CS platform. Amplitude reads behavior; it does not run renewal workflows, playbooks, or CSM task management. Guard: pipe Amplitude cohorts into a dedicated CS tool (Gainsight, Vitally, ChurnZero) where the health score and the plays actually live.
• Instrumentation quality is the ceiling. Inconsistent event taxonomy means useless cohorts; unlike auto-capture tools (Heap, Pendo), Amplitude rewards a deliberate tracking plan. Guard: invest in a governed event taxonomy up front, and use the AI agents to audit drift rather than to paper over it.