How mParticle’s scores are calculated
The full audit trail, recomputed from the verdict data at build time through the same code that produced the leaderboard: verdict × quality × story weight per cell, cells sum to dimension scores, dimensions blend into the PA Score. Every number on the product page is reproducible from this page alone; for why the formula looks like this, see the methodology.
verdict factors: full ×1.0 · partial ×0.6 · disputed ×0.3 · none ×0.0 · n/a excluded from both sides · cell points = weight × quality × factor · cell max = weight × 10
PA Score18/100
Agent-ready 29.3 × 0.30 = 8.79
API quality 0.0 × 0.20 = 0.00
Openness 12.0 × 0.20 = 2.40
Built-in AI 24.7 × 0.15 = 3.70
Automation 18.8 × 0.15 = 2.82
(8.79 + 0.00 + 2.40 + 3.70 + 2.82) ÷ (0.30 + 0.20 + 0.20 + 0.15 + 0.15) = 17.71 ÷ 1.00 = 17.7
Scores are stored to 1 decimal; the product page’s pills round to whole numbers for display. Each dimension below shows the stories, verdicts, and cited evidence behind its number.
Agent-ready29.3/100×0.30 of the PA blend
Outside-in: can YOUR agent reach and drive this product — API, MCP, CLI, headless runs, agent docs.
Point an agent at llms.txt or agent-oriented docsweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Run the product headlessly / in CI for automationweight 2
2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max
- [claimed-docs] https://docs.mparticle.com/developers/apis/http/“Warehouse Sync API Overview”
- [claimed-docs] https://docs.mparticle.com“Real-time API to drive user personalization”
- [claimed-docs] https://docs.mparticle.com/developers/apis/platform/audiences/“Audiences”
- [probe] https://docs.mparticle.com/developers/apis/http/“PROBE runtime (recorded 2026-09-08): mParticle's server-to-server events API is live and auth-gated — a keyless POST to https://s2s.mparticle.com/v2/events returned a bare HTTP 401, matching the documented key/secret basic authentication; the official @mparticle/web-sdk installed keylessly from npm and exports init.”
Plug MCP servers into this product so it can use their toolsweight 3
n/a — not applicable to this product: excluded from numerator and denominator
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Connect an agent via an official MCP serverweight 3
n/a — not applicable to this product: excluded from numerator and denominator
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Use an official CLIweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Drive the product through a documented public APIweight 3
3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max
- [claimed-docs] https://docs.mparticle.com“Send events directly to mParticle”
- [claimed-docs] https://docs.mparticle.com/developers/apis/http/“Warehouse Sync API Overview”
- [claimed-docs] https://docs.mparticle.com/developers/apis/platform/audiences/“Audiences”
- [claimed-docs] https://docs.mparticle.com“Client SDKs”
- [probe] https://docs.mparticle.com/developers/apis/http/“PROBE runtime (recorded 2026-09-08): mParticle's server-to-server events API is live and auth-gated — a keyless POST to https://s2s.mparticle.com/v2/events returned a bare HTTP 401, matching the documented key/secret basic authentication; the official @mparticle/web-sdk installed keylessly from npm and exports init.”
Issue scoped/least-privilege API credentials for an agentweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
- [probe] https://docs.mparticle.com/developers/apis/http/“PROBE runtime (recorded 2026-09-08): mParticle's server-to-server events API is live and auth-gated — a keyless POST to https://s2s.mparticle.com/v2/events returned a bare HTTP 401, matching the documented key/secret basic authentication; the official @mparticle/web-sdk installed keylessly from npm and exports init.”
- [claimed-docs] https://docs.mparticle.com/developers/apis/http/“Warehouse Sync API Overview”
Build against official SDKsweight 2
2 (weight) × 7 (quality) × 1.0 (full) = 14.0 of 20 max
- [claimed-docs] https://docs.mparticle.com“Client SDKs”
- [claimed-docs] https://docs.mparticle.com“Send your first event to mParticle”
- [claimed-docs] https://docs.mparticle.com“Send events directly to mParticle”
- [probe] https://docs.mparticle.com/developers/apis/http/“PROBE runtime (recorded 2026-09-08): mParticle's server-to-server events API is live and auth-gated — a keyless POST to https://s2s.mparticle.com/v2/events returned a bare HTTP 401, matching the documented key/secret basic authentication; the official @mparticle/web-sdk installed keylessly from npm and exports init.”
Subscribe to events via webhooksweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Agent-ready = 44.0 ÷ 150 × 100 = 29.3
API quality0.0/100×0.20 of the PA blend
The programmable surface once an agent is there — machine-readable spec, interactive docs, sandbox, versioning discipline.
Explore an interactive API reference with runnable examplesweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Download a machine-readable API spec (OpenAPI or equivalent)weight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Test against a sandbox environment without touching production dataweight 1
1 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 10 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Rely on versioned APIs with a documented deprecation policyweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
API quality = 0.0 ÷ 70 × 100 = 0.0
Openness12.0/100×0.20 of the PA blend
Can you leave, inspect, or self-host — data export, open source, portability.
Do everything through the API that I can do in the UIweight 2
2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max
- [claimed-docs] https://docs.mparticle.com/developers/apis/http/“Warehouse Sync API Overview”
- [claimed-docs] https://docs.mparticle.com/developers/apis/platform/audiences/“Audiences”
- [claimed-docs] https://docs.mparticle.com/guides/idsync/introduction/“IDSync is mParticle's identity resolution framework, enabling you to create a unified view of your customers, with improved data governance, policy, and security. IDSync gives visibility into, and control over, the management of known and anonymous user identities across apps and platforms.”
- [claimed-docs] https://docs.mparticle.com/guides/data-warehouse-sync/setup/“Warehouse Sync ingests data from your own warehouse into mParticle — documented setup flows cover Snowflake, Amazon Redshift, Google BigQuery, and Databricks ('Warehouse Sync uses the Databricks-to-Databricks Delta Sharing protocol to ingest data from Databricks into mParticle'), with a Warehouse Sync API, SQL reference, and data mapping.”
- [claimed-docs] https://docs.mparticle.com/guides/segmentation/audiences/connect-an-audience/“Once you have created an audience, you must connect it to an audience output where you can activate it. Visit our Integrations page and filter by Audience to view all audience outputs... Navigate to Data Platform > Setup > Directory, and click the card for your audience partner of choice.”
- [claimed-docs] https://docs.mparticle.com/guides/data-privacy-controls/“Manage your consent and opt-out privacy obligations under the GDPR and CCPA with Data Privacy Controls... Consent state powers both GDPR consent and CCPA data sale opt-out... Applying a forwarding rule of: Do not forward if CCPA Data sale opt out is present.”
- [probe] https://docs.mparticle.com/developers/apis/http/“PROBE runtime (recorded 2026-09-08): mParticle's server-to-server events API is live and auth-gated — a keyless POST to https://s2s.mparticle.com/v2/events returned a bare HTTP 401, matching the documented key/secret basic authentication; the official @mparticle/web-sdk installed keylessly from npm and exports init.”
Export all of my data in open formats and leaveweight 3
3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max
- [claimed-docs] https://docs.mparticle.com/developers/apis/http/“Warehouse Sync API Overview”
- [claimed-docs] https://docs.mparticle.com/guides/data-warehouse-sync/setup/“Warehouse Sync ingests data from your own warehouse into mParticle — documented setup flows cover Snowflake, Amazon Redshift, Google BigQuery, and Databricks ('Warehouse Sync uses the Databricks-to-Databricks Delta Sharing protocol to ingest data from Databricks into mParticle'), with a Warehouse Sync API, SQL reference, and data mapping.”
- [claimed-docs] https://docs.mparticle.com/guides/segmentation/audiences/connect-an-audience/“Once you have created an audience, you must connect it to an audience output where you can activate it. Visit our Integrations page and filter by Audience to view all audience outputs... Navigate to Data Platform > Setup > Directory, and click the card for your audience partner of choice.”
- [claimed-docs] https://www.mparticle.com/integrations/“Connect your customer data to the leading marketing, analytics, and data warehousing solutions with just a few clicks.”
Read the product's source under an open licenseweight 2
n/a — not applicable to this product: excluded from numerator and denominator
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Self-host the core productweight 3
n/a — not applicable to this product: excluded from numerator and denominator
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Openness = 6.0 ÷ 50 × 100 = 12.0
Built-in AI24.7/100×0.15 of the PA blend
Inside-out: how agentic the product itself is for its users — built-in assistants, autonomous features.
Get AI-generated insights and suggestions from my data inside the productweight 2
2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max
- [claimed-docs] https://www.mparticle.com“Score likelihood to churn, convert, or grow in value, then activate audiences before risk or opportunity passes.”
- [claimed-docs] https://www.mparticle.com“Describe the audience, journey, or growth goal. mParticle understands the customer data behind it, suggests the logic to use”
- [claimed-docs] https://www.mparticle.com“Describe the audience, journey, or growth goal. mParticle understands the customer data behind it, suggests the logic to use, and helps turn intent into revenue-driving activation.”
Set up automations that run autonomously in the backgroundweight 2
2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max
- [claimed-docs] https://docs.mparticle.com/developers/apis/platform/audiences/“Audiences”
- [claimed-docs] https://docs.mparticle.com/guides/composable-audiences/overview/“Composable Audiences”
- [claimed-docs] https://docs.mparticle.com/guides/segmentation/audiences/connect-an-audience/“Once you have created an audience, you must connect it to an audience output where you can activate it. Visit our Integrations page and filter by Audience to view all audience outputs... Navigate to Data Platform > Setup > Directory, and click the card for your audience partner of choice.”
- [claimed-docs] https://docs.mparticle.com/guides/data-privacy-controls/“Manage your consent and opt-out privacy obligations under the GDPR and CCPA with Data Privacy Controls... Consent state powers both GDPR consent and CCPA data sale opt-out... Applying a forwarding rule of: Do not forward if CCPA Data sale opt out is present.”
- [claimed-docs] https://docs.mparticle.com/guides/data-warehouse-sync/setup/“Warehouse Sync ingests data from your own warehouse into mParticle — documented setup flows cover Snowflake, Amazon Redshift, Google BigQuery, and Databricks ('Warehouse Sync uses the Databricks-to-Databricks Delta Sharing protocol to ingest data from Databricks into mParticle'), with a Warehouse Sync API, SQL reference, and data mapping.”
- [claimed-docs] https://www.mparticle.com“Describe the audience, journey, or growth goal. mParticle understands the customer data behind it, suggests the logic to use”
Delegate tasks to a built-in AI assistant inside the productweight 3
3 (weight) × 3 (quality) × 0.6 (partial) = 5.4 of 30 max
- [claimed-docs] https://www.mparticle.com“Describe the audience, journey, or growth goal. mParticle understands the customer data behind it, suggests the logic to use”
- [claimed-docs] https://www.mparticle.com“Describe the audience, journey, or growth goal. mParticle understands the customer data behind it, suggests the logic to use, and helps turn intent into revenue-driving activation.”
Operate the product with natural-language commandsweight 2
2 (weight) × 4 (quality) × 0.6 (partial) = 4.8 of 20 max
- [claimed-docs] https://www.mparticle.com“Describe the audience, journey, or growth goal. mParticle understands the customer data behind it, suggests the logic to use”
- [claimed-docs] https://www.mparticle.com“Describe the audience, journey, or growth goal. mParticle understands the customer data behind it, suggests the logic to use, and helps turn intent into revenue-driving activation.”
Built-in AI = 22.2 ÷ 90 × 100 = 24.7
Automation18.8/100×0.15 of the PA blend
Depth of automation primitives — rules, scheduling, bulk operations, webhooks.
Perform bulk operations across many items at onceweight 2
2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max
- [claimed-docs] https://docs.mparticle.com/guides/data-warehouse-sync/setup/“Warehouse Sync ingests data from your own warehouse into mParticle — documented setup flows cover Snowflake, Amazon Redshift, Google BigQuery, and Databricks ('Warehouse Sync uses the Databricks-to-Databricks Delta Sharing protocol to ingest data from Databricks into mParticle'), with a Warehouse Sync API, SQL reference, and data mapping.”
- [claimed-docs] https://docs.mparticle.com/developers/apis/http/“Warehouse Sync API Overview”
- [claimed-docs] https://docs.mparticle.com/developers/apis/platform/audiences/“Audiences”
- [claimed-docs] https://docs.mparticle.com/guides/data-privacy-controls/“Manage your consent and opt-out privacy obligations under the GDPR and CCPA with Data Privacy Controls... Consent state powers both GDPR consent and CCPA data sale opt-out... Applying a forwarding rule of: Do not forward if CCPA Data sale opt out is present.”
Define rules that trigger actions automatically on eventsweight 3
3 (weight) × 5 (quality) × 0.6 (partial) = 9.0 of 30 max
- [claimed-docs] https://docs.mparticle.com/guides/data-privacy-controls/“Manage your consent and opt-out privacy obligations under the GDPR and CCPA with Data Privacy Controls... Consent state powers both GDPR consent and CCPA data sale opt-out... Applying a forwarding rule of: Do not forward if CCPA Data sale opt out is present.”
- [claimed-docs] https://docs.mparticle.com/guides/segmentation/audiences/connect-an-audience/“Once you have created an audience, you must connect it to an audience output where you can activate it. Visit our Integrations page and filter by Audience to view all audience outputs... Navigate to Data Platform > Setup > Directory, and click the card for your audience partner of choice.”
- [claimed-docs] https://docs.mparticle.com/developers/apis/platform/audiences/“Audiences”
- [claimed-docs] https://docs.mparticle.com/guides/composable-audiences/overview/“Composable Audiences”
Schedule recurring jobs or workflowsweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Version, review, and roll back my automationsweight 1
1 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 10 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Automation = 15.0 ÷ 80 × 100 = 18.8