Showcase


Verified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Dashboards reporting — stories about dashboards reporting in this arenaDashboards reportingevidence →
Stories about dashboards reporting in this arena
Event ingestion — stories about event ingestion in this arenaEvent ingestionevidence →
Stories about event ingestion in this arena
Flags experiments — stories about flags experiments in this arenaFlags experimentsevidence →
Stories about flags experiments in this arena
Funnels retention — stories about funnels retention in this arenaFunnels retentionevidence →
Stories about funnels retention in this arena
Integrations — connecting to other tools — breadth and depth of built-in integrationsIntegrationsevidence →
Connecting to other tools — breadth and depth of built-in integrations
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy cookieless — stories about privacy cookieless in this arenaPrivacy cookielessevidence →
Stories about privacy cookieless in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Session replay — stories about session replay in this arenaSession replayevidence →
Stories about session replay in this arena
Warehouse sql — stories about warehouse sql in this arenaWarehouse sqlevidence →
Stories about warehouse sql in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Amplitude stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Webhooks · Scoped API keys · Versioning policy · API sandbox · Stream events onward to third-party destinations (CRM, ad platforms, webhooks) from the analytics platform
Subscribe to events via webhooks
—–
Build against official SDKs
✓8/10
Issue scoped/least-privilege API credentials for an agent
—–
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
✓9/10
unlocks → Interactive API docs
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
—–
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
~6/10
unlocks → MCP client
Operate the product with natural-language commands
✓8/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
✓8/10
Set up automations that run autonomously in the background
~4/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Dashboards reporting — stories about dashboards reporting in this arenaDashboards reporting
Stories about dashboards reporting in this arena
Event ingestion — stories about event ingestion in this arenaEvent ingestion
Stories about event ingestion in this arena
Identity
Flags experiments — stories about flags experiments in this arenaFlags experiments
Stories about flags experiments in this arena
Funnels retention — stories about funnels retention in this arenaFunnels retention
Stories about funnels retention in this arena
Integrations — connecting to other tools — breadth and depth of built-in integrationsIntegrations
Connecting to other tools — breadth and depth of built-in integrations
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy cookieless — stories about privacy cookieless in this arenaPrivacy cookieless
Stories about privacy cookieless in this arena
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Session replay — stories about session replay in this arenaSession replay
Stories about session replay in this arena
Warehouse sql — stories about warehouse sql in this arenaWarehouse sql
Stories about warehouse sql in this arena
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 6/10 | Cclaimed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | none | untested | none yet | |
Answer "which activation step loses users?" myself with funnels and drop-off analysis, without an analyst C Self serve insights | founder | Funnels retention — stories about funnels retention in this arenaFunnels retention | 3 | full | 8/10 | Xcommunity | |
Have an agent answer growth questions from live product data by running queries through the API or MCP server C Ai analytics ops | ai-native user | Warehouse sql — stories about warehouse sql in this arenaWarehouse sql | 3 | full | 8/10 | Tprobed | |
Measure retention over time and slice it by behavioral cohorts C Behavioral analysis | product-manager | Funnels retention — stories about funnels retention in this arenaFunnels retention | 3 | full | 8/10 | Cclaimed | |
Roll out features behind flags targeted by user properties, cohorts, and percentage rollouts C Feature flags | developer | Flags experiments — stories about flags experiments in this arenaFlags experiments | 3 | full | 8/10 | Cclaimed | |
Run A/B experiments with goal metrics and statistical significance reported on the results C Experimentation | product-manager | Flags experiments — stories about flags experiments in this arenaFlags experiments | 3 | full | 8/10 | Cclaimed | |
Run analytical queries and pull raw event data back through a documented query/export API G Raw access | developer | Warehouse sql — stories about warehouse sql in this arenaWarehouse sql | 3 | full | 8/10 | Tprobed | |
Send events from web, mobile, and backend apps through official SDKs for the major languages and platforms G Instrumentation | developer | Event ingestion — stories about event ingestion in this arenaEvent ingestion | 3 | full | 8/10 | Cclaimed | |
Watch recordings of real user sessions with sensitive input masked by default C Replay | product-manager | Session replay — stories about session replay in this arenaSession replay | 3 | full | 8/10 | Cclaimed | |
Build multi-step funnels with filters and breakdowns to find where users drop off C Behavioral analysis | product-manager | Funnels retention — stories about funnels retention in this arenaFunnels retention | 3 | partial | 7/10 | Xcommunity | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 5/10 | Cclaimed | |
Have an agent build a dashboard of my key metrics end-to-end via the API or MCP server C Ai analytics ops | ai-native user | Dashboards reporting — stories about dashboards reporting in this arenaDashboards reporting | 3 | partial | 5/10 | Tprobed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | none | 0/10 | ||
Query my raw events with SQL (or an SQL-equivalent query language) inside the platform C Raw access | developer | Warehouse sql — stories about warehouse sql in this arenaWarehouse sql | 3 | none | 0/10 | ||
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Jump from a funnel drop-off or an error event straight to session replays of the affected users C Replay | product-manager | Session replay — stories about session replay in this arenaSession replay | 2 | full | 9/10 | Cclaimed | |
Compose saved insights into shareable dashboards for my team C Dashboards | product-manager | Dashboards reporting — stories about dashboards reporting in this arenaDashboards reporting | 2 | full | 7/10 | Cclaimed | |
Capture clicks, pageviews, and form interactions automatically without writing tracking code for each event C Instrumentation | product-manager | Event ingestion — stories about event ingestion in this arenaEvent ingestion | 2 | partial | 6/10 | Xcommunity | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Tprobed | |
Have an agent create, target, and toggle feature flags through the API or MCP server C Ai analytics ops | ai-native user | Flags experiments — stories about flags experiments in this arenaFlags experiments | 2 | partial | 6/10 | Cclaimed | |
Stream events onward to third-party destinations (CRM, ad platforms, webhooks) from the analytics platform G Destinations | developer | Integrations — connecting to other tools — breadth and depth of built-in integrationsIntegrations | 2 | disputed | 6/10 | Dcontradicted | |
Sync events between the platform and my own data warehouse (query warehouse tables in-product or export events continuously to it) G Warehouse | developer | Warehouse sql — stories about warehouse sql in this arenaWarehouse sql | 2 | partial | 6/10 | Cclaimed | |
Explore the paths users actually take before or after a key event C Behavioral analysis | product-manager | Funnels retention — stories about funnels retention in this arenaFunnels retention | 2 | partial | 5/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Cclaimed | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 4/10 | Cclaimed | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 3/10 | Cclaimed | |
Create and manage dashboards and saved insights programmatically via the API C Dashboards | developer | Dashboards reporting — stories about dashboards reporting in this arenaDashboards reporting | 2 | partial | 3/10 | Cclaimed | |
Identify users across devices and merge anonymous pre-signup activity into their identified profile C Identity | developer | Event ingestion — stories about event ingestion in this arenaEvent ingestion | 2 | partial | 3/10 | Cclaimed | |
Track product usage without third-party cookies so I can minimize or avoid cookie consent banners C Privacy first analytics | founder | Privacy cookieless — stories about privacy cookieless in this arenaPrivacy cookieless | 2 | partial | 3/10 | Cclaimed | |
Analyze behavior at the account or company level, not just per user, for B2B products C Behavioral analysis | product-manager | Funnels retention — stories about funnels retention in this arenaFunnels retention | 2 | none | 0/10 | ||
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Bulk-import historical events from another analytics tool or a data export into the platform G Identity | developer | Event ingestion — stories about event ingestion in this arenaEvent ingestion | 1 | partial | 4/10 | Cclaimed | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | partial | 4/10 | Cclaimed | |
Subscribe to dashboards and get alerted when a key metric moves abnormally C Dashboards | product-manager | Dashboards reporting — stories about dashboards reporting in this arenaDashboards reporting | 1 | none | 0/10 |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 35 stories with headroom
What would move Amplitude’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
All evidence describes Amplitude publishing its own MCP server so external AI tools (Claude, Cursor, etc.) can pull Amplitude data — this is Amplitude acting as an MCP *server*, not as a client that plugs in and consumes external MCP servers' tools.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
nonemoves PA Scoreimpact 30
The evidence pack covers analytics, experimentation, session replay, and AI-query features, but contains no documentation of a rules/automation engine that triggers actions automatically based on events (e.g., event-triggered webhooks, workflows, or conditional messaging).
Openness — open source, data portability, and self-hosting storiesSelf-host the core product
nonemoves PA Scoreimpact 30
Amplitude is offered exclusively as a hosted SaaS analytics platform; no evidence of a self-hostable core product, open-source release, or on-prem deployment option appears anywhere in the docs, integrations, or community threads.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
No evidence in the pack addresses AI-training opt-out or data-usage-for-AI-training controls; the pack covers analytics, session replay, feature flags, and an MCP server but nothing about preventing data from being used to train AI models.
Warehouse sql — stories about warehouse sql in this arenaQuery my raw events with SQL (or an SQL-equivalent query language) inside the platform
nonemoves PA Scoreimpact 30
Missing: any documented SQL/notebook query interface inside Amplitude, evidence of a query language for ad-hoc raw event access, or hands-on confirmation of SQL support.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Evidence shows API keys, an MCP server, and OpenAPI spec, but nothing about scoped/least-privilege credential issuance (e.g., role-based API tokens, granular permission scopes) for agent use is documented.
Agenticness — how well agents can access and operate the productSubscribe to events via webhooks
nonemoves agent-readyimpact 30
Missing: any webhook API/documentation, event subscription mechanism, or third-party confirmation of webhook support.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
Evidence confirms Amplitude has API documentation (HTTP V2 endpoint, Dashboard REST API, various CRUD endpoints) and even an openapi.json spec file, but nothing in the pack shows an interactive reference UI with runnable/try-it examples — no Swagger-style console, no code sandbox, no mention of 'try it' functionality.
Showing the top 8 of 35 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map6 surfaces · 38 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs36 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Build against official SDKs
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Download a machine-readable API spec (OpenAPI or equivalent)
- Perform bulk operations across many items at once
- Version, review, and roll back my automations
- Have an agent build a dashboard of my key metrics end-to-end via the API or MCP server
- Create and manage dashboards and saved insights programmatically via the API
- Compose saved insights into shareable dashboards for my team
- Bulk-import historical events from another analytics tool or a data export into the platform
- Identify users across devices and merge anonymous pre-signup activity into their identified profile
- Capture clicks, pageviews, and form interactions automatically without writing tracking code for each event
- Send events from web, mobile, and backend apps through official SDKs for the major languages and platforms
- Have an agent create, target, and toggle feature flags through the API or MCP server
- Run A/B experiments with goal metrics and statistical significance reported on the results
- Roll out features behind flags targeted by user properties, cohorts, and percentage rollouts
- Build multi-step funnels with filters and breakdowns to find where users drop off
- Measure retention over time and slice it by behavioral cohorts
- Explore the paths users actually take before or after a key event
- Answer "which activation step loses users?" myself with funnels and drop-off analysis, without an analyst
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Track product usage without third-party cookies so I can minimize or avoid cookie consent banners
- Control data retention and deletion
- Opt out of telemetry and usage tracking
- Jump from a funnel drop-off or an error event straight to session replays of the affected users
- Watch recordings of real user sessions with sensitive input masked by default
- Have an agent answer growth questions from live product data by running queries through the API or MCP server
- Run analytical queries and pull raw event data back through a documented query/export API
- Sync events between the platform and my own data warehouse (query warehouse tables in-product or export events continuously to it)
MCP server docs9 stories
- Connect an agent via an official MCP server
- Get AI-generated insights and suggestions from my data inside the product
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Have an agent build a dashboard of my key metrics end-to-end via the API or MCP server
- Have an agent create, target, and toggle feature flags through the API or MCP server
- Answer "which activation step loses users?" myself with funnels and drop-off analysis, without an analyst
- Do everything through the API that I can do in the UI
- Have an agent answer growth questions from live product data by running queries through the API or MCP server
OpenAPI spec8 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Download a machine-readable API spec (OpenAPI or equivalent)
- Do everything through the API that I can do in the UI
- Have an agent answer growth questions from live product data by running queries through the API or MCP server
- Run analytical queries and pull raw event data back through a documented query/export API
llms.txt4 stories
Hacker News4 stories
- Capture clicks, pageviews, and form interactions automatically without writing tracking code for each event
- Build multi-step funnels with filters and breakdowns to find where users drop off
- Answer "which activation step loses users?" myself with funnels and drop-off analysis, without an analyst
- Stream events onward to third-party destinations (CRM, ad platforms, webhooks) from the analytics platform
Integrations docs3 stories
- Bulk-import historical events from another analytics tool or a data export into the platform
- Stream events onward to third-party destinations (CRM, ad platforms, webhooks) from the analytics platform
- Sync events between the platform and my own data warehouse (query warehouse tables in-product or export events continuously to it)
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
5 of 19 testable claims verified · 1 contradicted → integrity 16/100
32 distinct capability claims found in Amplitude’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
5
Verified
13
Unverified
1
Contradicted
19
Undersold
Verified (7)
“Auto-instrument page views, clicks, and sessions without manual tracking code”
Capture clicks, pageviews, and form interactions automatically without writing tracking code for each eventpartialproof ↗
“Build funnels and segment users to analyze behavior drop-off”
Build multi-step funnels with filters and breakdowns to find where users drop offpartialproof ↗
“Build funnels and segment users to analyze behavior drop-off”
Answer "which activation step loses users?" myself with funnels and drop-off analysis, without an analystfullproof ↗
“Ask questions in plain language and get AI-generated answers across all data”
Get AI-generated insights and suggestions from my data inside the productfullproof ↗
“Manage flags, experiments, and deployments from CI/scripts via Experiment APIs”
Run the product headlessly / in CI for automationpartialproof ↗
“Start a conversation about users/product and get expert-level answers in seconds without SQL or dashboards”
Get AI-generated insights and suggestions from my data inside the productfullproof ↗
“Start a conversation about users/product and get expert-level answers in seconds without SQL or dashboards”
Answer "which activation step loses users?" myself with funnels and drop-off analysis, without an analystfullproof ↗
Unverified (24)
“Setup wizard auto-detects framework, installs SDK, adds API key, fires test event”
“Send events directly from server to HTTP V2 endpoint”
Send events from web, mobile, and backend apps through official SDKs for the major languages and platformsfullproof ↗
“Evaluate feature flags locally for low-latency rollout decisions”
Roll out features behind flags targeted by user properties, cohorts, and percentage rolloutsfullproof ↗
“Create user cohorts”
Measure retention over time and slice it by behavioral cohortsfullproof ↗
“Run visual A/B tests on any page without engineering effort”
Run A/B experiments with goal metrics and statistical significance reported on the resultsfullproof ↗
“Watch real user session recordings to understand user behavior”
Watch recordings of real user sessions with sensitive input masked by defaultfullproof ↗
“Export project's event data”
Export all of my data in open formats and leavepartialproof ↗
“Manage flags, experiments, and deployments from CI/scripts via Experiment APIs”
Have an agent create, target, and toggle feature flags through the API or MCP serverpartialproof ↗
“Edit pages visually and ship winning experiment variant without code deploy”
Run A/B experiments with goal metrics and statistical significance reported on the resultsfullproof ↗
“Unified identity, event, and consent model shared across all SDKs”
Identify users across devices and merge anonymous pre-signup activity into their identified profilepartialproof ↗
“Charts, dashboards, and insights for building funnels and segmenting users”
Compose saved insights into shareable dashboards for my teamfullproof ↗
“Release features behind a flag, ramp to chosen audience, and kill switch if issues arise”
Roll out features behind flags targeted by user properties, cohorts, and percentage rolloutsfullproof ↗
“Replay sessions with full event and network context to see exact user experience”
Watch recordings of real user sessions with sensitive input masked by defaultfullproof ↗
“Test variants, target segments, and measure causal lift for confident shipping”
Run A/B experiments with goal metrics and statistical significance reported on the resultsfullproof ↗
“Embed an AI agent grounded in help content and user behavior to answer questions and complete tasks”
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
“Run Wizard CLI to instrument codebase and get first dashboard from one terminal command”
“Roll out behind a flag and run A/B tests so data drives release decisions”
Roll out features behind flags targeted by user properties, cohorts, and percentage rolloutsfullproof ↗
“Roll out behind a flag and run A/B tests so data drives release decisions”
Run A/B experiments with goal metrics and statistical significance reported on the resultsfullproof ↗
“List, export, or upload cohorts in Amplitude”
Measure retention over time and slice it by behavioral cohortsfullproof ↗
“Get dashboard graph data in JSON format through Dashboard REST API”
Create and manage dashboards and saved insights programmatically via the APIpartialproof ↗
“Jump from a chart, funnel, or support ticket directly to the exact session replay”
Jump from a funnel drop-off or an error event straight to session replays of the affected usersfullproof ↗
“Mask sensitive content, honor consent, and control what gets captured in replays”
Watch recordings of real user sessions with sensitive input masked by defaultfullproof ↗
“Use Experiment SDKs to flag and test features across web, mobile, and backend”
Send events from web, mobile, and backend apps through official SDKs for the major languages and platformsfullproof ↗
“Use Experiment SDKs to flag and test features across web, mobile, and backend”
Roll out features behind flags targeted by user properties, cohorts, and percentage rolloutsfullproof ↗
Contradicted (1)
“Bring behavioral context into external AI tools like Claude, Cursor, OpenAI, Lovable, Figma”
Plug MCP servers into this product so it can use their toolsnoneproof ↗
Undersold (19)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Drive the product through a documented public APIfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Operate the product with natural-language commandsfullproof ↗
Download a machine-readable API spec (OpenAPI or equivalent)fullproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Have an agent build a dashboard of my key metrics end-to-end via the API or MCP serverpartialproof ↗
Bulk-import historical events from another analytics tool or a data export into the platformpartialproof ↗
Explore the paths users actually take before or after a key eventpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Track product usage without third-party cookies so I can minimize or avoid cookie consent bannerspartialproof ↗
Have an agent answer growth questions from live product data by running queries through the API or MCP serverfullproof ↗
Run analytical queries and pull raw event data back through a documented query/export APIfullproof ↗
Sync events between the platform and my own data warehouse (query warehouse tables in-product or export events continuously to it)partialproof ↗
Claims outside our story set (5)
Real capability claims found in Amplitude’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Aggregate click, scroll, and selector data into visual engagement heatmaps”
source ↗“Launch in-product guides and surveys to onboard and learn from users”
source ↗“Define zones on a page to measure click rates, exposure, scroll reach, and rage clicks per region”
source ↗“Define events once and validate on ingest as single source of truth”
source ↗“Catch rage clicks, dead clicks, and errors across sessions”
source ↗
Business model
Free Starter plan up to 50K MTUs; Plus from $49/mo, Growth and Enterprise are quote-based and scale with monthly tracked users and add-on products.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% · openapi.json 100% (30d, checked every 6h since Sep 8 '26)
