Skip to content

Customer Data Platforms Arena

Customer Data Platforms arenaBuyer checklist

Every requirement we judge customer data platforms products against, as a ready-to-send RFP checklist — with each item's priority, why it matters, and how the top-ranked products score on it today.

51 requirements · 14 themes · verdicts for 5 products · updated 2026-09-08 · priorities mirror the story weights our scoring uses (methodology)

Procurement report →
Show the markdown export
# Customer Data Platforms — buyer checklist (RFP)

Derived from ProductArena's evidence-graded user-story taxonomy for Customer Data Platforms: 51 judged requirements. Priorities mirror story weights (3 = must-have, 2 = should-have, 1 = nice-to-have).

## Agenticness

- [ ] **[must-have]** Plug MCP servers into this product so it can use their tools
- [ ] **[must-have]** Connect an agent via an official MCP server
- [ ] **[must-have]** Drive the product through a documented public API
- [ ] **[must-have]** Delegate tasks to a built-in AI assistant inside the product
- [ ] **[should-have]** Point an agent at llms.txt or agent-oriented docs
- [ ] **[should-have]** Run the product headlessly / in CI for automation
- [ ] **[should-have]** Use an official CLI
- [ ] **[should-have]** Issue scoped/least-privilege API credentials for an agent
- [ ] **[should-have]** Build against official SDKs
- [ ] **[should-have]** Subscribe to events via webhooks
- [ ] **[should-have]** Get AI-generated insights and suggestions from my data inside the product
- [ ] **[should-have]** Set up automations that run autonomously in the background
- [ ] **[should-have]** Operate the product with natural-language commands
- [ ] **[should-have]** Explore an interactive API reference with runnable examples
- [ ] **[should-have]** Download a machine-readable API spec (OpenAPI or equivalent)
- [ ] **[should-have]** Rely on versioned APIs with a documented deprecation policy
- [ ] **[nice-to-have]** Test against a sandbox environment without touching production data

## Ai cdp

- [ ] **[must-have]** An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the loop
- [ ] **[must-have]** An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP server
- [ ] **[should-have]** Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schema
- [ ] **[should-have]** AI decisioning agents pick messages, timing, and channels per customer autonomously within guardrails I set, with measurable lift

## Audiences activation

- [ ] **[must-have]** Build audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activating
- [ ] **[should-have]** Audiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-time
- [ ] **[should-have]** Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targeting

## Automation depth

- [ ] **[must-have]** Define rules that trigger actions automatically on events
- [ ] **[should-have]** Perform bulk operations across many items at once
- [ ] **[should-have]** Schedule recurring jobs or workflows
- [ ] **[nice-to-have]** Version, review, and roll back my automations

## Destinations integrations

- [ ] **[must-have]** Route events to a large catalog of documented destination integrations with per-destination mapping and filtering

## Event collection

- [ ] **[must-have]** Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)
- [ ] **[should-have]** Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees
- [ ] **[nice-to-have]** Pull customer data in from third-party cloud apps and feeds — not just my own instrumented apps

## Identity resolution

- [ ] **[must-have]** Anonymous and known activity stitches into one customer profile across devices, with documented and configurable identity-resolution rules
- [ ] **[should-have]** Query unified customer profiles — traits, identifiers, event history — through a documented profile API or store

## Openness

- [ ] **[must-have]** Export all of my data in open formats and leave
- [ ] **[must-have]** Self-host the core product
- [ ] **[should-have]** Do everything through the API that I can do in the UI
- [ ] **[should-have]** Read the product's source under an open license

## Pipeline observability

- [ ] **[should-have]** Watch events flow live and diagnose delivery failures per destination — debugger views, delivery metrics, and alerting

## Privacy consent

- [ ] **[must-have]** User consent is captured and enforced across destinations — opt-outs and consent categories are honored downstream automatically
- [ ] **[should-have]** Process user deletion and suppression requests (GDPR/CCPA) and have them forwarded to connected destinations
- [ ] **[should-have]** Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributes

## Privacy posture

- [ ] **[must-have]** Prevent my data from being used to train AI models
- [ ] **[should-have]** Choose where my data is stored (region/residency)
- [ ] **[should-have]** Control data retention and deletion
- [ ] **[should-have]** Opt out of telemetry and usage tracking

## Replay portability

- [ ] **[should-have]** Replay archived events into a new destination or backfill history when a tool is added or a pipeline breaks

## Transformations quality

- [ ] **[should-have]** A tracking plan or schema is enforced — violating events get flagged, blocked, or quarantined instead of silently corrupting downstream data
- [ ] **[should-have]** Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinations

## Warehouse native

- [ ] **[must-have]** Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I control
- [ ] **[should-have]** Run warehouse-native: define models and audiences on tables already in my warehouse and activate them without re-collecting the data (reverse ETL)

---

Source: https://ultrametric.ai/productarena/arena/customer-data-platforms (evidence-graded verdicts for 5 products) · methodology: https://ultrametric.ai/productarena/methodology

Chips show the top 5 ranked products' current verdict on each requirement — ✓ full · ~ partial · ! disputed · — none · n/a not applicable.

Agenticness — how well agents can access and operate the productAgenticness· 17 items

How well agents can access and operate the product

Ai cdp — stories about ai cdp in this arenaAi cdp· 4 items

Stories about ai cdp in this arena

  • ai-native userAn agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the loop

    Core requirement — weighs 3× in arena scoring · 1 of 5 products fully deliver this today

    must-have
  • ai-native userAn agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP server

    Core requirement — weighs 3× in arena scoring · 2 of 5 products fully deliver this today

    must-have
  • ai-native userDescribe an audience in natural language and AI builds the segment definition for review, grounded in my actual schema

    Important, not disqualifying — weighs 2× in arena scoring · 1 of 4 products fully deliver this today

    should-have
  • ai-native userAI decisioning agents pick messages, timing, and channels per customer autonomously within guardrails I set, with measurable lift

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Audiences activation — stories about audiences activation in this arenaAudiences activation· 3 items

Stories about audiences activation in this arena

  • marketerBuild audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activating

    Core requirement — weighs 3× in arena scoring · no product fully delivers this yet

    must-have
  • marketerAudiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-time

    Important, not disqualifying — weighs 2× in arena scoring · 1 of 5 products fully deliver this today

    should-have
  • marketerComputed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targeting

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Automation depth — how much of the product can run unattendedAutomation depth· 4 items

How much of the product can run unattended

Destinations integrations — stories about destinations integrations in this arenaDestinations integrations· 1 item

Stories about destinations integrations in this arena

Event collection — stories about event collection in this arenaEvent collection· 3 items

Stories about event collection in this arena

  • data engineerCollect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)

    Core requirement — weighs 3× in arena scoring · 3 of 5 products fully deliver this today

    must-have
  • data engineerSend events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees

    Important, not disqualifying — weighs 2× in arena scoring · 1 of 5 products fully deliver this today

    should-have
  • data engineerPull customer data in from third-party cloud apps and feeds — not just my own instrumented apps

    Differentiator, not a dealbreaker — weighs 1× in arena scoring · 1 of 5 products fully deliver this today

    nice-to-have

Identity resolution — stories about identity resolution in this arenaIdentity resolution· 2 items

Stories about identity resolution in this arena

  • data engineerAnonymous and known activity stitches into one customer profile across devices, with documented and configurable identity-resolution rules

    Core requirement — weighs 3× in arena scoring · 3 of 5 products fully deliver this today

    must-have
  • data engineerQuery unified customer profiles — traits, identifiers, event history — through a documented profile API or store

    Important, not disqualifying — weighs 2× in arena scoring · 1 of 5 products fully deliver this today

    should-have

Openness — open source, data portability, and self-hosting storiesOpenness· 4 items

Open source, data portability, and self-hosting stories

Pipeline observability — stories about pipeline observability in this arenaPipeline observability· 1 item

Stories about pipeline observability in this arena

  • data engineerWatch events flow live and diagnose delivery failures per destination — debugger views, delivery metrics, and alerting

    Important, not disqualifying — weighs 2× in arena scoring · 1 of 5 products fully deliver this today

    should-have

Privacy consent — stories about privacy consent in this arenaPrivacy consent· 3 items

Stories about privacy consent in this arena

  • privacy leadUser consent is captured and enforced across destinations — opt-outs and consent categories are honored downstream automatically

    Core requirement — weighs 3× in arena scoring · 1 of 5 products fully deliver this today

    must-have
  • privacy leadProcess user deletion and suppression requests (GDPR/CCPA) and have them forwarded to connected destinations

    Important, not disqualifying — weighs 2× in arena scoring · 1 of 5 products fully deliver this today

    should-have
  • privacy leadControl PII flow per destination — hashing, masking, and field-level filtering of sensitive attributes

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Privacy posture — data-handling and privacy storiesPrivacy posture· 4 items

Data-handling and privacy stories

Replay portability — stories about replay portability in this arenaReplay portability· 1 item

Stories about replay portability in this arena

  • data engineerReplay archived events into a new destination or backfill history when a tool is added or a pipeline breaks

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Transformations quality — stories about transformations quality in this arenaTransformations quality· 2 items

Stories about transformations quality in this arena

  • data engineerA tracking plan or schema is enforced — violating events get flagged, blocked, or quarantined instead of silently corrupting downstream data

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have
  • data engineerTransform, filter, and enrich events in-pipeline with custom code or functions before they reach destinations

    Important, not disqualifying — weighs 2× in arena scoring · 2 of 5 products fully deliver this today

    should-have

Warehouse native — stories about warehouse native in this arenaWarehouse native· 2 items

Stories about warehouse native in this arena

  • data engineerRaw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I control

    Core requirement — weighs 3× in arena scoring · 3 of 5 products fully deliver this today

    must-have
  • data engineerRun warehouse-native: define models and audiences on tables already in my warehouse and activate them without re-collecting the data (reverse ETL)

    Important, not disqualifying — weighs 2× in arena scoring · 2 of 5 products fully deliver this today

    should-have

Full evidence behind every verdict lives on the arena page and each product page — chips above deep-link straight to the judged story.