mParticle
EcosystemEnterprise customer data platform for collecting and orchestrating customer data across devices and channels.
mParticle is an enterprise CDP used by large retail and commerce brands to collect, govern, and activate customer data. It operates at higher data volumes than many CDPs and has a strong focus on data quality and consent management, which makes it common in regulated industries and large enterprise accounts.
The platform collects events from mobile, web, server-side, and connected devices. It enforces data quality rules at ingest, filtering out malformed events before they reach downstream systems. The consent management layer tracks shopper opt-in status and can filter data routing based on consent state, which matters for GDPR and CCPA compliance.
mParticle's Profile API provides access to unified customer profiles built from cross-device event streams. Profiles include identity graph data (mapping email, phone, device IDs, and customer IDs to a single profile), computed attributes (traits calculated from event history), and audience membership (which segments the customer belongs to).
For AI agents, the identity graph is the most relevant feature. Agents operating with a shopper's email or phone number can query mParticle to resolve the full identity graph, surface loyalty tier and lifetime value from computed attributes, and check audience membership to determine promotional eligibility before initiating UCP checkout.
Why This Matters for UCP
mParticle supplies agents with identity graph resolution and computed attributes from enterprise retail data, enabling loyalty tier checks, LTV scoring, and audience membership lookups that personalize UCP checkout flows for large-scale commerce operators.
UCP Capabilities
UCP Endpoint
Ecosystem — Endpoint not yet publicly available
Integration Example
// mParticle Profile API: resolve identity and load computed attributes
// Agents use this to check loyalty status and audience membership before checkout.
const MP_API = 'https://api.mparticle.com/v1';
const creds = Buffer.from(
process.env.MP_API_KEY! + ':' + process.env.MP_API_SECRET!
).toString('base64');
// Resolve identity to get mpid
const identityResp = await fetch(`${MP_API}/identity/${encodeURIComponent('email:' + shopperEmail)}`, {
headers: { Authorization: `Basic ${creds}` },
}).then(r => r.json());
const mpid = identityResp.mpid;
console.log('Resolved mpid:', mpid);
// Fetch computed attributes for the profile
const attributes = await fetch(`${MP_API}/userprofiles/${mpid}/attributes`, {
headers: { Authorization: `Basic ${creds}` },
}).then(r => r.json());
console.log('Loyalty tier:', attributes.loyalty_tier);
console.log('Predicted LTV:', attributes.predicted_ltv);
console.log('Churn risk:', attributes.churn_risk_score);
// Check audience membership
const audiences = await fetch(`${MP_API}/userprofiles/${mpid}/audiences`, {
headers: { Authorization: `Basic ${creds}` },
}).then(r => r.json());
const isVipMember = audiences.some((a: any) => a.name === 'VIP Customers');
console.log('VIP eligible:', isVipMember);Category
Customer DataUCP Status
EcosystemTags
Pricing
enterprise
Is this your listing? Claim it to get analytics, a verified badge, and priority placement. Claim your listing →
Reviews
★★★★★4.7 (3 reviews)These are illustrative examples to show what reviews will look like. Submit your own experience below.
M. Lee
Backend Developer · Mar 3, 2026
Works well for our use case. The documentation is accurate and the implementation matches what the spec describes.
R. Kapoor
Platform Engineer · Jan 15, 2026
Integrated in an afternoon. Solid implementation with no unexpected edge cases in production.
J. Santos
Senior Engineer · Feb 28, 2026
Integration was straightforward. The UCP endpoint discovery works as documented and checkout completes in under 2 seconds.
9 other tools in Customer Data
Is this your tool? Claim this listing