Vendor Briefing Decoder

What to ask after the demo. Sixteen claims every CEP and CDP pitch makes, decoded into architecture, with the questions that separate a real answer from a slide.

Every CEP and CDP demo repeats the same handful of claims: real-time, composable, agentic, zero-copy. None of them are false so much as compressed: a whole architecture decision folded into a word that sounds finished. This tool doesn't rank vendors or name names; that scoring is procurement's job, and it stays there. What follows unpacks sixteen of the most common claims into what they actually require underneath, where the ambiguity lives, and the three questions that get you past the slide. These are the same claims that show up, vendor by vendor, in Field Notes on CEP. Bring the questions to your next briefing.

Need the definition first? This tool assumes you already know what the acronym stands for. If you don't, start with the glossary. MarTech Acronym Decoder

16 / 16 claims

Last updated August 30, 2026 · 16 claims

Data & Identity Whether the platform actually knows who the customer is.
Data & Identity Best for: Technical workshop
#

Identity graph

The pitch “Our identity graph gives you a single view of every customer.”

Force specificity

  1. Match rate isn't a fixed number, it depends on the identifiers and population behind it. How would you actually validate match rate and false-positive rate against a sample of my own data before I commit?
  2. How do you handle identity merges and splits when a match turns out to be wrong after messages have already gone out?
  3. Can I see the actual matching logic, deterministic keys versus probabilistic scoring, or is that entirely proprietary?
Data & Identity Best for: Briefing
#

Unified customer profile

The pitch “One unified profile for every customer, across every channel.”

Force specificity

  1. How do you handle a customer who exists in three source systems with three different IDs and no shared key?
  2. When two source systems disagree about the same field, a phone number or an opt-in status, whose data wins, is that precedence rule based on source of truth or event time, and can I reconfigure it myself as ownership changes?
  3. What is the profile refresh latency when a source system updates? How stale can the unified view get, and by how much?
Data & Identity Best for: Security & legal review
#

Data enrichment

The pitch “We enrich every profile with hundreds of data points, automatically.”

Force specificity

  1. Which of these attributes are directly observed, and which are modelled or inferred? What is the typical accuracy for the modelled ones?
  2. What is the data provenance and legal basis for using each third-party attribute in the markets where I operate?
  3. What happens to a campaign already using one of these attributes when the underlying third-party source changes or goes stale?
Decisioning & Delivery Who decides what happens next, and on what evidence.
Decisioning & Delivery Best for: Technical workshop
#

Real-time

The pitch “Real-time personalization, out of the box.”

Force specificity

  1. From the moment an event fires, how many milliseconds until a decision is made, and how many more until the message reaches the channel?
  2. Does that number hold for every channel you're selling me, or only for push and in-app, with email and paid still running on a batch sync?
  3. What happens to that latency under peak load, during a flash sale or a seasonal traffic spike?
Decisioning & Delivery Best for: Technical workshop
#

AI-driven decisioning

The pitch “AI decides the next best action for every customer, automatically.”

Force specificity

  1. What is the actual fallback logic when the model has no data for a customer, such as a new lead with zero history?
  2. For a specific customer, can I see which inputs, constraints and ranking factors actually drove the decision, and where the suppression logic sits relative to the model's ranking?
  3. Who owns the objective function? When two teams' journeys compete for the same send, whose goal wins, and where is that configured?
Decisioning & Delivery Best for: Briefing
#

Agentic AI

The pitch “Agentic AI that plans and executes campaigns on its own.”

Force specificity

  1. Walk me through an actual multi-step sequence the agent completed with zero human approval, from goal to executed action.
  2. Where are the guardrails? What can the agent never do without sign-off, and who configures that boundary?
  3. When the agent gets it wrong, how do I find out, and how far downstream does the damage travel before anyone notices?
Decisioning & Delivery Best for: Briefing
#

Omnichannel

The pitch “True omnichannel orchestration: every channel working together in real time.”

Force specificity

  1. If a customer converts through email, does an in-flight SMS or push step in the same journey know within seconds, or does it send anyway?
  2. Is frequency capping and channel priority computed once across all channels, or configured separately per channel with no shared view?
  3. Can you show one customer's full cross-channel touch history on a single timeline, not per-channel logs stitched together afterward?
Decisioning & Delivery Best for: Technical workshop
#

Predictive AI

The pitch “Our AI predicts churn and propensity before it happens.”

Force specificity

  1. What exact outcome was the model trained to predict, and how was that label defined?
  2. Can I see accuracy or lift measured on a cohort from my own business, not your reference dataset?
  3. How often does the model retrain, and what happens to live scores while a retrain is running?
Architecture Where the data really lives, and what it costs to move it.
Architecture Best for: Procurement
#

Composable / MACH

The pitch “Composable architecture: no vendor lock-in.”

Force specificity

  1. If I stop paying you tomorrow, where does my customer profile data live, and can I export it in a format another tool can read without a migration project?
  2. Which parts of your platform can I actually replace with a competitor's component, and which are load-bearing and non-negotiable?
  3. Do you charge separately for the components I don't use, or is 'composable' a suite priced under a new label?
Architecture Best for: Technical workshop
#

Zero-copy

The pitch “Zero-copy integration: activate straight from your warehouse, nothing duplicated.”

Force specificity

  1. At the moment a message sends, are you querying my warehouse live, or activating against a copy you synced earlier? How stale can that copy get?
  2. What is the query latency and cost impact on my warehouse when your platform activates at my actual send volume?
  3. If I revoke your warehouse access right now, does personalization stop immediately, or keep running off a cached copy?
Architecture Best for: Procurement
#

Native integrations

The pitch “Native integrations with every platform you already use.”

Force specificity

  1. Who built and maintains this specific integration, your team or the other vendor's, and when was it last updated?
  2. Does this integration expose the other platform's full object model with real-time, two-way webhooks, or does it poll a limited subset of fields on a schedule?
  3. Can I see this integration running in a live customer environment at roughly my scale, not just in a sandbox?
Governance & Privacy What the platform will let anyone see, and prove.
Governance & Privacy Best for: Security & legal review
#

Clean room

The pitch “Collaborate with partners in a privacy-safe clean room, no raw data ever leaves your walls.”

Force specificity

  1. What is the smallest aggregate size, the k-anonymity threshold, you allow a query to return, and who enforces it?
  2. Can either party ever export row-level matched data out of the clean room, under any workflow?
  3. Who has audited this, and can I see the audit, or is 'privacy-safe' a description you apply to yourselves?
Governance & Privacy Best for: Security & legal review
#

Data residency

The pitch “Full data residency: your data never leaves the region, sovereign cloud guaranteed.”

Force specificity

  1. Which specific data flows, storage, processing, backups, support access, are actually confined to the promised region, and which aren't?
  2. Do you use subprocessors or global support teams who can access this data, and where are they located?
  3. What does the residency guarantee say in the contract, versus what's said in this conversation?
Operating Model Who can run this day to day, and what happens when it breaks.
Operating Model Best for: Pilot readiness
#

No-code

The pitch “No-code journey builder: marketers build campaigns without IT.”

Force specificity

  1. What is the most complex journey a marketer, with no engineering support, has actually built and shipped on this platform?
  2. When something breaks, an empty segment, an event that never fires, who debugs it, do they need engineering to do it, and can a marketer version, roll back or safely promote a change without breaking a live journey?
  3. How do you prevent a marketer from building a suppression rule that accidentally contradicts a consent requirement?
Operating Model Best for: Technical workshop
#

Observability / debuggability

The pitch “Full observability into every journey, you'll always know exactly what happened and why.”

Force specificity

  1. For one specific customer, can you show the full decision trail, which journey, which branch, which data value tipped it, at the exact moment a message sent?
  2. How far back does that trace history go, and does it survive a schema change or a journey edit made after the fact?
  3. When a customer gets the wrong message, how long does it typically take your own team to reconstruct what actually happened?