Amplitude vs Plausible Analytics

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Amplitude
   Amplitude✓fullprobed9/10

   Direct probe confirms a live llms.txt at amplitude.com/llms.txt describing itself as an AI-native platform, plus a docs.md machine-readable docs mirror and an OpenAPI spec, giving agents multiple structured entry points. missing for 10: independent third-party confirmation that agents actually consume these files effectively in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://amplitude.com/llms.txt # Amplitude Amplitude is the AI-native digital analytics platform built for AI b…”
   • [probe] “PROBE docs-md: HTTP 200 at https://amplitude.com/docs.md # Amplitude Documentation Official documentation for Amplitude analytics, SDKs, an…”
   • [probe] “PROBE openapi: HTTP 200 at https://amplitude.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   Probes explicitly show llms.txt, docs.md, and OpenAPI endpoints all return 404, indicating no agent-oriented documentation is exposed at expected locations, and no other evidence mentions llms.txt or agent-readable docs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://plausible.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://plausible.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plausible.io/openapi.json, https://plausible.io/swagger.json, https://plausible.io/api/opena…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Amplitude~partialprobed6/10

   Amplitude offers headless automation surfaces suitable for CI: HTTP V2 event ingestion API, Dashboard REST API, Experiment APIs for managing flags/experiments 'from CI, scripts, or your own tools', a CLI-based wizard, and an OpenAPI spec probe. These support scripted/automated use without a GUI, but there's no evidence of a full CLI for ongoing operations (only a setup wizard), no CI-specific recipes/examples, and no independent/hands-on confirmation that headless CI workflows work reliably. missing for 10: dedicated CLI beyond setup wizard, documented CI/CD pipeline examples, independent verification of headless automation in practice.

   • [claimed-docs] “Send data directly from your server to the HTTP V2 endpoint.”
   • [claimed-docs] “Manage flags, experiments, and deployments from CI, scripts, or your own tools with the Experiment APIs.”
   • [claimed-docs] “Run the Wizard CLI to instrument your codebase and get a first dashboard from one terminal command.”
   • [claimed-docs] “Get data that's displayed on the dashboard graphs in JSON format through the Dashboard REST API.”
   • [probe] “PROBE openapi: HTTP 200 at https://amplitude.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Plausible Analytics~partialprobed6/10

   Plausible offers a documented Events API for server-side/programmatic tracking and a Stats API (including a JSON query endpoint with scoped API keys) that can be scripted or called from CI/automation pipelines without a UI. However, there is no explicit CLI, official CI/CD integration guide, or documented automation examples, and probes show no llms.txt/OpenAPI spec for programmatic discovery. Missing for 10: dedicated CLI/CI documentation, OpenAPI/machine-readable spec, and concrete automation/CI examples.

   • [claimed-docs] “The Plausible Events API can be used to record pageviews and custom events. This is useful when tracking Android or iOS mobile apps, or for …”
   • [claimed-docs] “This is useful when tracking Android or iOS mobile apps, or for server side tracking.”
   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [claimed-docs] “API keys are scoped to one team. The team selected in the top-right menu when you create the key determines which sites it can query.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plausible.io/openapi.json, https://plausible.io/swagger.json, https://plausible.io/api/opena…”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Amplitude
   Amplitude✓fullprobed8/10

   Amplitude is not itself an agent but a SaaS analytics platform, so the axis applies; it documents an official MCP server at amplitude.com/mcp-server that brings Amplitude's behavioral data into AI tools like Claude, Cursor, OpenAI, and Lovable, corroborated by a probe confirming the page exists. Missing for 10: independent/hands-on third-party verification of the MCP server actually working in practice.

   • [claimed-docs] “Bring Amplitude’s behavioral context directly into your AI tools—Claude, Cursor, OpenAI, Lovable, Figma, and more—to get answers where you w…”
   • [claimed-docs] “Bring Amplitude's behavioral context directly into your AI tools—Claude, Cursor, OpenAI, Lovable, Figma, and more—to get answers where you w…”
   • [claimed-docs] “Start a conversation about your users or product and get expert-level answers in seconds that you can share with your whole org. No SQL, con…”
   • [probe] “official MCP server documented at https://amplitude.com/mcp-server”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   Plausible is a SaaS analytics product, so an official MCP server is a plausible ecosystem offering, but no evidence pack item mentions MCP, an agent integration, or any AI-agent connector; probes confirm no llms.txt/openapi discoverability either.

   • [probe] “PROBE llms.txt: HTTP 404 at https://plausible.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://plausible.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plausible.io/openapi.json, https://plausible.io/swagger.json, https://plausible.io/api/opena…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Amplitude
   Amplitude~partialclaimed5/10

   Amplitude ships a Wizard CLI that auto-instruments a codebase and gets a first dashboard from one terminal command (amplitude-docs-27, amplitude-docs-1), which counts as an official CLI, but this is scoped to onboarding/setup rather than a general-purpose AI-native CLI for ongoing agentic workflows. Missing for 10: documentation of a broader CLI with commands beyond initial instrumentation, evidence of AI-native/agentic use cases via the CLI, and independent hands-on corroboration of the CLI's capabilities.

   • [claimed-docs] “Run the Wizard CLI to instrument your codebase and get a first dashboard from one terminal command.”
   • [claimed-docs] “The wizard detects your framework, installs the right SDK, adds your API key, and fires a test event.”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   No evidence of an official CLI tool for Plausible; the product only offers REST APIs (Events/Stats) and dashboard/scripts, with no mention of a CLI in docs or GitHub, and probes for llms.txt/docs.md/openapi found nothing CLI-related either.

   • [claimed-docs] “The Plausible Events API can be used to record pageviews and custom events. This is useful when tracking Android or iOS mobile apps, or for …”
   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plausible.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://plausible.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plausible.io/openapi.json, https://plausible.io/swagger.json, https://plausible.io/api/opena…”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Amplitude
   Amplitude✓fullprobed8/10

   Amplitude documents a broad public HTTP API surface (event ingestion, dashboard REST API, cohort management, event/property CRUD, experiment/feature-flag APIs) plus a confirmed OpenAPI spec and llms.txt/docs.md endpoints for machine consumption, indicating a well-documented, programmatically drivable API. missing for 10: independent third-party corroboration of API completeness/reliability and no evidence of official client libraries per language beyond SDK mentions.

   • [claimed-docs] “Send data directly from your server to the HTTP V2 endpoint.”
   • [claimed-docs] “Export your project's event data.”
   • [claimed-docs] “Manage flags, experiments, and deployments from CI, scripts, or your own tools with the Experiment APIs.”
   • [claimed-docs] “List all your cohorts in Amplitude, export a cohort in Amplitude, or upload a cohort.”
   • [claimed-docs] “Get data that's displayed on the dashboard graphs in JSON format through the Dashboard REST API.”
   • [claimed-docs] “Create, get, update, and delete categories, event types, event properties, and user properties.”
   • [probe] “PROBE openapi: HTTP 200 at https://amplitude.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://amplitude.com/llms.txt # Amplitude Amplitude is the AI-native digital analytics platform built for AI b…”
   • [probe] “PROBE docs-md: HTTP 200 at https://amplitude.com/docs.md # Amplitude Documentation Official documentation for Amplitude analytics, SDKs, an…”

   proof ↗⚑ flag

   Plausible Analytics✓fullprobed7/10

   Plausible documents both a Stats API (read-only query endpoint with API keys, JSON responses) and an Events API for recording pageviews/custom events server-side, giving programmatic access to core functionality. However missing for 10: no formal OpenAPI/Swagger spec (probes show 404s), no llms.txt/machine-readable docs for AI agents, and no evidence of official SDKs or independent hands-on API integration reports.

   • [claimed-docs] “The Plausible Events API can be used to record pageviews and custom events. This is useful when tracking Android or iOS mobile apps, or for …”
   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [claimed-docs] “API keys are scoped to one team. The team selected in the top-right menu when you create the key determines which sites it can query.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plausible.io/openapi.json, https://plausible.io/swagger.json, https://plausible.io/api/opena…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Plausible Analytics
   Amplitude—none0/10

   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.

   ⚑ flag

   Plausible Analytics~partialclaimed5/10

   Plausible's Stats API keys are explicitly scoped to a single team (determining which sites can be queried) and the Stats API itself is read-only, giving some least-privilege boundary useful for an agent with read access; the Events API is separate for write-side tracking. However there's no evidence of finer-grained scopes (e.g., per-site, read/write toggles, expiring/revocable tokens, or agent-specific credential issuance) beyond team-level scoping. Missing for 10: granular per-site or per-scope permissions, credential expiry/rotation controls, and any agent-specific credential management docs.

   • [claimed-docs] “API keys are scoped to one team. The team selected in the top-right menu when you create the key determines which sites it can query.”
   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Amplitude
   Amplitude✓fullprobed8/10

   Amplitude documents a full suite of official SDKs (web, mobile, server, game engines) sharing a unified identity/event model and API surface, backed by an installer wizard, HTTP V2 ingestion endpoint, and a published OpenAPI spec, all discoverable via llms.txt/docs.md for AI-native consumption. Missing for 10: independent/hands-on developer corroboration of SDK integration ease and no explicit AI-agent-specific SDK usage examples beyond the MCP server.

   • [claimed-docs] “Evaluate flags locally for low-latency rollout decisions.”
   • [claimed-docs] “Auto-instrument page views, clicks, and sessions out of the box.”
   • [claimed-docs] “Every SDK shares the same identity, event, and consent model, so a user instrumented once is understood everywhere.”
   • [claimed-docs] “Run the Wizard CLI to instrument your codebase and get a first dashboard from one terminal command.”
   • [claimed-docs] “Use Experiment SDKs to flag and test features across web, mobile, and backend.”
   • [claimed-docs] “Use the same API surface across web, mobile, server, and game engines.”
   • [claimed-docs] “Unified SDKs provide one integration point for multiple Amplitude products.”
   • [claimed-docs] “Send data directly from your server to the HTTP V2 endpoint.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://amplitude.com/llms.txt # Amplitude Amplitude is the AI-native digital analytics platform built for AI b…”
   • [probe] “PROBE docs-md: HTTP 200 at https://amplitude.com/docs.md # Amplitude Documentation Official documentation for Amplitude analytics, SDKs, an…”
   • [probe] “PROBE openapi: HTTP 200 at https://amplitude.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   Plausible offers Events API and Stats API but there is no evidence of official client SDKs/libraries (e.g., for Python, JS, Node, etc.) for developers to build against beyond raw HTTP APIs; probes show no OpenAPI spec or llms.txt either. missing for 10: official SDK packages, language client libraries, OpenAPI/machine-readable spec, llms.txt.

   • [claimed-docs] “The Plausible Events API can be used to record pageviews and custom events. This is useful when tracking Android or iOS mobile apps, or for …”
   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plausible.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://plausible.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plausible.io/openapi.json, https://plausible.io/swagger.json, https://plausible.io/api/opena…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Amplitude—none0/10

   No evidence of any webhook subscription mechanism for events; Amplitude's evidence covers SDKs, APIs for ingest/export, integrations, and an MCP server, but nothing describes outbound webhooks for event subscriptions. missing for 10: any webhook API/documentation, event subscription mechanism, or third-party confirmation of webhook support.

   ⚑ flag

   Plausible Analytics—none0/10

   Plausible offers an Events API (inbound, for recording events) and a Stats API (read-only query), but no evidence of outbound webhooks that let a subscriber be notified of events happening. No documentation mentions webhooks or push-based event subscriptions.

   • [claimed-docs] “The Plausible Events API can be used to record pageviews and custom events. This is useful when tracking Android or iOS mobile apps, or for …”
   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Amplitude
   Amplitude✓fullprobed8/10

   Amplitude AI (docs-10, docs-34) explicitly lets users ask plain-language questions and get expert-level answers/insights across their data, and the MCP server (docs-11/17, probe-4) surfaces this behavioral context directly inside AI tools. This directly matches the story of getting AI-generated insights inside the product. Missing for 10: independent/hands-on validation of the AI insight quality (only vendor docs present), and no detail on proactive suggestion generation vs. query-response only.

   • [claimed-docs] “Ask questions in plain language — Amplitude AI surfaces answers across all your data.”
   • [claimed-docs] “Start a conversation about your users or product and get expert-level answers in seconds that you can share with your whole org. No SQL, con…”
   • [claimed-docs] “Bring Amplitude’s behavioral context directly into your AI tools—Claude, Cursor, OpenAI, Lovable, Figma, and more—to get answers where you w…”
   • [claimed-docs] “Bring Amplitude's behavioral context directly into your AI tools—Claude, Cursor, OpenAI, Lovable, Figma, and more—to get answers where you w…”
   • [probe] “official MCP server documented at https://amplitude.com/mcp-server”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   No evidence of AI-generated insights, natural-language querying, or automated suggestions within the Plausible dashboard. It offers AI-traffic tracking (which AI tools send traffic) but not AI-generated analysis of the data itself; funnels, comparisons, and filters are manual analysis tools, not AI-driven insights.

   ⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Amplitude
   Amplitude~partialclaimed4/10

   Amplitude offers pieces that resemble autonomous background automation—flag rollout/rollback rules that react to data (amplitude-docs-19), automated in-product guides/surveys triggers (amplitude-docs-14), CI/script-driven experiment management (amplitude-docs-13), and an embeddable agent that 'completes tasks for users' (amplitude-docs-26)—but there is no dedicated, documented automation/workflow builder explicitly for AI-native users to configure and run persistent background automations. missing for 10: a first-party 'automations' or workflow engine with triggers/schedules, independent evidence of autonomous background execution, and confirmation the embedded agent runs unattended rather than on-demand.

   • [claimed-docs] “Release behind a flag, ramp to the audience you choose, and turn it off the moment something looks wrong.”
   • [claimed-docs] “Launch in-product guides and surveys to onboard, announce, and learn from users.”
   • [claimed-docs] “Manage flags, experiments, and deployments from CI, scripts, or your own tools with the Experiment APIs.”
   • [claimed-docs] “Embed an agent grounded in your help content and user behavior. Answer questions, guide flows, and complete tasks for users in the moments t…”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   No evidence of any automation, scheduling, workflow, or agentic background-task capability beyond scheduled email/Slack reports, which is not autonomous automation setup; there's no workflow builder, webhook triggers, or agent framework. Missing for 10: any automation/workflow builder, trigger-based actions, agent/autonomous task execution, or scripting interface for background automations.

   • [claimed-docs] “Email reports: scheduled reports delivered to your inbox”
   • [claimed-docs] “Slack reports: send reports to a Slack channel”
   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Amplitude
   Amplitude~partialclaimed6/10

   Amplitude AI lets users ask plain-language questions and get answers across their data, and an embeddable agent can 'answer questions, guide flows, and complete tasks for users,' which shows some built-in delegatable AI assistant capability. However, evidence is limited to marketing docs snippets with no hands-on demonstration of task delegation scope, autonomy limits, or independent corroboration. missing for 10: independent/hands-on verification of the AI assistant actually completing delegated tasks, detail on task scope/autonomy, and confirmation this is available to the analytics-user persona (not just embedded end-user product).

   • [claimed-docs] “Ask questions in plain language — Amplitude AI surfaces answers across all your data.”
   • [claimed-docs] “Embed an agent grounded in your help content and user behavior. Answer questions, guide flows, and complete tasks for users in the moments t…”
   • [claimed-docs] “Start a conversation about your users or product and get expert-level answers in seconds that you can share with your whole org. No SQL, con…”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   No evidence of any built-in AI assistant feature in Plausible; it only tracks AI referral traffic (docs-20/58), which is unrelated to delegating tasks to an assistant within the product. Missing for 10: any built-in AI assistant, agentic chat interface, or task-delegation feature.

   ⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Amplitude
   Amplitude✓fullprobed8/10

   Amplitude AI lets users 'ask questions in plain language' and get answers across data, and the MCP server brings this natural-language querying into external AI tools (Claude, Cursor, etc.), directly enabling natural-language operation of the product's analytics capabilities. This is corroborated by dedicated docs pages and a probe confirming the MCP server exists. Missing for 10: independent/hands-on verification of natural-language command accuracy and breadth (e.g., can it also configure flags/dashboards via NL, not just query), and no community evidence testing this specific feature.

   • [claimed-docs] “Ask questions in plain language — Amplitude AI surfaces answers across all your data.”
   • [claimed-docs] “Bring Amplitude’s behavioral context directly into your AI tools—Claude, Cursor, OpenAI, Lovable, Figma, and more—to get answers where you w…”
   • [claimed-docs] “Bring Amplitude's behavioral context directly into your AI tools—Claude, Cursor, OpenAI, Lovable, Figma, and more—to get answers where you w…”
   • [claimed-docs] “Start a conversation about your users or product and get expert-level answers in seconds that you can share with your whole org. No SQL, con…”
   • [probe] “official MCP server documented at https://amplitude.com/mcp-server”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   No evidence of any natural-language command interface, chatbot, AI assistant, or agentic control layer for Plausible; only a Stats/Events API requiring structured requests, and probes for llms.txt/docs.md/openapi all 404. missing for 10: any NL command interface, AI assistant/chat feature, or agent-facing API discovery mechanism.

   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plausible.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://plausible.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plausible.io/openapi.json, https://plausible.io/swagger.json, https://plausible.io/api/opena…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Amplitude—none0/10

   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.

   • [claimed-docs] “Send data directly from your server to the HTTP V2 endpoint.”
   • [claimed-docs] “Get data that's displayed on the dashboard graphs in JSON format through the Dashboard REST API.”
   • [claimed-docs] “Create, get, update, and delete categories, event types, event properties, and user properties.”
   • [probe] “PROBE openapi: HTTP 200 at https://amplitude.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   There is documentation for the Stats API and Events API, but no evidence of an interactive API reference with runnable examples (e.g., Swagger/OpenAPI explorer or embedded try-it console). Probes explicitly confirm no OpenAPI spec, llms.txt, or docs.md is available, indicating no interactive/agent-friendly API reference exists. Missing for 10: interactive API explorer, runnable code examples, OpenAPI/machine-readable spec.

   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [claimed-docs] “API keys are scoped to one team. The team selected in the top-right menu when you create the key determines which sites it can query.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plausible.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://plausible.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plausible.io/openapi.json, https://plausible.io/swagger.json, https://plausible.io/api/opena…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Amplitude
   Amplitude✓fullprobed9/10

   A direct probe confirms a machine-readable OpenAPI spec is available at https://amplitude.com/openapi.json (contains an 'openapi' key), and Amplitude also exposes llms.txt/docs.md machine-readable docs. Missing for 10: no independent/third-party corroboration of the spec's completeness or usage examples beyond the probe.

   • [probe] “PROBE openapi: HTTP 200 at https://amplitude.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://amplitude.com/llms.txt # Amplitude Amplitude is the AI-native digital analytics platform built for AI b…”
   • [probe] “PROBE docs-md: HTTP 200 at https://amplitude.com/docs.md # Amplitude Documentation Official documentation for Amplitude analytics, SDKs, an…”
   • [claimed-docs] “Send data directly from your server to the HTTP V2 endpoint.”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   Plausible documents its Stats API and Events API in prose, but explicit probes for an OpenAPI/Swagger spec (openapi.json, swagger.json, well-known paths) and llms.txt/docs.md all returned 404, with no other evidence of a machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://plausible.io/openapi.json, https://plausible.io/swagger.json, https://plausible.io/api/opena…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plausible.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://plausible.io/docs.md”
   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Amplitude—none0/10

   No evidence pack mentions a sandbox, test project, or staging environment separate from production data; docs reference API keys, SDKs, and CI/deployment but nothing about isolating test data from production. Missing for 10: sandbox/test environment documentation, guidance on separating test vs production data, any staging API keys or environment flags.

   ⚑ flag

   Plausible Analytics—none0/10

   No evidence of any sandbox/test environment, staging API, or mock mode for Plausible; only production Events/Stats API docs and self-hosting options are documented, none of which describe an isolated sandbox for AI-native testing.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Amplitude—none0/10

   Evidence shows Amplitude has REST/HTTP APIs (e.g., HTTP V2 endpoint, Dashboard REST API, Experiment APIs) and an OpenAPI spec, confirming APIs exist, but nothing in the pack documents API versioning conventions or a deprecation/sunset policy for these APIs. The axis applies to any API-driven platform, but no evidence supports the specific claim of a documented deprecation policy.

   • [claimed-docs] “Send data directly from your server to the HTTP V2 endpoint.”
   • [claimed-docs] “Get data that's displayed on the dashboard graphs in JSON format through the Dashboard REST API.”
   • [claimed-docs] “Manage flags, experiments, and deployments from CI, scripts, or your own tools with the Experiment APIs.”
   • [probe] “PROBE openapi: HTTP 200 at https://amplitude.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   There's documentation for the Events API and Stats API (including a v2 query endpoint), but no evidence of API versioning scheme or a documented deprecation policy; probes for OpenAPI spec/docs.md all returned 404s. missing for 10: explicit API version numbers/labels, changelog of breaking changes, documented deprecation timeline or sunset policy.

   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plausible.io/openapi.json, https://plausible.io/swagger.json, https://plausible.io/api/opena…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Amplitude
   Amplitude~partialclaimed5/10

   Amplitude's APIs support programmatic mass operations—batch event ingestion via HTTP V2 (docs-2), CRUD across event types/properties (docs-38), cohort list/export/upload (docs-29), and CI/script-driven flag/experiment management (docs-13)—which enable bulk-style automation for AI-native users. However there's no explicit documentation of a dedicated bulk-operations UI or API endpoint for acting on 'many items at once' as a single call. Missing for 10: explicit bulk-update/bulk-delete endpoints, documented batch size limits, and independent evidence of bulk workflows being used successfully.

   • [claimed-docs] “Send data directly from your server to the HTTP V2 endpoint.”
   • [claimed-docs] “Create, get, update, and delete categories, event types, event properties, and user properties.”
   • [claimed-docs] “List all your cohorts in Amplitude, export a cohort in Amplitude, or upload a cohort.”
   • [claimed-docs] “Manage flags, experiments, and deployments from CI, scripts, or your own tools with the Experiment APIs.”
   • [claimed-docs] “Export your project's event data.”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   The evidence shows only single-item APIs (Events API for recording one event/pageview, Stats API for querying stats) and CSV import/export/consolidated dashboards, none of which describe bulk create/update/delete operations across many items (e.g., batch site/goal/user management). No documentation or community evidence indicates a bulk-operations capability suited to AI-native automation.

   • [claimed-docs] “The Plausible Events API can be used to record pageviews and custom events. This is useful when tracking Android or iOS mobile apps, or for …”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [claimed-docs] “Import stats: bring in data via CSV”
   • [claimed-docs] “Export stats: download your data”
   • [claimed-docs] “Consolidated view: all your sites in one dashboard”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round drawn
   Amplitude—none0/10

   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). Feature flags/experiments and in-product guides are mentioned but only as manually configured campaigns, not as an automatic event-triggered rules system.

   • [claimed-docs] “Launch in-product guides and surveys to onboard, announce, and learn from users.”
   • [claimed-docs] “Release behind a flag, ramp to the audience you choose, and turn it off the moment something looks wrong.”
   • [claimed-docs] “Roll out behind a flag and run A/B tests so the data, not a hunch, drives the release.”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   Plausible offers notifications (traffic spikes, email/Slack reports) and read/write APIs, but there is no evidence of a rules engine or automation feature that lets users define conditional triggers to take actions on events (e.g., webhooks, if-this-then-that logic). Missing for 10: rule definition UI/API, conditional trigger logic, automated action execution beyond static notifications.

   • [claimed-docs] “Traffic spike notifications: get alerted when traffic spikes”
   • [claimed-docs] “Email reports: scheduled reports delivered to your inbox”
   • [claimed-docs] “Slack reports: send reports to a Slack channel”
   • [claimed-docs] “The Plausible Events API can be used to record pageviews and custom events. This is useful when tracking Android or iOS mobile apps, or for …”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Amplitude—none0/10

   Amplitude is an analytics/experimentation platform; nothing in the evidence pack references scheduling recurring jobs, workflows, or automated cron-like tasks. There's no mention of scheduled reports, recurring data exports, or workflow automation triggers.

   ⚑ flag

   Plausible Analytics—none0/10

   No evidence of any scheduling, workflow automation, or recurring job capability for AI-native users; Plausible only offers scheduled email/Slack reports for humans, not programmable recurring jobs/workflows. Missing for 10: any scheduler API, cron-like job configuration, or workflow automation tooling for AI agents.

   ⚑ flag

Ai analytics ops

1. ai-native userHave an agent build a dashboard of my key metrics end-to-end via the API or MCP server

   weight 3 · round to Amplitude
   Amplitude~partialprobed5/10

   Amplitude has documented APIs (Dashboard REST API for reading chart data, event/property CRUD, cohort APIs) and an official MCP server that lets AI tools like Claude/Cursor query Amplitude data in plain language, which covers agent-driven analytics querying. However, evidence shows the Dashboard API is read-only (fetching JSON of existing dashboard graphs) and 'Create a dashboard' appears to be a UI action, not an API/MCP-exposed operation, so there's no documented end-to-end agent workflow that programmatically builds a new dashboard from scratch via API or MCP. Missing for 10: an API/MCP endpoint or example specifically for creating/configuring dashboards (not just querying data), and any hands-on/community proof of an agent successfully building a dashboard end-to-end.

   • [claimed-docs] “Bring Amplitude’s behavioral context directly into your AI tools—Claude, Cursor, OpenAI, Lovable, Figma, and more—to get answers where you w…”
   • [claimed-docs] “Bring Amplitude's behavioral context directly into your AI tools—Claude, Cursor, OpenAI, Lovable, Figma, and more—to get answers where you w…”
   • [claimed-docs] “Start a conversation about your users or product and get expert-level answers in seconds that you can share with your whole org. No SQL, con…”
   • [claimed-docs] “Get data that's displayed on the dashboard graphs in JSON format through the Dashboard REST API.”
   • [claimed-docs] “Create a dashboard”
   • [claimed-docs] “Create, get, update, and delete categories, event types, event properties, and user properties.”
   • [probe] “official MCP server documented at https://amplitude.com/mcp-server”

   proof ↗⚑ flag

   Plausible Analytics~partialprobed4/10

   Plausible exposes a Stats API (/api/v2/query) that returns JSON metrics and could be used by an agent to assemble a custom dashboard, but there is no evidence of an MCP server, agent-oriented SDK, or documented workflow for programmatic dashboard creation end-to-end. Probes confirm no llms.txt, docs.md, or OpenAPI spec, suggesting the API isn't packaged for agent discovery/consumption. missing for 10: official MCP server, agent-facing API discovery (OpenAPI/llms.txt), end-to-end example of an agent building a dashboard via API.

   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [claimed-docs] “API keys are scoped to one team. The team selected in the top-right menu when you create the key determines which sites it can query.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plausible.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://plausible.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plausible.io/openapi.json, https://plausible.io/swagger.json, https://plausible.io/api/opena…”

   proof ↗⚑ flag

Dashboards

1. developerCreate and manage dashboards and saved insights programmatically via the API

   weight 2 · round to Amplitude
   Amplitude~partialclaimed3/10

   The docs mention a Dashboard REST API that returns JSON data for existing dashboard graphs and a general 'Create a dashboard' doc, plus API endpoints for cohorts and event/property metadata, but none of these clearly describe full CRUD (create/update/delete) for dashboards or 'saved insights' via API—only read/export access is explicitly documented. Missing for 10: explicit API endpoints for creating/updating/deleting dashboards, a documented 'saved insights' API object, and independent confirmation that these operations work programmatically.

   • [claimed-docs] “Get data that's displayed on the dashboard graphs in JSON format through the Dashboard REST API.”
   • [claimed-docs] “Create a dashboard”
   • [claimed-docs] “List all your cohorts in Amplitude, export a cohort in Amplitude, or upload a cohort.”
   • [claimed-docs] “Create, get, update, and delete categories, event types, event properties, and user properties.”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   Plausible's Stats API only provides read-only query access to stats and the Events API only records events; there is no evidence of an API for creating/managing dashboards or saved insights programmatically. Missing for 10: any API endpoint for creating/editing dashboards, saving insights, or managing report configurations.

   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [claimed-docs] “API keys are scoped to one team. The team selected in the top-right menu when you create the key determines which sites it can query.”

   proof ↗⚑ flag

2. product-managerCompose saved insights into shareable dashboards for my team

   weight 2 · round to Amplitude
   Amplitude✓fullclaimed7/10

   Docs confirm core dashboard-building capabilities: creating dashboards, charts/insights, funnels/segments, and organizing dashboards/notebooks into team-owned spaces for collaboration, which directly supports composing insights into shareable team dashboards. Missing for 10: explicit documentation of sharing/permissions mechanics (e.g., link sharing, access controls) and independent/hands-on confirmation of the dashboard-building workflow beyond first-party docs.

   • [claimed-docs] “Charts, dashboards, and insights. Build funnels, segment users, answer "why".”
   • [claimed-docs] “Create a dashboard”
   • [claimed-docs] “Use spaces to organize charts, dashboards, and notebooks for the team that owns the work.”
   • [claimed-docs] “Build funnels, segment users, answer "why".”
   • [claimed-docs] “Get data that's displayed on the dashboard graphs in JSON format through the Dashboard REST API.”

   proof ↗⚑ flag

   Plausible Analytics~partialclaimed4/10

   Plausible offers dashboard sharing (shared links, embed dashboard, consolidated multi-site view) and team collaboration via SSO/roles, letting a PM share the existing analytics dashboard with a team. However there is no evidence of a 'saved insights' concept or a dashboard builder that lets a PM compose multiple saved reports/segments into a custom shareable dashboard — Plausible's dashboard is a fixed, single-page view per site (or consolidated across sites), not an assembled collection of saved insights. Missing for 10: saved/insight-level bookmarking, drag-and-drop or composable dashboard layout, ability to mix multiple custom reports into one shareable view.

   • [claimed-docs] “Consolidated view](/docs/consolidated-views): all your sites in one dashboard”
   • [claimed-docs] “Embed dashboard: embed your stats on any page”
   • [claimed-docs] “Shared links: share your dashboard publicly or with specific people”
   • [claimed-docs] “Single Sign-On (SSO): for teams on Google Workspaces, Microsoft Entra, or Okta”
   • [github] “Invite team members with role-based access, share dashboards publicly or with anyone using a simple link.”
   • [claimed-docs] “Consolidated view: all your sites in one dashboard”

   proof ↗⚑ flag

3. product-managerSubscribe to dashboards and get alerted when a key metric moves abnormally

   weight 1 · round to Plausible Analytics
   Amplitude—none0/10

   The evidence pack covers dashboards, charts, cohorts, and a Dashboard REST API, but contains no mention of subscribing to dashboards or receiving alerts when a metric moves abnormally (e.g., anomaly detection, alerting rules, or subscription/notification features). missing for 10: evidence of dashboard subscription feature, evidence of anomaly/alert detection on metrics, evidence of notification delivery (email/Slack) tied to metric changes.

   • [claimed-docs] “Create a dashboard”
   • [claimed-docs] “Use spaces to organize charts, dashboards, and notebooks for the team that owns the work.”
   • [claimed-docs] “Get data that's displayed on the dashboard graphs in JSON format through the Dashboard REST API.”

   proof ↗⚑ flag

   Plausible Analytics~partialclaimed6/10

   Plausible offers scheduled email/Slack reports (subscribe to dashboard) and explicit 'traffic spike notifications' that alert when traffic moves abnormally, directly matching the core of this story. However, evidence only covers traffic volume anomalies, not configurable alerts on other key metrics like conversion rate, revenue, or goal completions, and there's no mention of custom thresholds or anomaly sensitivity settings. Missing for 10: alerting on arbitrary/custom key metrics beyond traffic, threshold configuration, and real-time push alerts (vs. periodic email/Slack digests).

   • [claimed-docs] “Traffic spike notifications: get alerted when traffic spikes”
   • [claimed-docs] “Email reports: scheduled reports delivered to your inbox”
   • [claimed-docs] “Slack reports: send reports to a Slack channel”
   • [github] “Get weekly or monthly reports via email or Slack, including traffic spike/drop notifications.”

   proof ↗⚑ flag

Identity

1. developerBulk-import historical events from another analytics tool or a data export into the platform

   weight 1 · round to Plausible Analytics
   Amplitude~partialclaimed4/10

   Amplitude's HTTP V2 API for sending events from a server (amplitude-docs-2) and third-party ETL/integration connectors like Fivetran and RudderStack (amplitude-intdir-5, amplitude-intdir-12) suggest a path for importing external or historical event data, but there is no explicit documentation of a dedicated bulk/batch historical import tool or backfill process. Missing for 10: explicit bulk-import/backfill API documentation, guidance on importing from competitor tools (e.g., Mixpanel/Segment exports), and any hands-on confirmation of successful historical data migration.

   • [claimed-docs] “Send data directly from your server to the HTTP V2 endpoint.”
   • [claimed-docs] “Fivetran is the leader in automated data integration, delivering ready-to-use connectors that adapt to change.”
   • [claimed-docs] “RudderStack provides Event streaming, ETL Pipelines, and Reverse ETL Pipelines that allow customers to have a 360 degree actionable view of …”
   • [claimed-docs] “Export your project's event data.”

   proof ↗⚑ flag

   Plausible Analytics✓fullcommunity7/10

   Plausible has documented Google Analytics import (bring in historical data) and CSV import/export features, directly supporting bulk-import of historical events from another tool or data export. Community evidence corroborates users migrating from GA with import as a known feature, though one older comment requested the feature before it existed, suggesting it was a later addition. Missing for 10: independent hands-on verification of import fidelity/limits, and detail on supported source formats beyond GA/CSV.

   • [claimed-docs] “Import from Google Analytics](/docs/google-analytics-import): bring in your historical data”
   • [claimed-docs] “Import from Google Analytics: bring in your historical data”
   • [claimed-docs] “You can even import your Google Analytics stats.”
   • [github] “Familiar metrics, campaign tracking and Search Console integration. Import your historical Google Analytics stats and continue where you lef…”
   • [github] “Smooth transition from Google Analytics Familiar metrics, campaign tracking and Search Console integration. Import your historical Google An…”
   • [claimed-docs] “Import stats: bring in data via CSV”
   • [community] “That's why we actually migrated from Google Analytics to Plausible... By the way: Import of analytics data from Google would be a great feat…”

   proof ↗⚑ flag

2. developerIdentify users across devices and merge anonymous pre-signup activity into their identified profile

   weight 2 · round to Amplitude
   Amplitude~partialclaimed3/10

   The only relevant evidence is a generic identity-model claim ('Every SDK shares the same identity, event, and consent model, so a user instrumented once is understood everywhere'), which gestures at cross-context identity resolution but never explicitly describes cross-device merging or converting anonymous pre-signup activity into an identified user profile. missing for 10: explicit documentation of user/device ID merge behavior, identify API or alias mechanism for anonymous-to-known user transition, and any independent confirmation of cross-device identity stitching.

   • [claimed-docs] “Every SDK shares the same identity, event, and consent model, so a user instrumented once is understood everywhere.”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   Plausible's core design explicitly avoids collecting personal data or building user profiles — it uses privacy-preserving daily-salted hashes for unique visitor counts rather than persistent identifiers, and docs/community evidence confirm it does not store IPs or build cross-session/cross-device profiles. There is no mechanism described for identifying users across devices or merging anonymous activity into an identified profile.

   • [claimed-docs] “Plausible collects no personal data and requires no consent banner. Every visit in your dashboard is a real visit.”
   • [claimed-docs] “Plausible collects no personal data and requires no consent banner.”
   • [community] “They don't store IP addresses. Information they gather are not stored in a way to build user profiles or do fingerprinting.”
   • [community] “I'm fairly certain that people behind VPNs will not be properly counted (everyone with the same user-agent will be counted as if they were t…”

   proof ↗⚑ flag

Instrumentation

1. product-managerCapture clicks, pageviews, and form interactions automatically without writing tracking code for each event

   weight 2 · round drawn
   Amplitude~partialcommunity6/10

   Amplitude's docs claim built-in autocapture ('Auto-instrument page views, clicks, and sessions out of the box' and a Wizard CLI that 'instruments your codebase' in one command), directly matching the story of code-free automatic event capture. However, all support is first-party marketing/docs with no independent hands-on confirmation of the autocapture specifically, and community feedback (amplitude-comm-3) reports that real-world integration is 'very hard' and data is 'often wrong,' introducing real-world doubt about the ease claimed. Missing for 10: independent/hands-on verification that autocapture works as advertised without extra config, and resolution of the community-reported integration difficulty.

   • [claimed-docs] “Auto-instrument page views, clicks, and sessions out of the box.”
   • [claimed-docs] “Run the Wizard CLI to instrument your codebase and get a first dashboard from one terminal command.”
   • [claimed-docs] “The wizard detects your framework, installs the right SDK, adds your API key, and fires a test event.”
   • [community] “Amplitude is NOT a great product when you actually try to implement it. I have seen at least 3 companies pay for them... only to realize tha…”

   proof ↗⚑ flag

   Plausible Analytics~partialcommunity6/10

   Plausible auto-tracks pageviews and scroll depth with no code, and can automatically turn pages into goals for file downloads, form completions and outbound link clicks without custom event code (plausible-docs-40, plausible-docs-54, plausible-docs-21, plausible-docs-37). However, dedicated 'click tracking' beyond outbound links, and richer form-interaction capture, generally require custom events/Events API or tag manager setup rather than being fully automatic, and one community comment notes founders avoid deeper user-flow tracking for privacy reasons (plausible-comm-5). Missing for 10: comprehensive automatic click tracking (not just outbound links), evidence of fully automatic form field-level interaction capture, and independent hands-on confirmation of zero-code setup across all these event types.

   • [claimed-docs] “Turn any page into a goal. Automatically track file downloads, form completions and external link clicks. Set up custom events and revenue t…”
   • [claimed-docs] “Turn any page into a goal. Automatically track file downloads, form completions and external link clicks.”
   • [claimed-docs] “Scroll depth from 1 to 100 percent is tracked automatically on every page. No setup, no tag managers.”
   • [claimed-docs] “Scroll depth from 1 to 100 percent is tracked automatically on every page. No setup, no tag managers. Create scroll depth goals without code…”
   • [community] “The founders refuse to adopt tracking of user flows through a web site, allegedly for privacy reasons.”

   proof ↗⚑ flag

2. developerSend events from web, mobile, and backend apps through official SDKs for the major languages and platforms

   weight 3 · round to Amplitude
   Amplitude✓fullclaimed8/10

   Docs explicitly describe a unified SDK model spanting web, mobile, server, and game engines with a shared identity/event model (amplitude-docs-36, amplitude-docs-16, amplitude-docs-37), plus a direct HTTP V2 endpoint for backend/server-side event sending (amplitude-docs-2) and auto-instrumentation for web/mobile (amplitude-docs-4). This covers the core of the story across major platforms via official SDKs. Missing for 10: an explicit enumerated list of supported languages/platforms and independent (non-vendor) confirmation of SDK reliability/breadth beyond docs claims.

   • [claimed-docs] “Send data directly from your server to the HTTP V2 endpoint.”
   • [claimed-docs] “Auto-instrument page views, clicks, and sessions out of the box.”
   • [claimed-docs] “Every SDK shares the same identity, event, and consent model, so a user instrumented once is understood everywhere.”
   • [claimed-docs] “Use Experiment SDKs to flag and test features across web, mobile, and backend.”
   • [claimed-docs] “Use the same API surface across web, mobile, server, and game engines.”
   • [claimed-docs] “Unified SDKs provide one integration point for multiple Amplitude products.”

   proof ↗⚑ flag

   Plausible Analytics~partialclaimed4/10

   Plausible offers a generic Events API for recording pageviews/custom events usable from mobile or server-side apps, plus a script tag for web, but there's no evidence of official SDKs/libraries for specific languages (e.g., Swift, Kotlin, Node, Python) beyond raw HTTP API and script snippet. missing for 10: official mobile SDKs (iOS/Android), official backend language SDKs, community/hands-on confirmation of SDK usage.

   • [claimed-docs] “The Plausible Events API can be used to record pageviews and custom events. This is useful when tracking Android or iOS mobile apps, or for …”
   • [claimed-docs] “This is useful when tracking Android or iOS mobile apps, or for server side tracking.”
   • [claimed-docs] “Add the script to your site”

   proof ↗⚑ flag

Experimentation

1. product-managerRun A/B experiments with goal metrics and statistical significance reported on the results

   weight 3 · round to Amplitude
   Amplitude✓fullclaimed8/10

   Amplitude's Feature Experiment product explicitly supports A/B, multivariate, and bandit testing with audience targeting, causal lift measurement, and visual editing to ship variants, plus Experiment APIs for programmatic control (docs-25, docs-41, docs-42, docs-13, docs-15, docs-28). Statistical significance/causal lift is referenced ('measure causal lift') but no deep documentation of the specific stats methodology or independent hands-on validation of experiment result reporting is present. Missing for 10: detailed documentation of significance testing methodology/confidence intervals, and independent/hands-on corroboration of the experiment results UI.

   • [claimed-docs] “Ship with confidence. Test variants, target segments, measure causal lift.”
   • [claimed-docs] “Run A/B, multivariate, and bandit tests so the data, not the loudest opinion, makes the call.”
   • [claimed-docs] “Define the audience to target users by properties, cohorts, or segments.”
   • [claimed-docs] “Manage flags, experiments, and deployments from CI, scripts, or your own tools with the Experiment APIs.”
   • [claimed-docs] “Edit pages with a visual editor and ship the winning variant without a code deploy.”
   • [claimed-docs] “Roll out behind a flag and run A/B tests so the data, not a hunch, drives the release.”
   • [claimed-docs] “Use Experiment SDKs to flag and test features across web, mobile, and backend.”
   • [claimed-docs] “Release behind a flag, ramp to the audience you choose, and turn it off the moment something looks wrong.”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   Plausible is a privacy-focused web analytics tool offering goals, funnels, and traffic stats, but there is no evidence of any A/B testing/experimentation feature, variant assignment, or statistical significance reporting on results.

   ⚑ flag

Behavioral analysis

1. product-managerBuild multi-step funnels with filters and breakdowns to find where users drop off

   weight 3 · round to Plausible Analytics
   Amplitude~partialcommunity7/10

   Docs explicitly reference building funnels, segmenting users, and answering 'why' via charts/dashboards, which is core to this story, but there is no direct documentation detail on breakdown/filter mechanics within a funnel, nor independent hands-on validation of funnel accuracy — one community comment even flags data accuracy concerns during implementation. missing for 10: explicit funnel filter/breakdown feature documentation, independent hands-on corroboration of funnel drop-off analysis working as described.

   • [claimed-docs] “Build funnels, segment users, answer "why".”
   • [claimed-docs] “Charts, dashboards, and insights. Build funnels, segment users, answer "why".”
   • [claimed-docs] “Create user cohorts”
   • [community] “Amplitude is NOT a great product when you actually try to implement it. I have seen at least 3 companies pay for them... only to realize tha…”

   proof ↗⚑ flag

   Plausible Analytics✓fullcommunity8/10

   Plausible's docs explicitly describe a funnel-analysis feature that lets users define a sequence of steps, choose sequential or strict-order funnels, and see drop-off at each step, complemented by filters/segments (docs-32, docs-44) and a 'user journeys' report showing paths visitors take (docs-55, docs-41, docs-42, docs-56). This directly matches the story's ask for multi-step funnels with filters and breakdowns to find drop-off points. Missing for 10: independent/hands-on validation of funnel usability in practice, and an old community comment (plausible-comm-5) noting the founders once resisted user-flow tracking, which slightly tempers confidence though it predates the now-documented feature.

   • [claimed-docs] “Define a sequence of steps and measure how many visitors complete each one. Use funnel analysis to find where people drop off and improve yo…”
   • [claimed-docs] “Measure drop-off across a fixed sequence of steps. Or explore the paths visitors actually take to discover flows you didn't predict.”
   • [claimed-docs] “Choose between two funnel types: sequential (visitors can take other actions between steps) or strict order (steps must happen in exact cons…”
   • [claimed-docs] “User journeys: explore the paths visitors take on your site”
   • [claimed-docs] “Define a sequence of steps and measure how many visitors complete each one. Use funnel analysis to find where people drop off”
   • [claimed-docs] “Filters and segments: drill into any slice of your traffic”
   • [claimed-docs] “You can go granular and click on any of the entries in any of the reports to filter your Plausible dashboard by it.”
   • [community] “The founders refuse to adopt tracking of user flows through a web site, allegedly for privacy reasons.”
   • [community] “Plausible is very nice, but it lacks much of the information from Matomo (like 'after viewing /foo, visitors tend to view…'). Matomo... lack…”

   proof ↗⚑ flag

2. product-managerAnalyze behavior at the account or company level, not just per user, for B2B products

   weight 2 · round drawn
   Amplitude—none0/10

   The evidence pack covers user-level analytics, cohorts, funnels, session replay, and experimentation, but contains no mention of account-level or company/group-based analytics (e.g., grouping events by an 'account' or 'company' entity) that B2B PMs need. Since account-based analysis is a plausible and common analytics-platform capability, its absence here is 'none' rather than 'na'.

   • [claimed-docs] “Build funnels, segment users, answer "why".”
   • [claimed-docs] “Create user cohorts”
   • [claimed-docs] “Charts, dashboards, and insights. Build funnels, segment users, answer "why".”
   • [claimed-docs] “Define the audience to target users by properties, cohorts, or segments.”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   Plausible is designed around anonymous, privacy-first visitor-level metrics (no personal data, no user profiles/fingerprinting) and there is no evidence of any account-based or company-level grouping, CRM/CDP integration, or B2B account analytics feature in the docs, GitHub description, or community discussion.

   • [claimed-docs] “Plausible collects no personal data and requires no consent banner. Every visit in your dashboard is a real visit.”
   • [claimed-docs] “Plausible collects no personal data and requires no consent banner.”
   • [community] “They don't store IP addresses. Information they gather are not stored in a way to build user profiles or do fingerprinting.”
   • [community] “I'm fairly certain that people behind VPNs will not be properly counted (everyone with the same user-agent will be counted as if they were t…”

   proof ↗⚑ flag

3. product-managerMeasure retention over time and slice it by behavioral cohorts

   weight 3 · round to Amplitude
   Amplitude✓fullclaimed8/10

   Amplitude is core analytics product with explicit retention/behavioral-cohort features: funnels/segmentation ('Build funnels, segment users, answer why'), user cohort creation, and cohort management APIs (list/export/upload). This directly supports retention-over-time analysis sliced by behavioral cohorts, which is a first-class Amplitude use case. Missing for 10: no explicit named 'Retention chart' documentation excerpt and no independent/hands-on report specifically confirming retention-by-cohort workflow quality.

   • [claimed-docs] “Build funnels, segment users, answer "why".”
   • [claimed-docs] “Create user cohorts”
   • [claimed-docs] “Charts, dashboards, and insights. Build funnels, segment users, answer "why".”
   • [claimed-docs] “List all your cohorts in Amplitude, export a cohort in Amplitude, or upload a cohort.”
   • [claimed-docs] “Create a dashboard”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   Plausible's docs describe funnels, goals, and dashboard filters/segments, but there is no evidence of retention curves, cohort definitions, or cohort-based behavioral analysis over time. In fact, Plausible's privacy-first design (no persistent personal identifiers, daily-rotating hashed uniques, no user-flow tracking per plausible-comm-5) architecturally works against cross-session cohort/retention analysis.

   • [claimed-docs] “Define a sequence of steps and measure how many visitors complete each one. Use funnel analysis to find where people drop off and improve yo…”
   • [claimed-docs] “Measure drop-off across a fixed sequence of steps. Or explore the paths visitors actually take to discover flows you didn't predict.”
   • [community] “The founders refuse to adopt tracking of user flows through a web site, allegedly for privacy reasons.”
   • [community] “Plausible is very nice, but it lacks much of the information from Matomo (like 'after viewing /foo, visitors tend to view…'). Matomo... lack…”
   • [community] “I'm fairly certain that people behind VPNs will not be properly counted (everyone with the same user-agent will be counted as if they were t…”

   proof ↗⚑ flag

4. product-managerExplore the paths users actually take before or after a key event

   weight 2 · round to Amplitude
   Amplitude~partialclaimed5/10

   Amplitude's docs confirm funnel building and segmentation ('Build funnels, segment users, answer why') and session replay lets PMs see exact user sessions tied to funnel drop-off points, which supports exploring behavior around key events. However, no explicit mention of a dedicated Path/Journey analysis feature (e.g., Amplitude's Pathfinder/User Paths chart type) appears in the evidence, so the story's specific 'paths before/after an event' capability is only indirectly covered via funnels + session replay. Missing for 10: explicit path/journey analysis chart documentation, independent user validation of path exploration accuracy.

   • [claimed-docs] “Build funnels, segment users, answer "why".”
   • [claimed-docs] “Charts, dashboards, and insights. Build funnels, segment users, answer "why".”
   • [claimed-docs] “Go from a chart, funnel, or support ticket to the exact session.”
   • [claimed-docs] “Watch real user sessions to understand the why behind your metrics. Spot frustration, tie errors to UX, and measure engagement across every …”
   • [claimed-docs] “See exactly what users experience. Replay sessions with full event and network context.”

   proof ↗⚑ flag

   Plausible Analytics!disputedcontradicted5/10

   Plausible's marketing docs explicitly advertise a 'User journeys' feature to 'explore the paths visitors actually take to discover flows you didn't predict' (docs-41, docs-55), which matches the story closely. However, community hands-on reports directly contradict this: one HN commenter states 'The founders refuse to adopt tracking of user flows through a web site, allegedly for privacy reasons' and another notes Plausible 'lacks much of the information from Matomo (like after viewing /foo, visitors tend to view…)' — suggesting the feature is either new/limited or not as capable as claimed. Missing for 10: independent corroboration that the User Journeys feature actually surfaces pre/post-event path exploration as described, and resolution of the conflicting community reports of it being absent or weak.

   • [claimed-docs] “Measure drop-off across a fixed sequence of steps. Or explore the paths visitors actually take to discover flows you didn't predict.”
   • [claimed-docs] “User journeys: explore the paths visitors take on your site”
   • [community] “The founders refuse to adopt tracking of user flows through a web site, allegedly for privacy reasons.”
   • [community] “Plausible is very nice, but it lacks much of the information from Matomo (like 'after viewing /foo, visitors tend to view…'). Matomo... lack…”

   proof ↗⚑ flag

Self serve insights

1. founderAnswer "which activation step loses users?" myself with funnels and drop-off analysis, without an analyst

   weight 3 · round to Amplitude
   Amplitude✓fullcommunity8/10

   Amplitude's core product is explicitly built around funnels, segmentation, and self-serve answers ('Build funnels, segment users, answer why') plus an AI assistant that answers plain-language questions without SQL or a data team, directly matching the founder self-serve need. Community evidence corroborates ease of adoption across non-analyst roles, though one review notes implementation/data-quality difficulties. Missing for 10: independent hands-on validation specifically of funnel/drop-off analysis accuracy and ease for a non-analyst founder persona.

   • [claimed-docs] “Build funnels, segment users, answer "why".”
   • [claimed-docs] “Charts, dashboards, and insights. Build funnels, segment users, answer "why".”
   • [claimed-docs] “Ask questions in plain language — Amplitude AI surfaces answers across all your data.”
   • [claimed-docs] “Start a conversation about your users or product and get expert-level answers in seconds that you can share with your whole org. No SQL, con…”
   • [community] “We got on for the generous free plan, stayed for the simple UX. Amplitude has been the only analytics product that we've gotten the whole te…”
   • [community] “Amplitude is NOT a great product when you actually try to implement it. I have seen at least 3 companies pay for them... only to realize tha…”

   proof ↗⚑ flag

   Plausible Analytics~partialcommunity7/10

   Plausible has a dedicated, documented Funnel Analysis feature (sequential or strict-order steps, drop-off measurement) plus a User Journeys view showing paths visitors take, and the dashboard is explicitly designed for no-training self-serve use — directly matching the 'find where activation drops off myself' story. However, independent community feedback flags real limits: one HN commenter notes Plausible 'lacks much of the information from Matomo (like after viewing /foo, visitors tend to view...)', suggesting the flow/transition analysis is shallower than competitors, and another older comment claims the founders resisted user-flow tracking on privacy grounds. missing for 10: independent hands-on validation that funnel drop-off analysis works well in practice for real activation funnels, and resolution of the comparative gap noted vs Matomo's flow reports.

   • [claimed-docs] “Define a sequence of steps and measure how many visitors complete each one. Use funnel analysis to find where people drop off and improve yo…”
   • [claimed-docs] “Measure drop-off across a fixed sequence of steps. Or explore the paths visitors actually take to discover flows you didn't predict.”
   • [claimed-docs] “Choose between two funnel types: sequential (visitors can take other actions between steps) or strict order (steps must happen in exact cons…”
   • [claimed-docs] “Define a sequence of steps and measure how many visitors complete each one. Use funnel analysis to find where people drop off”
   • [claimed-docs] “User journeys: explore the paths visitors take on your site”
   • [claimed-docs] “You get one dashboard with the essential website stats, easy to use and understand with no training or prior experience.”
   • [community] “Plausible is very nice, but it lacks much of the information from Matomo (like 'after viewing /foo, visitors tend to view…'). Matomo... lack…”
   • [community] “The founders refuse to adopt tracking of user flows through a web site, allegedly for privacy reasons.”

   proof ↗⚑ flag

Destinations

1. developerStream events onward to third-party destinations (CRM, ad platforms, webhooks) from the analytics platform

   weight 2 · round to Amplitude
   Amplitude!disputedcontradicted6/10

   Amplitude's integrations directory documents connections to CRM (Salesforce, HubSpot), reverse-ETL/streaming tools (Hightouch, RudderStack, Segment), and states it can integrate with any system, supporting onward event streaming to third-party destinations. However, a hands-on community report explicitly states 'they dont do a good job in sending data back to things like SFDC,' directly contradicting the claimed CRM-sync capability for at least one major destination. Missing for 10: independent corroboration of reliable webhook/ad-platform streaming, and resolution of the documented SFDC sync complaint.

   • [claimed-docs] “Connect the leading data and marketing platforms to Amplitude. Don’t see what you need? We can integrate with any system.”
   • [claimed-docs] “Hightouch syncs data from data warehouses into tools that teams rely on to run the business (CRM, email, ERP, etc.”
   • [claimed-docs] “Salesforce provides customer relationship management software and applications focused on sales, customer service, marketing automation, ana…”
   • [claimed-docs] “RudderStack provides Event streaming, ETL Pipelines, and Reverse ETL Pipelines that allow customers to have a 360 degree actionable view of …”
   • [community] “Amplitude is NOT a great product when you actually try to implement it. I have seen at least 3 companies pay for them... only to realize tha…”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   Evidence only covers Plausible's Events API (ingest custom events into Plausible) and Stats API (read-only query of Plausible's own stats), plus GTM/webhook-free tracking setup — there is no mention of streaming events onward to CRMs, ad platforms, or external webhooks. No outbound integration/export-to-third-party pipeline is documented anywhere in the pack.

   • [claimed-docs] “The Plausible Events API can be used to record pageviews and custom events. This is useful when tracking Android or iOS mobile apps, or for …”
   • [claimed-docs] “This is useful when tracking Android or iOS mobile apps, or for server side tracking.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [claimed-docs] “API keys are scoped to one team. The team selected in the top-right menu when you create the key determines which sites it can query.”
   • [claimed-docs] “Google Tag Manager](/gtm-template): deploy without touching your code”
   • [claimed-docs] “Google Tag Manager: deploy without touching your code”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Amplitude
   Amplitude~partialprobed6/10

   Amplitude exposes broad APIs (HTTP V2 event ingestion, Dashboard REST API, Experiment APIs for flags/experiments, Cohorts API, taxonomy CRUD, data export) that mirror many core UI workflows, and an official MCP server lets AI tools query behavioral data. However, several flagship UI capabilities—session replay viewing/analysis, the visual A/B test editor, in-product guides/surveys creation, dashboard/chart creation, and the AI 'ask in plain language' analyst—are documented only as UI features with no corresponding API endpoints in the evidence pack. Missing for 10: API parity for session replay, visual experiment editor, dashboard/notebook creation, and guides/surveys authoring; independent confirmation that API coverage matches UI feature-for-feature.

   • [claimed-docs] “Send data directly from your server to the HTTP V2 endpoint.”
   • [claimed-docs] “Export your project's event data.”
   • [claimed-docs] “Manage flags, experiments, and deployments from CI, scripts, or your own tools with the Experiment APIs.”
   • [claimed-docs] “List all your cohorts in Amplitude, export a cohort in Amplitude, or upload a cohort.”
   • [claimed-docs] “Get data that's displayed on the dashboard graphs in JSON format through the Dashboard REST API.”
   • [claimed-docs] “Create, get, update, and delete categories, event types, event properties, and user properties.”
   • [claimed-docs] “Watch real user sessions to understand the why behind your metrics.”
   • [claimed-docs] “Edit pages with a visual editor and ship the winning variant without a code deploy.”
   • [claimed-docs] “Create a dashboard”
   • [probe] “PROBE openapi: HTTP 200 at https://amplitude.com/openapi.json — contains "openapi" key”
   • [probe] “official MCP server documented at https://amplitude.com/mcp-server”

   proof ↗⚑ flag

   Plausible Analytics~partialprobed4/10

   Plausible ships a read-only Stats API for querying metrics and an Events API for recording pageviews/custom events, letting AI-native users pull dashboard-like data and send events programmatically, but there is no evidence of API coverage for configuration tasks that are core UI features — creating/managing funnels, goals, annotations, shared links, team/SSO settings, email/Slack reports, or site management. No OpenAPI spec is discoverable (probe results all 404), reinforcing that API surface is narrower than the UI. missing for 10: API endpoints for funnel/goal/annotation creation, team & site management, shared-link/report configuration, and a discoverable OpenAPI/spec confirming full parity.

   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [claimed-docs] “API keys are scoped to one team. The team selected in the top-right menu when you create the key determines which sites it can query.”
   • [claimed-docs] “The Plausible Events API can be used to record pageviews and custom events. This is useful when tracking Android or iOS mobile apps, or for …”
   • [claimed-docs] “This is useful when tracking Android or iOS mobile apps, or for server side tracking.”
   • [claimed-docs] “Define a sequence of steps and measure how many visitors complete each one. Use funnel analysis to find where people drop off and improve yo…”
   • [claimed-docs] “You can also add annotations to the chart to mark important events like a deployment, a campaign launch or an outage.”
   • [claimed-docs] “Single Sign-On (SSO): for teams on Google Workspaces, Microsoft Entra, or Okta”
   • [claimed-docs] “Shared links: share your dashboard publicly or with specific people”
   • [claimed-docs] “Email reports: scheduled reports delivered to your inbox”
   • [claimed-docs] “Slack reports: send reports to a Slack channel”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plausible.io/openapi.json, https://plausible.io/swagger.json, https://plausible.io/api/opena…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Plausible Analytics
   Amplitude~partialclaimed5/10

   Amplitude provides data export mechanisms (event data export, Dashboard REST API returning JSON, cohort export/upload) via documented APIs, which support portability of raw data. However, there's no evidence of a comprehensive full-account export (e.g., all configuration, dashboards, experiments, session replays) in a single open-format bundle, nor any documented account-deletion/data-portability workflow for 'leaving' the platform. missing for 10: full-account export tooling covering dashboards/configs/experiments/session-replay data, an explicit data-portability/account-closure workflow, and independent verification that exported formats are truly open and complete.

   • [claimed-docs] “Export your project's event data.”
   • [claimed-docs] “List all your cohorts in Amplitude, export a cohort in Amplitude, or upload a cohort.”
   • [claimed-docs] “Get data that's displayed on the dashboard graphs in JSON format through the Dashboard REST API.”

   proof ↗⚑ flag

   Plausible Analytics✓fullcommunity7/10

   Plausible offers explicit data export (CSV export/import), a read-only Stats API for programmatic access, and is fully open-source/self-hostable (Community Edition), meaning users can export data and run their own instance to 'leave' the SaaS entirely without lock-in. Community evidence corroborates the FOSS/self-host value as a real selling point against vendor lock-in. Missing for 10: no evidence of a bulk 'export everything' guarantee covering raw event-level data, no independent hands-on test of export completeness, and no explicit documentation of data portability guarantees beyond CSV/API.

   • [claimed-docs] “Import stats: bring in data via CSV”
   • [claimed-docs] “Export stats: download your data”
   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [claimed-docs] “A getting started guide to self-hosting Plausible Community Edition”
   • [community] “One huge selling point of using Plausible is that you can self-host it and it's FOSS. If the company disappears, you can continue using what…”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Plausible Analytics
   Amplitude—none0/10

   Amplitude is a closed-source, proprietary SaaS analytics platform; the evidence pack shows only some SDKs (e.g., Flutter) are open-source but no evidence the core product's source is open-licensed or readable. This axis applies to any product (a buyer could ask about source availability), but there's no evidence of an open license covering Amplitude's core codebase.

   • [claimed-docs] “The Flutter SDK is an open-source UI for developing applications for Android, iOS, Windows, Mac, Linux, Google Fuchsia and the Web.”

   proof ↗⚑ flag

   Plausible Analytics✓fullcommunity8/10

   Plausible Community Edition is open-source on GitHub, and community evidence corroborates that the FOSS/self-hosted nature is a genuine, trusted selling point (people can maintain the code themselves if the company disappears). Missing for 10: explicit license name/text, and no direct evidence of AI-native machine-readable license documentation.

   • [claimed-docs] “A getting started guide to self-hosting Plausible Community Edition”
   • [community] “One huge selling point of using Plausible is that you can self-host it and it's FOSS. If the company disappears, you can continue using what…”
   • [community] “I'm a very happy self-hosted Plausible user for years now. Solid, simple, and easy to maintain.”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Plausible Analytics
   Amplitude—none0/10

   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.

   ⚑ flag

   Plausible Analytics✓fullcommunity8/10

   Plausible ships an official open-source Community Edition with self-hosting docs (GitHub repo), and community members confirm running it successfully in production for years, valuing that it's FOSS and can be maintained independently. Missing for 10: independent benchmarking of self-hosted performance/scale, and one community comment notes self-hosting complexity (ClickHouse dependency) as a real friction point.

   • [claimed-docs] “A getting started guide to self-hosting Plausible Community Edition”
   • [community] “I'm a very happy self-hosted Plausible user for years now. Solid, simple, and easy to maintain.”
   • [community] “One huge selling point of using Plausible is that you can self-host it and it's FOSS. If the company disappears, you can continue using what…”
   • [community] “I think Plausible's self-hosting is not simple, requiring unnecessarily heavy databases like ClickHouse, which can be overkill for the avera…”

   proof ↗⚑ flag

Privacy first analytics

1. founderTrack product usage without third-party cookies so I can minimize or avoid cookie consent banners

   weight 2 · round to Plausible Analytics
   Amplitude~partialclaimed3/10

   Amplitude's docs mention server-side event sending (HTTP V2 endpoint) and a shared consent model with options to mask sensitive content and honor consent, which implies some capacity for privacy-conscious, non-cookie-dependent tracking, but there is no explicit claim about avoiding third-party cookies or reducing cookie-consent banners. missing for 10: explicit documentation of cookieless/first-party tracking, cookie policy details, or guidance on reducing consent-banner requirements.

   • [claimed-docs] “Send data directly from your server to the HTTP V2 endpoint.”
   • [claimed-docs] “Every SDK shares the same identity, event, and consent model, so a user instrumented once is understood everywhere.”
   • [claimed-docs] “Mask sensitive content, honor consent, and control what gets captured.”

   proof ↗⚑ flag

   Plausible Analytics✓fullcommunity9/10

   Plausible's docs explicitly state it collects no personal data, uses no cookies, and requires no consent banner, which is corroborated by community reports of GDPR-compliant, cookie-free operation and no IP storage. missing for 10: independent legal/regulatory audit confirming zero consent-banner requirement across all jurisdictions.

   • [claimed-docs] “Plausible collects no personal data and requires no consent banner. Every visit in your dashboard is a real visit.”
   • [claimed-docs] “Plausible collects no personal data and requires no consent banner.”
   • [claimed-docs] “By using Plausible, you do not need cookie banners for analytics or to collect consent for tracking.”
   • [community] “Plausible Analytics is GDPR compliant - with one possible exception - the IP address which if they dropped the last 3 digits would probably …”
   • [community] “They don't store IP addresses. Information they gather are not stored in a way to build user profiles or do fingerprinting.”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Plausible Analytics
   Amplitude—none0/10

   No evidence in the pack mentions data residency, region selection, EU/US hosting options, or any data storage location controls for Amplitude. This is a fair axis for an analytics SaaS platform handling user data, but absence of evidence means it cannot be credited as delivered. missing for 10: any mention of regional data hosting options, EU/US residency controls, or data location settings.

   ⚑ flag

   Plausible Analytics~partialcommunity5/10

   Plausible enables data residency control primarily through self-hosting (Community Edition), letting users run and store data on their own infrastructure/region, corroborated by community reports of long-term self-hosted use. However there is no evidence of an official region-selection option within the hosted Cloud product (e.g., EU vs US data center choice) — missing for 10: explicit cloud region/residency selection docs, compliance certifications tied to specific regions, and independent verification of hosted-data location choices.

   • [claimed-docs] “A getting started guide to self-hosting Plausible Community Edition”
   • [community] “I'm a very happy self-hosted Plausible user for years now. Solid, simple, and easy to maintain.”
   • [community] “One huge selling point of using Plausible is that you can self-host it and it's FOSS. If the company disappears, you can continue using what…”
   • [community] “I think Plausible's self-hosting is not simple, requiring unnecessarily heavy databases like ClickHouse, which can be overkill for the avera…”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Amplitude—none0/10

   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.

   ⚑ flag

   Plausible Analytics—none0/10

   The evidence pack covers Plausible's privacy stance on cookies, consent banners, and personal data collection, but nowhere does it address whether collected data is used to train AI models or how a user could opt out of such use. No policy or documentation snippet specifically discusses AI-training data usage.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Plausible Analytics
   Amplitude~partialclaimed3/10

   Docs mention consent controls and content masking for session replay (amplitude-docs-33) and CRUD including delete for event/user properties via API (amplitude-docs-38), which touch on privacy controls, but there's no explicit documentation of a user-level data retention policy or GDPR-style deletion/export mechanism for end-user data. missing for 10: explicit data retention policy settings, a documented user data deletion/erasure API or workflow, and any independent confirmation that deletion requests are honored.

   • [claimed-docs] “Mask sensitive content, honor consent, and control what gets captured.”
   • [claimed-docs] “Create, get, update, and delete categories, event types, event properties, and user properties.”

   proof ↗⚑ flag

   Plausible Analytics~partialcommunity5/10

   Plausible collects no personal data/no cookies and offers CSV export, self-hosting, and data-policy docs implying minimal retention, but there's no explicit documented mechanism for AI-native users to programmatically control retention windows or trigger deletion of specific data via API. missing for 10: explicit retention policy/duration documentation, API or dashboard controls for data deletion/right-to-erasure, and independent confirmation of these controls working.

   • [claimed-docs] “Plausible collects no personal data and requires no consent banner. Every visit in your dashboard is a real visit.”
   • [claimed-docs] “Plausible collects no personal data and requires no consent banner.”
   • [claimed-docs] “By using Plausible, you do not need cookie banners for analytics or to collect consent for tracking.”
   • [claimed-docs] “Export stats: download your data”
   • [claimed-docs] “Import stats: bring in data via CSV”
   • [community] “They don't store IP addresses. Information they gather are not stored in a way to build user profiles or do fingerprinting.”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round to Amplitude
   Amplitude~partialclaimed4/10

   Amplitude documents a shared 'consent model' across SDKs and features to 'honor consent, and control what gets captured' for session replay, implying some opt-out/consent tooling exists in its data-collection stack, but there is no dedicated documentation about an AI-native user opting out of Amplitude's own telemetry or usage tracking of the product itself. missing for 10: explicit opt-out/DNT mechanism documentation, privacy policy specifics for AI-native/developer users, independent confirmation that consent controls actually block tracking.

   • [claimed-docs] “Every SDK shares the same identity, event, and consent model, so a user instrumented once is understood everywhere.”
   • [claimed-docs] “Mask sensitive content, honor consent, and control what gets captured.”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   The evidence describes Plausible's privacy-friendly approach to tracking *website visitors* (no cookies, no personal data collection, no consent banners) but contains no mention of any telemetry or usage-tracking mechanism in the Plausible product itself (e.g., self-hosted CE phoning home to Plausible Inc.) nor any documented opt-out setting for such telemetry.

   ⚑ flag

Ai analytics ops

1. ai-native userHave an agent answer growth questions from live product data by running queries through the API or MCP server

   weight 3 · round to Amplitude
   Amplitude✓fullprobed8/10

   Amplitude ships an official MCP server that lets AI tools (Claude, Cursor, OpenAI, etc.) query behavioral data conversationally without SQL or dashboards, plus REST/Dashboard/Export APIs for programmatic access to live product data. Together these enable an agent to answer growth questions from live data via API or MCP. Missing for 10: independent hands-on verification of the MCP server's query accuracy/reliability and no community corroboration of agent-driven analysis in practice.

   • [claimed-docs] “Bring Amplitude’s behavioral context directly into your AI tools—Claude, Cursor, OpenAI, Lovable, Figma, and more—to get answers where you w…”
   • [claimed-docs] “Bring Amplitude's behavioral context directly into your AI tools—Claude, Cursor, OpenAI, Lovable, Figma, and more—to get answers where you w…”
   • [claimed-docs] “Start a conversation about your users or product and get expert-level answers in seconds that you can share with your whole org. No SQL, con…”
   • [claimed-docs] “Get data that's displayed on the dashboard graphs in JSON format through the Dashboard REST API.”
   • [claimed-docs] “Create, get, update, and delete categories, event types, event properties, and user properties.”
   • [probe] “official MCP server documented at https://amplitude.com/mcp-server”
   • [probe] “PROBE openapi: HTTP 200 at https://amplitude.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Plausible Analytics~partialprobed4/10

   Plausible has a documented Stats API with a /api/v2/query endpoint supporting complex stats queries via API keys, which an agent could call to answer growth questions from live data. However, there is no evidence of an official MCP server, no OpenAPI/machine-readable spec (probes show 404s for llms.txt, docs.md, openapi.json), and no agent-specific tooling or SDK documented. Missing for 10: MCP server integration, machine-readable API schema/discovery, and any agent-oriented documentation or examples.

   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [claimed-docs] “API keys are scoped to one team. The team selected in the top-right menu when you create the key determines which sites it can query.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plausible.io/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://plausible.io/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plausible.io/openapi.json, https://plausible.io/swagger.json, https://plausible.io/api/opena…”

   proof ↗⚑ flag

Raw access

1. developerRun analytical queries and pull raw event data back through a documented query/export API

   weight 3 · round to Amplitude
   Amplitude✓fullprobed8/10

   Amplitude documents a Dashboard REST API returning JSON query results, an Export API for raw event data, and other CRUD APIs (events, cohorts, taxonomy), with an OpenAPI spec confirmed reachable — covering both analytical queries and raw event export as the story requires. Missing for 10: independent/hands-on developer corroboration of the export/query API's reliability and rate limits beyond first-party docs.

   • [claimed-docs] “Send data directly from your server to the HTTP V2 endpoint.”
   • [claimed-docs] “Export your project's event data.”
   • [claimed-docs] “Get data that's displayed on the dashboard graphs in JSON format through the Dashboard REST API.”
   • [claimed-docs] “Create, get, update, and delete categories, event types, event properties, and user properties.”
   • [probe] “PROBE openapi: HTTP 200 at https://amplitude.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Plausible Analytics~partialprobed6/10

   Plausible documents a Stats API (/api/v2/query) that accepts simple and complex stats queries and returns JSON, plus an Events API for recording events, and API keys scoped for querying sites — this covers programmatic querying of aggregated stats. However, this is not a SQL/warehouse-style raw event export API; there's no evidence of raw event-level data export or a documented OpenAPI spec (probes confirm openapi endpoints 404), and no independent hands-on corroboration of the query API's depth or limitations. Missing for 10: raw event-level data export/warehouse-SQL-style querying, OpenAPI/schema documentation, and independent developer corroboration of the query API's capabilities.

   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [claimed-docs] “API keys are scoped to one team. The team selected in the top-right menu when you create the key determines which sites it can query.”
   • [claimed-docs] “The Plausible Events API can be used to record pageviews and custom events. This is useful when tracking Android or iOS mobile apps, or for …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plausible.io/openapi.json, https://plausible.io/swagger.json, https://plausible.io/api/opena…”

   proof ↗⚑ flag

2. developerQuery my raw events with SQL (or an SQL-equivalent query language) inside the platform

   weight 3 · round drawn
   Amplitude—none0/10

   Evidence shows Amplitude offers dashboards, charts, cohorts, and an AI natural-language query interface (which explicitly markets 'No SQL' as a benefit), plus REST/export APIs and warehouse integrations like BigQuery/Snowflake for data export — but nothing indicates an in-platform SQL or SQL-equivalent query editor over raw events. missing for 10: 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.

   • [claimed-docs] “Ask questions in plain language — Amplitude AI surfaces answers across all your data.”
   • [claimed-docs] “Start a conversation about your users or product and get expert-level answers in seconds that you can share with your whole org. No SQL, con…”
   • [claimed-docs] “Export your project's event data.”
   • [claimed-docs] “Get data that's displayed on the dashboard graphs in JSON format through the Dashboard REST API.”
   • [claimed-docs] “BigQuery is Google's fully managed, petabyte scale, low cost analytics data warehouse.”
   • [claimed-docs] “Snowflake makes it easy to amass all your data, enable rapid analytics, and derive data-driven insights for all your business users.”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   Plausible offers a Stats API (JSON query endpoint) and Events API, but there is no evidence of SQL or SQL-equivalent query language access to raw events inside the platform — no warehouse-style query editor, no SQL interface. missing for 10: SQL/SQL-equivalent query language, raw event-level query access, in-platform query editor.

   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”

   proof ↗⚑ flag

Warehouse

1. developerSync events between the platform and my own data warehouse (query warehouse tables in-product or export events continuously to it)

   weight 2 · round to Amplitude
   Amplitude~partialclaimed6/10

   Amplitude documents an Export API for event data and lists first-party integrations with warehouses (BigQuery, Snowflake, Databricks) plus reverse-ETL tools (Hightouch, Fivetran, RudderStack) that support syncing events to/from a warehouse, satisfying the 'continuous export' half of the story. However, there's no evidence of an in-product warehouse query feature (e.g., querying warehouse tables directly within Amplitude's UI). Missing for 10: in-product warehouse querying capability, and independent/hands-on confirmation of the export-to-warehouse pipelines actually working reliably.

   • [claimed-docs] “Export your project's event data.”
   • [claimed-docs] “BigQuery is Google's fully managed, petabyte scale, low cost analytics data warehouse.”
   • [claimed-docs] “Databricks is a unified, open analytics platform that enables building, deploying, sharing, and maintaining enterprise-grade data, analytics…”
   • [claimed-docs] “Snowflake makes it easy to amass all your data, enable rapid analytics, and derive data-driven insights for all your business users.”
   • [claimed-docs] “Hightouch syncs data from data warehouses into tools that teams rely on to run the business (CRM, email, ERP, etc.”
   • [claimed-docs] “Fivetran is the leader in automated data integration, delivering ready-to-use connectors that adapt to change.”

   proof ↗⚑ flag

   Plausible Analytics—none0/10

   Plausible offers a Stats API for querying its own data and an Events API for sending events in, plus CSV export/import, but there is no evidence of syncing or continuously exporting events to an external data warehouse, nor querying warehouse tables in-product. missing for 10: warehouse export/sync capability (e.g. BigQuery/Snowflake integration), continuous event streaming to external warehouse, in-product warehouse query support.

   • [claimed-docs] “Plausible Stats API is a read-only HTTP interface for viewing historical and real-time stats.”
   • [claimed-docs] “The /api/v2/query endpoint accepts simple and complex stats queries in the POST request body and returns the metrics as JSON.”
   • [claimed-docs] “Export stats: download your data”
   • [claimed-docs] “The Plausible Events API can be used to record pageviews and custom events. This is useful when tracking Android or iOS mobile apps, or for …”

   proof ↗⚑ flag