Rank #5 of 5 in Customer Data Platforms
Access
Showcase


Try itExperimental
See what an agent can do with mParticle before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -si -X POST https://s2s.mparticle.com/v2/events -H 'Content-Type: application/json' -d '{}' # live events API answers 401 keylesslyrecorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Ai cdp — stories about ai cdp in this arenaAi cdpevidence →
Stories about ai cdp in this arena
Audiences activation — stories about audiences activation in this arenaAudiences activationevidence →
Stories about audiences activation in this arena
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Destinations integrations — stories about destinations integrations in this arenaDestinations integrationsevidence →
Stories about destinations integrations in this arena
Event collection — stories about event collection in this arenaEvent collectionevidence →
Stories about event collection in this arena
Identity resolution — stories about identity resolution in this arenaIdentity resolutionevidence →
Stories about identity resolution in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pipeline observability — stories about pipeline observability in this arenaPipeline observabilityevidence →
Stories about pipeline observability in this arena
Privacy consent — stories about privacy consent in this arenaPrivacy consentevidence →
Stories about privacy consent in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Replay portability — stories about replay portability in this arenaReplay portabilityevidence →
Stories about replay portability in this arena
Transformations quality — stories about transformations quality in this arenaTransformations qualityevidence →
Stories about transformations quality in this arena
Warehouse native — stories about warehouse native in this arenaWarehouse nativeevidence →
Stories about warehouse native in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where mParticle stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Webhooks · Scoped API keys · Machine-readable spec · Versioning policy · API sandbox · Official CLI · Full data export
Subscribe to events via webhooks
—–
Build against official SDKs
✓7/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
n/an/a
Download a machine-readable API spec (OpenAPI or equivalent)
—–
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
—–
Explore an interactive API reference with runnable examples
—–
Docs for agents
Point an agent at llms.txt or agent-oriented docs
—–
Agentic features
Delegate tasks to a built-in AI assistant inside the product
~3/10
Operate the product with natural-language commands
~4/10
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
~5/10
Set up automations that run autonomously in the background
~5/10
Ai cdp — stories about ai cdp in this arenaAi cdp
Stories about ai cdp in this arena
An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the loop
~4/10
An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP server
~4/10
Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schema
~5/10
AI decisioning agents pick messages, timing, and channels per customer autonomously within guardrails I set, with measurable lift
—0/10
Audiences activation — stories about audiences activation in this arenaAudiences activation
Stories about audiences activation in this arena
Audiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-time
~6/10
Build audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activating
~3/10
Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targeting
~5/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Destinations integrations — stories about destinations integrations in this arenaDestinations integrations
Stories about destinations integrations in this arena
Event collection — stories about event collection in this arenaEvent collection
Stories about event collection in this arena
Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees
~6/10
Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)
~7/10
Pull customer data in from third-party cloud apps and feeds — not just my own instrumented apps
~7/10
Identity resolution — stories about identity resolution in this arenaIdentity resolution
Stories about identity resolution in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pipeline observability — stories about pipeline observability in this arenaPipeline observability
Stories about pipeline observability in this arena
Privacy consent — stories about privacy consent in this arenaPrivacy consent
Stories about privacy consent in this arena
User consent is captured and enforced across destinations — opt-outs and consent categories are honored downstream automatically
✓8/10
Process user deletion and suppression requests (GDPR/CCPA) and have them forwarded to connected destinations
~6/10
Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributes
~5/10
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Replay portability — stories about replay portability in this arenaReplay portability
Stories about replay portability in this arena
Transformations quality — stories about transformations quality in this arenaTransformations quality
Stories about transformations quality in this arena
Warehouse native — stories about warehouse native in this arenaWarehouse native
Stories about warehouse native in this arena
Sorted by importance (agentic first) (high → low) · 51/51 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 3/10 | Cclaimed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | none | untested | none yet | |
Anonymous and known activity stitches into one customer profile across devices, with documented and configurable identity-resolution rules C Stitching | data engineer | Identity resolution — stories about identity resolution in this arenaIdentity resolution | 3 | full | 8/10 | Cclaimed | |
User consent is captured and enforced across destinations — opt-outs and consent categories are honored downstream automatically C Consent | privacy lead | Privacy consent — stories about privacy consent in this arenaPrivacy consent | 3 | full | 8/10 | Cclaimed | |
Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page) C Sdks | data engineer | Event collection — stories about event collection in this arenaEvent collection | 3 | partial | 7/10 | Tprobed | |
Route events to a large catalog of documented destination integrations with per-destination mapping and filtering C Destinations | data engineer | Destinations integrations — stories about destinations integrations in this arenaDestinations integrations | 3 | partial | 7/10 | Xcommunity | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 5/10 | Cclaimed | |
An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP server C Agent pipeline | ai-native user | Ai cdp — stories about ai cdp in this arenaAi cdp | 3 | partial | 4/10 | Cclaimed | |
An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the loop C Agent audiences | ai-native user | Ai cdp — stories about ai cdp in this arenaAi cdp | 3 | partial | 4/10 | Cclaimed | |
Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I control C Warehouse sync | data engineer | Warehouse native — stories about warehouse native in this arenaWarehouse native | 3 | partial | 4/10 | Cclaimed | |
Build audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activating C Audiences | marketer | Audiences activation — stories about audiences activation in this arenaAudiences activation | 3 | partial | 3/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | n/a | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
Audiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-time C Activation | marketer | Audiences activation — stories about audiences activation in this arenaAudiences activation | 2 | partial | 6/10 | Cclaimed | |
Process user deletion and suppression requests (GDPR/CCPA) and have them forwarded to connected destinations C Deletion | privacy lead | Privacy consent — stories about privacy consent in this arenaPrivacy consent | 2 | partial | 6/10 | Cclaimed | |
Query unified customer profiles — traits, identifiers, event history — through a documented profile API or store C Profiles | data engineer | Identity resolution — stories about identity resolution in this arenaIdentity resolution | 2 | partial | 6/10 | Cclaimed | |
Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees C Ingest | data engineer | Event collection — stories about event collection in this arenaEvent collection | 2 | partial | 6/10 | Tprobed | |
Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targeting C Traits | marketer | Audiences activation — stories about audiences activation in this arenaAudiences activation | 2 | partial | 5/10 | Cclaimed | |
Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributes C Pii controls | privacy lead | Privacy consent — stories about privacy consent in this arenaPrivacy consent | 2 | partial | 5/10 | Cclaimed | |
Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schema C Ai assist | ai-native user | Ai cdp — stories about ai cdp in this arenaAi cdp | 2 | partial | 5/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Cclaimed | |
A tracking plan or schema is enforced — violating events get flagged, blocked, or quarantined instead of silently corrupting downstream data C Data quality | data engineer | Transformations quality — stories about transformations quality in this arenaTransformations quality | 2 | partial | 4/10 | Cclaimed | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 4/10 | Cclaimed | |
Replay archived events into a new destination or backfill history when a tool is added or a pipeline breaks C Replay | data engineer | Replay portability — stories about replay portability in this arenaReplay portability | 2 | partial | 4/10 | Cclaimed | |
Run warehouse-native: define models and audiences on tables already in my warehouse and activate them without re-collecting the data (reverse ETL) C Composable | data engineer | Warehouse native — stories about warehouse native in this arenaWarehouse native | 2 | partial | 4/10 | Cclaimed | |
Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinations C Transformations | data engineer | Transformations quality — stories about transformations quality in this arenaTransformations quality | 2 | partial | 4/10 | Cclaimed | |
AI decisioning agents pick messages, timing, and channels per customer autonomously within guardrails I set, with measurable lift C Ai decisioning | ai-native user | Ai cdp — stories about ai cdp in this arenaAi cdp | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Watch events flow live and diagnose delivery failures per destination — debugger views, delivery metrics, and alerting C Observability | data engineer | Pipeline observability — stories about pipeline observability in this arenaPipeline observability | 2 | none | 0/10 | ||
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | n/a | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Pull customer data in from third-party cloud apps and feeds — not just my own instrumented apps C Sources | data engineer | Event collection — stories about event collection in this arenaEvent collection | 1 | partial | 7/10 | Tprobed | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 42 stories with headroom
What would move mParticle’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
partialq3/10moves Built-in AIimpact 31.5
Missing: evidence of a general-purpose conversational assistant, documentation of its scope/capabilities beyond audience building, and any independent/hands-on corroboration of it working.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
mParticle documents APIs for sending data in and forwarding it to partner integrations (docs-11, docs-x2) and a Warehouse Sync feature, but the evidence shows Warehouse Sync only ingests data from a customer's warehouse into mParticle (docs-x4), not a comprehensive open-format export/backup of all stored customer data for leaving the platform.
Agenticness — how well agents can access and operate the productPoint an agent at llms.txt or agent-oriented docs
nonemoves agent-readyimpact 30
Missing: llms.txt file, agent-oriented doc structure, any mention of AI-agent/LLM crawling support.
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
Missing: any mention of an official mParticle CLI, its installation, command reference, or usage examples.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Evidence only shows basic key/secret authentication gating mParticle's events API (401 on keyless POST), with no mention of scoped, least-privilege, or agent-specific credential issuance mechanisms.
Agenticness — how well agents can access and operate the productSubscribe to events via webhooks
nonemoves agent-readyimpact 30
Missing: any documented webhook endpoint registration, event subscription API, or push-notification mechanism for external/AI consumers.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
The evidence pack lists many docs pages and API references but contains no mention of an interactive API reference with runnable/try-it-now examples (e.g., embedded Swagger/Postman consoles or live code sandboxes).
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
The evidence pack documents multiple mParticle APIs (HTTP events API, Warehouse Sync API, Platform Audiences API) but contains no mention of a downloadable OpenAPI/Swagger spec or any machine-readable API definition file.
Showing the top 8 of 42 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map6 surfaces · 31 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Guides docs22 stories
- Set up automations that run autonomously in the background
- An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the loop
- An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP server
- Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schema
- Audiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-time
- Build audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activating
- Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targeting
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Route events to a large catalog of documented destination integrations with per-destination mapping and filtering
- Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)
- Pull customer data in from third-party cloud apps and feeds — not just my own instrumented apps
- Query unified customer profiles — traits, identifiers, event history — through a documented profile API or store
- Anonymous and known activity stitches into one customer profile across devices, with documented and configurable identity-resolution rules
- Do everything through the API that I can do in the UI
- User consent is captured and enforced across destinations — opt-outs and consent categories are honored downstream automatically
- Process user deletion and suppression requests (GDPR/CCPA) and have them forwarded to connected destinations
- Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributes
- Control data retention and deletion
- Replay archived events into a new destination or backfill history when a tool is added or a pipeline breaks
- Run warehouse-native: define models and audiences on tables already in my warehouse and activate them without re-collecting the data (reverse ETL)
- Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I control
Developers docs19 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Set up automations that run autonomously in the background
- An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the loop
- An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP server
- Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schema
- Audiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-time
- Build audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activating
- Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targeting
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees
- Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)
- Pull customer data in from third-party cloud apps and feeds — not just my own instrumented apps
- Query unified customer profiles — traits, identifiers, event history — through a documented profile API or store
- Do everything through the API that I can do in the UI
- Replay archived events into a new destination or backfill history when a tool is added or a pipeline breaks
- Run warehouse-native: define models and audiences on tables already in my warehouse and activate them without re-collecting the data (reverse ETL)
docs.mparticle.com14 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Build audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activating
- Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees
- Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)
- Query unified customer profiles — traits, identifiers, event history — through a documented profile API or store
- Anonymous and known activity stitches into one customer profile across devices, with documented and configurable identity-resolution rules
- User consent is captured and enforced across destinations — opt-outs and consent categories are honored downstream automatically
- Process user deletion and suppression requests (GDPR/CCPA) and have them forwarded to connected destinations
- Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributes
- Control data retention and deletion
- A tracking plan or schema is enforced — violating events get flagged, blocked, or quarantined instead of silently corrupting downstream data
- Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinations
mparticle.com7 stories
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schema
- Audiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-time
- Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targeting
Integrations docs4 stories
- An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP server
- Route events to a large catalog of documented destination integrations with per-destination mapping and filtering
- Pull customer data in from third-party cloud apps and feeds — not just my own instrumented apps
- Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I control
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -si -X POST https://s2s.mparticle.com/v2/events -H 'Content-Type: application/json' -d '{}' # live events API answers 401 keylesslyreproduced$ curl -si -X POST https://s2s.mparticle.com/v2/events -H 'Content-Type: application/json' -d '{}' # live events API answers 401 [redacted]lessly
HTTP/2 401
date: Tue, 08 Sep 2026 22:00:13 GMT
content-length: 0
server: Kestrel
$mktemp -d && npm install @mparticle/web-sdk && node -e "console.log('PA_PROBE_OK mparticle init:', typeof require('@mparticle/web-sdk').init)"reproduced$ mktemp -d && npm install @mparticle/web-sdk && node -e "console.log('PA_PROBE_OK mparticle init:', typeof require('@mparticle/web-sdk').init)"
added 3 packages in 150ms
PA_PROBE_OK mparticle init: function
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
4 of 14 testable claims verified · 0 contradicted → integrity 29/100
19 distinct capability claims found in mParticle’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
4
Verified
10
Unverified
0
Contradicted
17
Undersold
Verified (4)
“Official client SDKs collect events from web, mobile, and server apps”
Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)partialproof ↗
“Events can be sent directly (server-to-server) to mParticle's ingestion API”
Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guaranteespartialproof ↗
“One-click connections to a large catalog of marketing, analytics, and data warehousing destinations”
Route events to a large catalog of documented destination integrations with per-destination mapping and filteringpartialproof ↗
“Warehouse Sync ingests data from your own warehouse (Snowflake, Redshift, BigQuery, Databricks) into mParticle”
Pull customer data in from third-party cloud apps and feeds — not just my own instrumented appspartialproof ↗
Unverified (12)
“Real-time profile API lets apps pull unified customer data to drive personalization”
Query unified customer profiles — traits, identifiers, event history — through a documented profile API or storepartialproof ↗
“IDSync identity resolution unifies known and anonymous user identities across apps/devices with configurable rules”
Anonymous and known activity stitches into one customer profile across devices, with documented and configurable identity-resolution rulesfullproof ↗
“Provides tools to view and enforce data quality, flagging violations against expected schema”
A tracking plan or schema is enforced — violating events get flagged, blocked, or quarantined instead of silently corrupting downstream datapartialproof ↗
“Lets you engage and activate customer cohorts across channels”
Audiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-timepartialproof ↗
“Data can be transformed, filtered, and enriched as it enters and leaves the pipeline”
Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinationspartialproof ↗
“Consent state (GDPR/CCPA) is captured and used to control whether events are forwarded to specific destinations”
User consent is captured and enforced across destinations — opt-outs and consent categories are honored downstream automaticallyfullproof ↗
“AI can grow undersized or saturated audiences by learning from strongest customer behaviors”
Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targetingpartialproof ↗
“Predictive scores for churn, conversion, and value growth can be computed and used to trigger audience activation”
Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targetingpartialproof ↗
“You can describe a desired audience or goal in natural language and the system suggests the logic/segment definition”
Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schemapartialproof ↗
“Visual interface for building customer audiences from traits and behaviors”
Build audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activatingpartialproof ↗
“Composable Audiences let you define audiences directly on warehouse-resident data without re-collecting it”
Run warehouse-native: define models and audiences on tables already in my warehouse and activate them without re-collecting the data (reverse ETL)partialproof ↗
“Audiences are connected to partner destinations via a directory of audience outputs for activation”
Audiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-timepartialproof ↗
Undersold (17)
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the looppartialproof ↗
An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP serverpartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Process user deletion and suppression requests (GDPR/CCPA) and have them forwarded to connected destinationspartialproof ↗
Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributespartialproof ↗
Replay archived events into a new destination or backfill history when a tool is added or a pipeline breakspartialproof ↗
Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I controlpartialproof ↗
Claims outside our story set (3)
Real capability claims found in mParticle’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Supports building custom integrations beyond the built-in connector catalog”
source ↗“Can lift identity match rates up to 2x with one click to improve audience reach”
source ↗“Can target or suppress at the household level using linked first-party identity signals”
source ↗
Business model
Sales-quoted only — the site offers 'Request pricing' and 'Contact sales' with no published tiers or unit rates; mParticle merged with Rokt in 2025 and targets enterprise contracts.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
