Mixpanel vs Plausible Analytics

Agent access

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

   weight 2 · round to Mixpanel
   Mixpanel✓fullprobed9/10

   A direct probe confirms Mixpanel serves a working llms.txt at docs.mixpanel.com/llms.txt (HTTP 200) with a curated index of docs, and Mixpanel also documents an MCP server for agent-native data access. Missing for 10: no independent/community corroboration of an agent actually consuming llms.txt successfully.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.mixpanel.com/llms.txt # Mixpanel - [What is Mixpanel?](https://docs.mixpanel.com/docs/what-is-mixp…”
   • [claimed-docs] “Mixpanel provides a hosted Model Context Protocol (MCP) server that gives AI assistants direct access to your Mixpanel data.”
   • [probe] “official MCP server documented at https://docs.mixpanel.com/docs/mcp”

   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 to Plausible Analytics
   Mixpanel~partialclaimed5/10

   Mixpanel exposes REST-based APIs (Raw Event Export, Query API, Engage API, JQL) that can be scripted and run headlessly/in CI for data export and querying, and warehouse connectors support automated syncs. However, there's no evidence of an official CLI, SDK for automation pipelines, or documented CI/CD integration pattern — the product is primarily a UI-driven analytics platform with API access as a secondary capability. missing for 10: dedicated CLI tool, CI/CD pipeline examples or GitHub Actions integration, headless automation SDK, and any hands-on/community evidence of running Mixpanel in automated pipelines.

   • [claimed-docs] “To export raw event data, use the Raw Event Export API. The events payload is returned as JSONL”
   • [claimed-docs] “The raw export API allows you to download your event data as it is received and stored within Mixpanel, complete with all event properties”
   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [claimed-docs] “The JQL JavaScript code must define a main() function. This JavaScript will be compiled, and the main() function will be executed by the que…”
   • [claimed-docs] “The Query API allows you to obtain the same calculated and formatted results that you see from a report in our web app.”
   • [claimed-docs] “you can sync data from data warehouses like Snowflake, BigQuery, Databricks, Redshift, and Postgres to Mixpanel”
   • [claimed-docs] “Use the Feature Flags API to assign your users to variants for experiments, rollout, and releases.”

   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 Mixpanel
   Mixpanel✓fullprobed8/10

   Mixpanel documents a hosted, official MCP server that gives AI assistants direct access to Mixpanel data, exposing tools like natural-language querying of events/funnels/retention and dashboard creation, confirmed by both docs and a live probe of the docs page. missing for 10: independent/hands-on verification of the MCP server working in practice, and details on authentication/scopes beyond the docs.

   • [claimed-docs] “Mixpanel provides a hosted Model Context Protocol (MCP) server that gives AI assistants direct access to your Mixpanel data.”
   • [claimed-docs] “Create-Dashboard | Create a new dashboard with text cards and reports”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required.”
   • [claimed-docs] “Once connected, you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation …”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required”
   • [probe] “official MCP server documented at https://docs.mixpanel.com/docs/mcp”

   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 drawn
   Mixpanel—none0/10

   The evidence pack documents Mixpanel's APIs, MCP server, JQL query language, and export methods, but contains no mention of an official command-line interface (CLI) tool for Mixpanel. A SaaS analytics platform could plausibly ship a CLI for automation/scripting, so the axis applies, but no evidence supports it.

   ⚑ 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 Mixpanel
   Mixpanel✓fullprobed8/10

   Mixpanel documents a comprehensive public REST-style API surface (Query API, Raw Event Export API, Engage API, Feature Flags API, JQL) plus a hosted MCP server that lets AI assistants query events, funnels, retention, and replays via natural language, giving AI-native users both programmatic and agentic access. missing for 10: no discoverable OpenAPI/Swagger spec (probe found only 404s) and no independent/hands-on corroboration of the MCP server or APIs actually working reliably.

   • [claimed-docs] “To export raw event data, use the Raw Event Export API. The events payload is returned as JSONL”
   • [claimed-docs] “The raw export API allows you to download your event data as it is received and stored within Mixpanel, complete with all event properties”
   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [claimed-docs] “The Query API allows you to obtain the same calculated and formatted results that you see from a report in our web app.”
   • [claimed-docs] “Use the Feature Flags API to assign your users to variants for experiments, rollout, and releases.”
   • [claimed-docs] “Create custom queries using Javascript code”
   • [claimed-docs] “Mixpanel provides a hosted Model Context Protocol (MCP) server that gives AI assistants direct access to your Mixpanel data.”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.mixpanel.com/openapi.json, https://docs.mixpanel.com/swagger.json, https://docs.mixpane…”
   • [probe] “official MCP server documented at https://docs.mixpanel.com/docs/mcp”

   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
   Mixpanel—none0/10

   Mixpanel offers an MCP server and various APIs, but the evidence pack contains no mention of scoped/least-privilege API keys, service accounts, or permission-limited tokens for agent use — only generic API/export/query docs and generic security incident commentary unrelated to credential scoping.

   ⚑ 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 Mixpanel
   Mixpanel~partialclaimed4/10

   Evidence shows official APIs (Query API, Raw/Engage Export API, Feature Flags API) and a JQL scripting interface for building custom analytics, which support programmatic integration, but there is no explicit mention of official client SDKs (e.g., JS/Python/mobile libraries), language coverage, or code samples that an AI-native builder would need. Missing for 10: explicit SDK documentation/list of languages, code snippets, GitHub repos, and independent corroboration of SDK reliability.

   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [claimed-docs] “The Query API allows you to obtain the same calculated and formatted results that you see from a report in our web app.”
   • [claimed-docs] “Use the Feature Flags API to assign your users to variants for experiments, rollout, and releases.”
   • [claimed-docs] “Create custom queries using Javascript code”
   • [claimed-docs] “The JQL JavaScript code must define a main() function. This JavaScript will be compiled, and the main() function will be executed by the que…”

   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
   Mixpanel—none0/10

   No evidence of Mixpanel offering webhooks to push/subscribe to events; the evidence only covers exports (raw export API, warehouse connectors, MCP server for querying data), which are pull-based, not event-driven webhook subscriptions.

   ⚑ 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 Mixpanel
   Mixpanel✓fullclaimed7/10

   Mixpanel's own docs/marketing describe AI-driven insight surfacing ('Agents monitor your product continuously, surface insights before you think to ask' and example outputs like 'Signups dipped 19% last week'), AI trend-spotting across replays/heatmaps, AI summaries of replay playlists, and natural-language querying via its MCP server. These directly match the story of AI-generated insights/suggestions inside the product. Missing for 10: independent/hands-on validation of these AI insight features' accuracy or usefulness, and more concrete product detail beyond marketing copy.

   • [claimed-docs] “Agents monitor your product continuously, surface insights before you think to ask, and tell your team exactly what to do next.”
   • [claimed-docs] “Diagnose what changed, and why, in seconds, delivered as a dashboard you and your team can keep working from.”
   • [claimed-docs] “Signups dipped 19% last week — a brief pullback against otherwise steady growth.”
   • [claimed-docs] “Use AI to spot trends across hundreds of replays and heatmaps, then zoom in yourself to get to the “why” behind every change.”
   • [claimed-docs] “Save playlists of replays based on events or properties, and quickly review with AI summaries, making it easy to revisit groups of replays t…”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required.”
   • [claimed-docs] “Once connected, you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation …”

   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 Mixpanel
   Mixpanel~partialclaimed3/10

   Mixpanel markets background 'Agents' that continuously monitor data and surface insights/recommendations autonomously (mixpanel-docs-44), suggesting some agentic automation capability, but there is no documentation on how a user actually configures or triggers these automations, what actions they can take, or independent confirmation they run unattended. missing for 10: setup/configuration docs for these agents, description of trigger conditions and autonomous actions, independent/hands-on evidence of them running in the background.

   • [claimed-docs] “Agents monitor your product continuously, surface insights before you think to ask, and tell your team exactly what to do next.”

   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 Mixpanel
   Mixpanel~partialclaimed4/10

   Mixpanel's marketing copy references built-in AI features such as 'Agents' that 'monitor your product continuously... and tell your team exactly what to do next,' AI-generated replay summaries, and AI trend-spotting across replays/heatmaps, suggesting some in-product AI assistant capability. However, these are thin marketing snippets rather than detailed product docs describing how a user actually delegates multi-step tasks to an assistant, and the only well-documented AI integration (MCP server) is for external AI assistants to query Mixpanel data, not a built-in assistant for users. Missing for 10: detailed first-party documentation of the 'Agents' feature and how tasks are delegated/executed, concrete UI/workflow examples, and independent hands-on corroboration.

   • [claimed-docs] “Agents monitor your product continuously, surface insights before you think to ask, and tell your team exactly what to do next.”
   • [claimed-docs] “Use AI to spot trends across hundreds of replays and heatmaps, then zoom in yourself to get to the “why” behind every change.”
   • [claimed-docs] “Save playlists of replays based on events or properties, and quickly review with AI summaries, making it easy to revisit groups of replays t…”
   • [claimed-docs] “Mixpanel provides a hosted Model Context Protocol (MCP) server that gives AI assistants direct access to your Mixpanel data.”

   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 Mixpanel
   Mixpanel✓fullprobed8/10

   Mixpanel documents a hosted MCP server that lets AI assistants query events, funnels, flows, retention, and session replays using natural language without dashboard navigation, directly matching the story of operating the product via NL commands. This is first-party documentation without independent hands-on corroboration of the NL experience itself. Missing for 10: independent/community validation of the MCP natural-language workflow in practice, and detail on the breadth/reliability of commands beyond the listed examples.

   • [claimed-docs] “Mixpanel provides a hosted Model Context Protocol (MCP) server that gives AI assistants direct access to your Mixpanel data.”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required.”
   • [claimed-docs] “Once connected, you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation …”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required”
   • [claimed-docs] “Create-Dashboard | Create a new dashboard with text cards and reports”
   • [probe] “official MCP server documented at https://docs.mixpanel.com/docs/mcp”

   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
   Mixpanel—none0/10

   While Mixpanel documents various APIs (Query API, Raw Export API, JQL), there is no evidence of an interactive API reference with runnable/try-it examples; a probe for a standard OpenAPI/Swagger spec returned 404s across all candidate paths, suggesting no interactive API console exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.mixpanel.com/openapi.json, https://docs.mixpanel.com/swagger.json, https://docs.mixpane…”
   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [claimed-docs] “The Query API allows you to obtain the same calculated and formatted results that you see from a report in our web app.”

   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 drawn
   Mixpanel—none0/10

   Mixpanel has extensive REST/Query/Export APIs, but direct probes for a machine-readable OpenAPI/Swagger spec (openapi.json, swagger.json, etc.) all returned 404, and no documentation evidence points to a downloadable spec file—only human-readable reference docs are cited.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.mixpanel.com/openapi.json, https://docs.mixpanel.com/swagger.json, https://docs.mixpane…”
   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [claimed-docs] “The Query API allows you to obtain the same calculated and formatted results that you see from a report in our web app.”

   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
   Mixpanel—none0/10

   No evidence pack item mentions a sandbox, test/dev project, or any mechanism to let an AI assistant query or write data without touching the production Mixpanel dataset — the MCP server docs (mixpanel-docs-10, mixpanel-docs-19) only describe querying live production data. Missing for 10: any documented sandbox/test project mode, data isolation for AI testing, or non-production environment support.

   • [claimed-docs] “Mixpanel provides a hosted Model Context Protocol (MCP) server that gives AI assistants direct access to your Mixpanel data.”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required.”
   • [probe] “official MCP server documented at https://docs.mixpanel.com/docs/mcp”

   proof ↗⚑ 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
   Mixpanel—none0/10

   No evidence pack item mentions API versioning, version numbers, or a documented deprecation/sunset policy for Mixpanel's APIs; the openapi.json probe returned 404s and no versioning docs were found. missing for 10: API version scheme documentation, deprecation/sunset policy, changelog or migration guides for breaking changes.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.mixpanel.com/openapi.json, https://docs.mixpanel.com/swagger.json, https://docs.mixpane…”

   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 Mixpanel
   Mixpanel~partialclaimed5/10

   Mixpanel offers APIs (Raw Event Export, JQL, Query API) that allow programmatic, high-volume data operations (bulk export, custom scripted queries, bulk filtering/cohort retrieval), and its MCP server lets AI agents query events, funnels, retention, etc. via natural language. However, the MCP tool list only shows single-item actions like 'Create-Dashboard', with no documented bulk-operation tools (e.g., batch create/update/delete across many items) for an AI-native agent to invoke. missing for 10: explicit AI-agent-invocable bulk operation tools (batch create/update/delete), independent confirmation of bulk actions succeeding at scale via MCP or API in practice.

   • [claimed-docs] “To export raw event data, use the Raw Event Export API. The events payload is returned as JSONL”
   • [claimed-docs] “To export raw event data, use the Raw Event Export API... This method is recommended for high volume exports.”
   • [claimed-docs] “Create custom queries using Javascript code”
   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [claimed-docs] “The JQL JavaScript code must define a main() function. This JavaScript will be compiled, and the main() function will be executed by the que…”
   • [claimed-docs] “Mixpanel provides a hosted Model Context Protocol (MCP) server that gives AI assistants direct access to your Mixpanel data.”
   • [claimed-docs] “Create-Dashboard | Create a new dashboard with text cards and reports”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required.”

   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
   Mixpanel—none0/10

   Mixpanel's evidence covers analytics reporting, exports, session replay, and an MCP server for querying data with natural language, but there is no documented feature for defining rule-based triggers that automatically fire actions on events (e.g., alerts, webhooks, workflow automation). The closest mention, 'Agents monitor your product continuously... tell your team what to do next' (mixpanel-docs-44), describes passive AI insight surfacing, not user-defined event-triggered automation.

   • [claimed-docs] “Agents monitor your product continuously, surface insights before you think to ask, and tell your team exactly what to do next.”
   • [claimed-docs] “Use the Feature Flags API to assign your users to variants for experiments, rollout, and releases.”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required.”

   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
   Mixpanel—none0/10

   Mixpanel is an analytics platform with export APIs, MCP server for queries, and dashboards, but there is no evidence of any capability to schedule recurring jobs or workflows (e.g., scheduled reports, cron-like automation, recurring data syncs beyond warehouse mirroring). No scheduling/automation feature is documented anywhere in the evidence pack.

   ⚑ 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 Mixpanel
   Mixpanel✓fullprobed8/10

   Mixpanel provides a documented hosted MCP server explicitly with a Create-Dashboard action ('Create a new dashboard with text cards and reports') plus natural-language querying of events, funnels, flows, retention, session replays, complementing the Query/Export APIs an agent could also use end-to-end. This directly matches the story of an agent building a dashboard via MCP or API, though there's no independent hands-on report confirming a real agent successfully completed this end-to-end. missing for 10: independent/hands-on verification of an agent actually building a dashboard via MCP or API, and more detail on API-only dashboard creation outside MCP.

   • [claimed-docs] “Mixpanel provides a hosted Model Context Protocol (MCP) server that gives AI assistants direct access to your Mixpanel data.”
   • [claimed-docs] “Create-Dashboard | Create a new dashboard with text cards and reports”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required.”
   • [claimed-docs] “Once connected, you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation …”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required”
   • [probe] “official MCP server documented at https://docs.mixpanel.com/docs/mcp”
   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [claimed-docs] “The Query API allows you to obtain the same calculated and formatted results that you see from a report in our web app.”

   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 Mixpanel
   Mixpanel~partialprobed3/10

   Mixpanel's hosted MCP server exposes a 'Create-Dashboard' tool that can create dashboards with text cards and reports, and lets you query events/funnels/retention/etc. programmatically, but this is MCP-tool access for AI assistants, not a documented general-purpose REST API for full CRUD (create/update/delete) of dashboards and saved insights. The Query API (docs-39, docs-43) only supports reading/filtering data, not creating or managing dashboard objects. Missing for 10: explicit REST API endpoints for creating, updating, and deleting dashboards/saved insights outside the MCP context, and any evidence of programmatic dashboard sharing/permissions management.

   • [claimed-docs] “Mixpanel provides a hosted Model Context Protocol (MCP) server that gives AI assistants direct access to your Mixpanel data.”
   • [claimed-docs] “Create-Dashboard | Create a new dashboard with text cards and reports”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required.”
   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [claimed-docs] “The Query API allows you to obtain the same calculated and formatted results that you see from a report in our web app.”
   • [probe] “official MCP server documented at https://docs.mixpanel.com/docs/mcp”

   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 Mixpanel
   Mixpanel~partialclaimed6/10

   Mixpanel's marketing/docs reference dashboards as an output (e.g. MCP tool 'Create-Dashboard' with text cards and reports, and marketing copy about 'a dashboard you and your team can keep working from'), implying saved insights can be composed into shareable team dashboards. However there is no first-party documentation detailing the dashboard-building UI, sharing/permissions workflow, or team collaboration mechanics beyond these brief mentions. Missing for 10: dedicated dashboard-creation docs, sharing/permission controls, and independent/hands-on evidence of team usage.

   • [claimed-docs] “Create-Dashboard | Create a new dashboard with text cards and reports”
   • [claimed-docs] “Diagnose what changed, and why, in seconds, delivered as a dashboard you and your team can keep working from.”
   • [claimed-docs] “Connect your product data to your company strategy in one interactive view, so teams can align faster, act with confidence, and stay account…”

   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
   Mixpanel~partialclaimed4/10

   Evidence shows Mixpanel has AI 'Agents' that monitor products continuously and surface anomalies (e.g., 'Signups dipped 19% last week') and can 'tell your team exactly what to do next,' suggesting some proactive alerting capability, but there is no explicit documentation of a dashboard subscription mechanism or configurable alert thresholds for PMs. missing for 10: explicit dashboard subscription feature, alert configuration/thresholds, delivery channels (email/Slack) for alerts.

   • [claimed-docs] “Agents monitor your product continuously, surface insights before you think to ask, and tell your team exactly what to do next.”
   • [claimed-docs] “Signups dipped 19% last week — a brief pullback against otherwise steady growth.”
   • [claimed-docs] “Diagnose what changed, and why, in seconds, delivered as a dashboard you and your team can keep working from.”

   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
   Mixpanel~partialclaimed6/10

   Mixpanel supports ingesting historical/bulk data via Warehouse Connectors (syncing from Snowflake, BigQuery, Databricks, Redshift, Postgres) and has a general import/ingestion API implied by its event JSON model, but the evidence pack lacks explicit documentation of a dedicated bulk 'Import API' for historical event backfill or migration from another analytics tool. missing for 10: explicit historical/bulk import API docs, guidance on importing from other analytics platforms (e.g., Amplitude/Segment migration), and confirmation of backdated event timestamp support.

   • [claimed-docs] “you can sync data from data warehouses like Snowflake, BigQuery, Databricks, Redshift, and Postgres to Mixpanel”
   • [claimed-docs] “With Warehouse Connectors, you can sync data from data warehouses like Snowflake, BigQuery, Databricks, Redshift, and Postgres to Mixpanel.”
   • [claimed-docs] “you can sync data from data warehouses like Snowflake, BigQuery, Databricks, Redshift, and Postgres to Mixpanel.”
   • [claimed-docs] “SET CHANGE\TRACKING = TRUE; # or ALTER VIEW SET CHANGE\TRACKING = TRUE; \\\ Mixpanel will create and manage the necessary STREAM objects in …”
   • [claimed-docs] “SET TBLPROPERTIES (delta.enableChangeDataFeed = true); \\\ \\Considerations when using Mirror with Databricks:\\ \ Mirror is not supported o…”
   • [claimed-docs] “Every data point sent to Mixpanel is stored as JSON in our data store.”

   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 drawn
   Mixpanel—none0/10

   The evidence pack contains no mention of Mixpanel's identity resolution features (e.g., identify(), $merge, alias, distinct_id merging) for tying anonymous pre-signup activity to an identified user profile. While this is a well-known Mixpanel capability generally, none of the provided docs, community posts, or probes reference it, so per the evidence-only rule this must be judged as unsupported.

   ⚑ 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 to Plausible Analytics
   Mixpanel—none0/10

   The evidence pack covers Mixpanel's event model, funnels, retention, exports, warehouse connectors, and session replay, but nowhere documents an autocapture/autotrack feature that automatically records clicks, pageviews, and form interactions without custom instrumentation. Session Replay (mixpanel-docs-4/23/28/33) records video sessions but does not equate to automatic event-level tracking for analytics events.

   ⚑ 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 Plausible Analytics
   Mixpanel—none0/10

   The evidence pack never mentions any specific SDKs (JavaScript, iOS, Android, Python, Java, etc.) for sending events from web, mobile, or backend apps — it only discusses tracking methods generically (warehouse connectors, event ingestion server rewrite, export APIs) without documenting an SDK catalog. Missing for 10: explicit mention of official web SDK, mobile SDKs (iOS/Android), backend/server SDKs, and any platform coverage list.

   • [community] “Mixpanel rewrote their event-ingestion server from Erlang to Python after two years, citing that 'the code has become difficult to maintain.…”
   • [claimed-docs] “Every data point sent to Mixpanel is stored as JSON in our data store.”
   • [claimed-docs] “SET CHANGE\TRACKING = TRUE; # or ALTER VIEW SET CHANGE\TRACKING = TRUE; \\\ Mixpanel will create and manage the necessary STREAM objects in …”

   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 Mixpanel
   Mixpanel~partialclaimed5/10

   Mixpanel documents a Feature Flags API for assigning variants to experiments/rollouts and marketing copy claims users can 'design, run, and analyze tests and rollouts' alongside analytics, indicating some experimentation capability. However, there is no explicit documentation of goal-metric configuration or statistical-significance calculation/reporting for A/B tests. missing for 10: explicit stat-sig reporting docs, goal-metric setup workflow, independent corroboration of experiment results UI.

   • [claimed-docs] “Close the gap between shipping fast and shipping right by designing, running, and analyzing tests and rollouts in the same place you do all …”
   • [claimed-docs] “Use the Feature Flags API to assign your users to variants for experiments, rollout, and releases.”

   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 drawn
   Mixpanel✓fullcommunity8/10

   Mixpanel's funnels report explicitly measures conversion through a series of events, properties enable filtering/cohorting, and the Query API supports breakdowns and filtering of events; marketing copy also touts discovering 'critical drop-off points.' Missing for 10: a hands-on community example specifically confirming breakdown usage inside funnels (only adjacent Flow feature has direct user testimonials) and independent verification of the breakdown UI itself.

   • [claimed-docs] “Measure conversions through a series of events”
   • [claimed-docs] “Properties allow you to create groups of users (aka cohorts) and also enable you to filter for certain events or users.”
   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [claimed-docs] “Discover critical drop-off points and calibrate user journeys to optimize every touchpoint for maximum engagement, retention, and growth.”
   • [community] “On Mixpanel's Flow feature: 'This is the coolest thing I have seen in Analytics for a long time. This really gets to the heart of most of th…”

   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 to Mixpanel
   Mixpanel~partialcommunity4/10

   Mixpanel does support account/company-level (group) analytics for B2B use cases, but the evidence pack lacks first-party docs describing this feature directly — the only confirmation comes from a community report noting that group-level/account-level analytics 'useful for B2B SaaS' exists but is 'tucked away on one of Mixpanel's higher price plans,' limiting access for many customers. Missing for 10: first-party documentation of the Group Analytics feature, details on setup/limits, and independent hands-on validation beyond the pricing-gate complaint.

   • [community] “Group-level/account-level analytics useful for B2B SaaS is 'tucked away on one of Mixpanel's higher price plans,' limiting access for smalle…”

   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 Mixpanel
   Mixpanel✓fullclaimed8/10

   Mixpanel's Retention report explicitly assesses user engagement over time, and properties/cohorts allow filtering and grouping of users for behavioral segmentation, directly matching the story. Documentation confirms retention analysis, cohort creation via properties, and query/export APIs that support slicing by cohort. Missing for 10: independent hands-on evidence of retention-by-cohort slicing in practice and no community corroboration specifically on retention feature usability.

   • [claimed-docs] “The Retention report in Mixpanel is designed to assess user engagement over a specified period of time.”
   • [claimed-docs] “Properties allow you to create groups of users (aka cohorts) and also enable you to filter for certain events or users.”
   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [claimed-docs] “The Query API allows you to obtain the same calculated and formatted results that you see from a report in our web app.”

   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 Mixpanel
   Mixpanel✓fullcommunity7/10

   Mixpanel's 'Flows' report is explicitly designed to visualize the paths users take before/after a given event, and this is corroborated by independent hands-on community praise ('gets to the heart of most of the information you need on user flows') as well as the docs' framing around discovering drop-off points and calibrating user journeys. However, community feedback also flags real friction (hover-based UI hard to use, requests to unify page-view vs custom events) and no probe confirms path exploration works flawlessly today. missing for 10: recent independent corroboration of UI usability, explicit documentation of 'before event' path exploration (most docs emphasize funnels/retention/after-event flows).

   • [claimed-docs] “Discover critical drop-off points and calibrate user journeys to optimize every touchpoint for maximum engagement, retention, and growth.”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required.”
   • [community] “On Mixpanel's Flow feature: 'This is the coolest thing I have seen in Analytics for a long time. This really gets to the heart of most of th…”
   • [community] “Paying Mixpanel customer feedback on Flow: 'My biggest request is the same as the biggest request for the rest of Mixpanel: remove the wall …”
   • [community] “Usability complaints about Flow's hover-based UI: 'Requires too much effort (rolling over hover states) to dig out information' and is 'Very…”

   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 Mixpanel
   Mixpanel✓fullcommunity8/10

   Mixpanel's core product is self-serve funnels ('measure conversions through a series of events') and drop-off analysis, with docs explicitly framing this as a no-code, click-based, self-serve capability ('interactive reports that let you query and visualize the results with just a few clicks', 'Discover critical drop-off points'), plus Session Replay to explore 'why customers drop off' — all designed for non-analyst self-service. Community evidence corroborates the self-serve UI power ('PMs spend hours in mixpanel quickly generating custom report after custom report') though also notes UI friction in an older Flow feature. Missing for 10: no first-party founder/non-technical-user case study specifically validating a founder (not a PM/analyst) independently diagnosing activation drop-off, and one community note flags usability complaints on a related flow visualization.

   • [claimed-docs] “Measure conversions through a series of events”
   • [claimed-docs] “Discover critical drop-off points and calibrate user journeys to optimize every touchpoint for maximum engagement, retention, and growth.”
   • [claimed-docs] “It enables you to track how users engage with your product and analyze this data with interactive reports that let you query and visualize t…”
   • [claimed-docs] “Now, with Mixpanel Session Replay, you can quickly follow up by exploring **why** customers drop off.”
   • [community] “'Getting a front end anywhere near as slick and powerful as Mixpanel's is an even bigger challenge than the data pipeline... I've seen PMs s…”
   • [community] “On Mixpanel's Flow feature: 'This is the coolest thing I have seen in Analytics for a long time. This really gets to the heart of most of th…”
   • [community] “Usability complaints about Flow's hover-based UI: 'Requires too much effort (rolling over hover states) to dig out information' and is 'Very…”

   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 drawn
   Mixpanel—none0/10

   Evidence shows only inbound warehouse syncing (Snowflake/BigQuery/etc. into Mixpanel) and pull-based export APIs (Raw Event Export, Query API, CSV), none of which describe pushing/streaming events out to CRM systems, ad platforms, or webhooks. The partner integrations directory lists third-party platforms (mParticle, Census, Vendo) but their descriptions frame them as bringing data INTO Mixpanel, not Mixpanel streaming events out to them.

   • [claimed-docs] “you can sync data from data warehouses like Snowflake, BigQuery, Databricks, Redshift, and Postgres to Mixpanel”
   • [claimed-docs] “To export raw event data, use the Raw Event Export API. The events payload is returned as JSONL”
   • [claimed-docs] “With Warehouse Connectors, you can sync data from data warehouses like Snowflake, BigQuery, Databricks, Redshift, and Postgres to Mixpanel.”
   • [claimed-docs] “You can export data from your project using a variety of methods, including lightweight CSVs generated from the UI, large volume raw data ex…”
   • [claimed-docs] “mParticle is an AI Customer Data Platform that powers the entire marketing stack with real-time customer data. Companies like NBCUniversal, …”
   • [claimed-docs] “Census is the #1 Data Activation platform that unites revenue teams around a single source of truth in the cloud data warehouse. Our no-code…”
   • [claimed-docs] “Vendo is a marketing data platform for growth teams. It connects the tools you already use — Shopify, Google Ads, Meta Ads, TikTok, Klaviyo,…”

   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 Mixpanel
   Mixpanel~partialclaimed6/10

   Mixpanel exposes a broad API surface—Query API (mirrors report results), Raw Export/Engage APIs, Feature Flags API, JQL for custom queries, and an MCP server that can create dashboards and query via natural language—giving strong programmatic coverage of most analytics workflows (mixpanel-docs-39, mixpanel-docs-43, mixpanel-docs-36, mixpanel-docs-37, mixpanel-docs-10, mixpanel-docs-11). However, some UI-only capabilities are explicitly documented, e.g. Session Replay sampling is managed 'directly from the Mixpanel UI — no code changes or redeployment required' (mixpanel-docs-5, mixpanel-docs-29), indicating a gap rather than full UI/API parity. Missing for 10: explicit confirmation that dashboard configuration, session-replay settings, and all admin/UI-only controls are fully API-accessible, and independent verification of complete parity beyond vendor docs.

   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [claimed-docs] “The Query API allows you to obtain the same calculated and formatted results that you see from a report in our web app.”
   • [claimed-docs] “Use the Feature Flags API to assign your users to variants for experiments, rollout, and releases.”
   • [claimed-docs] “Create custom queries using Javascript code”
   • [claimed-docs] “Mixpanel provides a hosted Model Context Protocol (MCP) server that gives AI assistants direct access to your Mixpanel data.”
   • [claimed-docs] “Create-Dashboard | Create a new dashboard with text cards and reports”
   • [claimed-docs] “teams can manage Session Replay sampling directly from the Mixpanel UI — no code changes or redeployment required.”
   • [claimed-docs] “teams can manage Session Replay sampling directly from the Mixpanel UI — no code changes or redeployment required”

   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 Mixpanel
   Mixpanel✓fullcommunity8/10

   Mixpanel documents multiple open-format export paths — Raw Event Export API returning JSONL (mixpanel-docs-7,9,18,31), CSV export from the UI (mixpanel-docs-25,30), Engage API for user profiles (mixpanel-docs-8), and Query API for aggregated data (mixpanel-docs-39,43) — enabling a user to pull out event, profile, and query data in standard formats. Community commentary even praises Mixpanel's export policy as 'great' when discussing data ownership (mixpanel-comm-13), corroborating that full data export works in practice. Missing for 10: no explicit statement of exporting *all* config/dashboard/schema metadata, and no independent bulk-export walkthrough beyond forum anecdote.

   • [claimed-docs] “To export raw event data, use the Raw Event Export API. The events payload is returned as JSONL”
   • [claimed-docs] “The raw export API allows you to download your event data as it is received and stored within Mixpanel, complete with all event properties”
   • [claimed-docs] “Every data point sent to Mixpanel is stored as JSON in our data store.”
   • [claimed-docs] “You can export data from your project using a variety of methods, including lightweight CSVs generated from the UI, large volume raw data ex…”
   • [claimed-docs] “You may export small batches of events as a CSV for use in quick analysis by navigating to the Events tab”
   • [claimed-docs] “To export User Profile data, use the Engage API.”
   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [community] “Complaint about vendor lock-in: 'The tool is lovely, their export policy is great, but there's something about actually owning your data' — …”

   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
   Mixpanel—none0/10

   Mixpanel is closed-source SaaS; no evidence of any open-licensed source code repository or license grant is present in the evidence pack, only product docs, integrations, and community commentary unrelated to source licensing.

   ⚑ 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
   Mixpanel—none0/10

   Mixpanel is offered exclusively as a hosted SaaS product; no evidence pack item mentions a self-hosted or on-premise deployment option, source code availability, or Docker/Kubernetes install path. Absence of evidence for this applicable capability yields a 'none' verdict.

   ⚑ 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
   Mixpanel—none0/10

   The evidence pack contains no documentation on cookieless tracking, first-party identity resolution, or reducing/avoiding cookie consent banners — Mixpanel's docs focus on events, funnels, retention, session replay, exports, and MCP, none of which address cookie usage or consent-banner avoidance. Missing for 10: any statement on cookieless tracking methods, first-party data collection design, or consent-banner impact.

   ⚑ 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 Mixpanel
   Mixpanel✓fullclaimed7/10

   Mixpanel documents an EU Data Residency Program allowing customers to process and store personal data in Europe, directly addressing regional data residency choice [mixpanel-docs-38], backed by GDPR-oriented deletion/retrieval APIs [mixpanel-docs-12]. Missing for 10: no detail on which regions beyond EU are supported, no independent/hands-on confirmation of the residency mechanics or migration process, and no mention of per-project region selection UI.

   • [claimed-docs] “Mixpanel provides you with the option to process and store your customers' personal data in Europe via our EU Data Residency Program.”
   • [claimed-docs] “Mixpanel deletion and retrieval APIs are in place to help Mixpanel implementations meet the requirements outlined by the General Data Protec…”

   proof ↗⚑ 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
   Mixpanel—none0/10

   No evidence in the pack addresses AI-training opt-out or any policy preventing customer data from being used to train AI models; privacy docs only mention GDPR deletion/retrieval APIs and EU data residency, not AI-training exclusion.

   • [claimed-docs] “Mixpanel deletion and retrieval APIs are in place to help Mixpanel implementations meet the requirements outlined by the General Data Protec…”
   • [claimed-docs] “Mixpanel provides you with the option to process and store your customers' personal data in Europe via our EU Data Residency Program.”

   proof ↗⚑ 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 Mixpanel
   Mixpanel✓fullclaimed7/10

   Mixpanel documents explicit deletion and retrieval APIs built to meet GDPR requirements, plus an EU Data Residency Program for regional data storage/processing, giving users concrete levers to control retention and deletion of their data ([mixpanel-docs-12], [mixpanel-docs-38]). Missing for 10: independent/hands-on verification of the deletion APIs actually working, and documentation of configurable retention windows or automated data-expiry settings beyond GDPR compliance language.

   • [claimed-docs] “Mixpanel deletion and retrieval APIs are in place to help Mixpanel implementations meet the requirements outlined by the General Data Protec…”
   • [claimed-docs] “Mixpanel provides you with the option to process and store your customers' personal data in Europe via our EU Data Residency Program.”

   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 drawn
   Mixpanel—none0/10

   Evidence pack shows Mixpanel's GDPR deletion/retrieval APIs and EU data residency options for customer data stored in Mixpanel, but there is no mention of any mechanism for an AI-native user (e.g., of the MCP server or AI features) to opt out of telemetry/usage tracking collected about their own interactions with Mixpanel's tools.

   • [claimed-docs] “Mixpanel deletion and retrieval APIs are in place to help Mixpanel implementations meet the requirements outlined by the General Data Protec…”
   • [claimed-docs] “Mixpanel provides you with the option to process and store your customers' personal data in Europe via our EU Data Residency Program.”

   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 Mixpanel
   Mixpanel✓fullprobed8/10

   Mixpanel documents a hosted MCP server that lets AI assistants query events, funnels, flows, retention, and session replays via natural language (no dashboard navigation), plus a Query API for filtering/breaking down events, cohorts, and profiles, and a raw export/JQL API for deeper queries—together covering agent-driven growth Q&A over live product data. Missing for 10: independent/hands-on verification of MCP server reliability or accuracy, and no evidence of complex ad-hoc SQL-like warehouse querying via MCP beyond the documented report types.

   • [claimed-docs] “Mixpanel provides a hosted Model Context Protocol (MCP) server that gives AI assistants direct access to your Mixpanel data.”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required.”
   • [claimed-docs] “Once connected, you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation …”
   • [claimed-docs] “you can query events, funnels, flows, retention, session replays, and more using natural language — no dashboard navigation required”
   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [claimed-docs] “The Query API allows you to obtain the same calculated and formatted results that you see from a report in our web app.”
   • [probe] “official MCP server documented at https://docs.mixpanel.com/docs/mcp”

   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 Mixpanel
   Mixpanel✓fullclaimed9/10

   Mixpanel documents a Query API for analytical queries (filter/breakdown events, cohorts, activity streams) and a separate Raw Event Export API returning full JSONL event data, plus JQL for custom JS-based queries — directly matching the query/export API story. Missing for 10: no independent/hands-on developer corroboration of API reliability or rate limits beyond first-party docs.

   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [claimed-docs] “The Query API allows you to obtain the same calculated and formatted results that you see from a report in our web app.”
   • [claimed-docs] “To export raw event data, use the Raw Event Export API. The events payload is returned as JSONL”
   • [claimed-docs] “The raw export API allows you to download your event data as it is received and stored within Mixpanel, complete with all event properties”
   • [claimed-docs] “To export raw event data, use the Raw Event Export API... This method is recommended for high volume exports.”
   • [claimed-docs] “Create custom queries using Javascript code”
   • [claimed-docs] “The JQL JavaScript code must define a main() function. This JavaScript will be compiled, and the main() function will be executed by the que…”

   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 to Mixpanel
   Mixpanel~partialclaimed5/10

   Mixpanel doesn't offer SQL, but its JQL (JavaScript Query Language) lets developers write custom code queries against raw event data directly in the platform, and the Query API can filter/break down events and return activity streams — a functional but not syntactic SQL-equivalent. missing for 10: no actual SQL support, no evidence JQL/Query API is positioned as a full SQL-equivalent, and no independent/hands-on corroboration of its expressiveness for raw-event querying.

   • [claimed-docs] “Create custom queries using Javascript code”
   • [claimed-docs] “The JQL JavaScript code must define a main() function. This JavaScript will be compiled, and the main() function will be executed by the que…”
   • [claimed-docs] “The Mixpanel Query API endpoints can: Filter or break down Events * Return user profiles. * Return an activity/event stream for a user. * Re…”
   • [claimed-docs] “The Query API allows you to obtain the same calculated and formatted results that you see from a report in our web app.”

   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 Mixpanel
   Mixpanel~partialclaimed7/10

   Mixpanel's Warehouse Connectors let you sync data from Snowflake, BigQuery, Databricks, Redshift, and Postgres into Mixpanel, and the Raw Event Export API (JSONL, recommended for high-volume) lets you pull events out for warehouse loading, satisfying both directions of the story at a basic level. However, continuous/automated export to a warehouse is not natively built-in as a managed reverse-sync pipeline—Mixpanel's own partner directory lists third-party Reverse ETL tools like Census for pushing Mixpanel data to warehouses, implying continuous outbound sync relies on partner tooling rather than a first-party feature. Missing for 10: evidence of a native continuous/scheduled export-to-warehouse pipeline (not just an on-demand API), and independent/hands-on confirmation that Warehouse Connectors and export API work reliably at scale.

   • [claimed-docs] “you can sync data from data warehouses like Snowflake, BigQuery, Databricks, Redshift, and Postgres to Mixpanel”
   • [claimed-docs] “With Warehouse Connectors, you can sync data from data warehouses like Snowflake, BigQuery, Databricks, Redshift, and Postgres to Mixpanel.”
   • [claimed-docs] “you can sync data from data warehouses like Snowflake, BigQuery, Databricks, Redshift, and Postgres to Mixpanel.”
   • [claimed-docs] “To export raw event data, use the Raw Event Export API. The events payload is returned as JSONL”
   • [claimed-docs] “The raw export API allows you to download your event data as it is received and stored within Mixpanel, complete with all event properties”
   • [claimed-docs] “To export raw event data, use the Raw Event Export API... This method is recommended for high volume exports.”
   • [claimed-docs] “You can export data from your project using a variety of methods, including lightweight CSVs generated from the UI, large volume raw data ex…”
   • [claimed-docs] “Census is the #1 Data Activation platform that unites revenue teams around a single source of truth in the cloud data warehouse. Our no-code…”
   • [claimed-docs] “SET CHANGE\TRACKING = TRUE; # or ALTER VIEW SET CHANGE\TRACKING = TRUE; \\\ Mixpanel will create and manage the necessary STREAM objects in …”
   • [claimed-docs] “SET TBLPROPERTIES (delta.enableChangeDataFeed = true); \\\ \\Considerations when using Mirror with Databricks:\\ \ Mirror is not supported o…”

   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