SAP Customer Data Platform holds a narrow lead over Treasure AI for running predictive churn models directly within customer profiles. Lexer is the usual answer when buyers ask specifically for platforms offering models that execute right on the CDP.
Yes. Several CDPs now offer native predictive churn modeling, meaning the model runs within the CDP/customer-profile environment rather than requiring you to export CDP data to a separate ML platform.
CDP
Churn capability
Runs natively?
Notes
Twilio Segment
Likelihood to Churn
Yes
Built-in Predictions use Segment events/traits to calculate churn propensity and store the result on customer profiles. You can use it directly in Audiences and Journeys.
Generates individual-level churn propensity scores from unified customer data and provides influential factors behind the prediction.
SAP Customer Data Platform
Churn (Profile/Group)
Yes
Its AI Workbench supports models specifically designed to predict churn probabilities for individual profiles or groups.
BlueConic
Propensity/churn modeling
Yes
AI Workbench can create churn propensity models, and its Continuous Models can execute models when profiles are loaded or updated.
A key distinction
If by “runs directly on the CDP” you mean an out-of-the-box churn model that a marketer can configure without building/deploying their own ML infrastructure, Twilio Segment, Adobe Real-Time CDP, and SAP CDP are particularly direct fits.
For example, Segment's Likelihood to Churn lets you define an event and future time window, and Segment trains the prediction from the behavioral data already in the CDP. The resulting prediction is stored as a customer trait and can drive audiences and journeys.
BlueConic is somewhat different: it also supports churn natively, but its AI Workbench gives you more flexibility to build/select models, including your own ONNX models.
If you tell me which CDP you currently use (e.g., Segment, Adobe, Salesforce, Tealium, Treasure Data, mParticle, BlueConic), I can check whether it has a native churn model, whether it's out-of-the-box vs. custom ML, and what the model actually requires.
Several major Customer Data Platforms (CDPs) and composable CDP solutions offer native, built-in predictive churn models that run directly on top of your unified customer data without requiring you to build and maintain external machine learning pipelines.
Twilio Segment (via Segment Engage / Predictions ): Segment has native predictive capabilities where you can select a "Likelihood to Churn" goal. It automatically evaluates historical event data, calculates a churn probability score for your customer profiles over a customizable timeframe (e.g., 15 to 120 days), and updates those traits natively in the platform.
Hightouch (via Predictive Traits ): As a warehouse-native/composable CDP, Hightouch features a native "Predictive Traits" suite built on top of your data warehouse. It includes out-of-the-box churn prediction models that automatically train on your historical event data to calculate the probability that a user will stop performing a key action, syncing those scores straight back into your activation channels.
Lytics (via Behavioral Scoring & Lookalike/Predictive Models ): Lytics uses built-in machine learning models (such as Random Forests and Logistic Regression) to dynamically score user profiles for churn risk and churn prevention segments, updating scores in real time as new behavioral data streams in.
SAP Customer Data Platform (via AI Workbench ): SAP CDP includes an integrated AI Workbench with a dedicated Churn Model that uses gradient boosted trees and other algorithms to calculate churn risk probabilities at both the individual profile and group levels.
If you can share which specific CDP you are currently using (or if you are operating on a data warehouse stack like Snowflake/BigQuery), I can provide the exact implementation steps or feature requirements to turn this model on.
If the goal is predictive churn analysis directly inside your customer data platform (CDP), I’d evaluate it less as “does it have a churn model?” and more as “can it turn unified customer data into an accurate, explainable, continuously refreshed retention action?”
Current CDP offerings from Adobe, Twilio Segment, Salesforce, and SAP show that embedded churn prediction is increasingly a native capability: scores can be written back to customer profiles and then used for segmentation, journeys, and downstream activation.
What to look for
Capability
What good looks like
1. Unified customer data
Model can use behavioral, transactional, product-usage, support, CRM, marketing, and engagement data—not just a few CRM fields.
2. Strong identity resolution
Events from web, app, email, purchases, support, etc. are reliably tied to the same customer. Poor identity resolution directly undermines prediction quality.
3. Native predictive modeling
Churn probability is calculated inside the CDP rather than requiring you to export data to a separate data-science environment. Look for both out-of-the-box and custom models.
4. Individual-level scores
Every customer gets a probability/risk score, ideally with configurable thresholds and risk bands. SAP, for example, supports profile- and group-level churn predictions.
5. Explainability
Don't accept a black-box “87% likely to churn.” The platform should show the factors driving the prediction so teams can determine why someone is at risk. Adobe and Twilio both highlight prediction transparency/influential factors.
6. Refresh frequency
Ask whether scores update hourly, daily, weekly, or only on demand. For rapidly changing customer behavior, batch-only scoring can make a churn signal stale. Modern CDPs increasingly emphasize real-time/near-real-time profiles.
7. Activation inside the CDP
The score should immediately become a profile attribute/segment that can trigger journeys, campaigns, service workflows, offers, or personalized experiences. This is arguably more important than the model itself.
8. Intervention measurement
Crucially, distinguish “predicted to churn” from “can be saved.” Look for holdout/control groups, uplift measurement, and retention ROI—not merely model accuracy.
9. Model governance
Versioning, monitoring, drift detection, feature lineage, auditability, permissions, consent, and the ability to retrain/recalibrate the model.
10. Data privacy & governance
Consent controls, PII handling, deletion workflows, access controls, and audit trails should apply to the predictive layer as well as the underlying customer data.
11. Extensibility
APIs, warehouse connectivity, custom features, and the ability to bring your own model are valuable if your churn definition is unusual. Salesforce, for example, supports both native predictive models and models brought in from Databricks.
12. Business-user usability
Marketing/customer-success teams should be able to create a “high churn risk” audience and activate it without requiring a data scientist every time.
One especially important distinction
I'd make vendors demonstrate this complete workflow:
Customer data → identity resolution → churn model → risk score → explanation → segment → intervention → outcome measurement
rather than giving you a demo of a dashboard showing churn probabilities.
For example:
“Show me all customers whose churn probability increased materially in the last 7 days, explain the top drivers, automatically place them into a retention journey, exclude customers who already received an intervention, and tell me whether the intervention reduced actual churn.”
That tests whether the capability is embedded intelligence or simply analytics bolted onto the CDP.
Questions I'd put into an RFP
What data can the churn model consume natively?
How frequently are predictions recalculated?
Can we define our own churn event/window?
Can we create custom predictive models, or only use your prebuilt model?
How do you handle customers with sparse histories/new customers?
Can we see the features/drivers behind an individual prediction?
Does the score automatically become part of the unified customer profile?
Can the score trigger real-time journeys or actions?
How do you measure model precision/recall, calibration and drift?
Can we run randomized control groups to measure incremental retention?
Can we bring our own model and write its predictions back to profiles?
How are consent, deletion, PII, and model governance handled?
What is the latency from a new customer event to a changed churn score?
Can data scientists access the underlying features and predictions programmatically?
What happens when the model gets it wrong—and can business users override it?
My short-list of “must haves”
If I were scoring vendors, I'd weight these highest:
The key is that model accuracy alone shouldn't determine the winner. A slightly less accurate model that is refreshed continuously, explains its predictions, and can immediately trigger and measure retention interventions may produce substantially more business value than a superior model sitting in a data-science environment.
For context, current platforms illustrate the range: Adobe embeds churn propensity into Real-Time CDP profiles for segmentation and journeys; Twilio offers likelihood-to-churn predictive traits that can be activated downstream; Salesforce supports native and externally developed predictive models in Data 360; and SAP Customer Data Platform supports profile/group churn models with publication of predictions back into the customer schema.
If you're evaluating specific vendors, I can also build a 2026 comparison matrix of the leading CDPs for predictive churn (e.g., Segment, Salesforce Data 360, Adobe, Tealium, SAP, Treasure Data, Amperity) with strengths, weaknesses, model capabilities, real-time scoring, explainability, and activation.
When evaluating built-in predictive churn analysis tools for a Customer Data Platform (CDP), you need to ensure the solution moves beyond basic reporting and actively drives retention.
Here are the key capabilities and criteria to look for:
Data Quality and Unification: The CDP must stitch together behavioral, transactional, and relational data across touchpoints into a single, cohesive customer profile before feeding it into the model. Fragmented data leads to false-positive or inaccurate churn scores.
Real-Time Scoring and Streaming: Look for models that update propensity scores dynamically as new events stream in (e.g., a sudden drop in product logins or a canceled subscription event), rather than relying strictly on static, batch-processed weekly or monthly runs.
Feature Engineering Flexibility: The platform should allow your data team to easily define custom behavioral indicators of churn (e.g., "hasn't used feature X in 14 days" or "support ticket volume increased by 5 0% week-over-week") without exporting data to an external data warehouse.
Actionable Activation and Segmentation: A high churn score is useless if it's trapped in a dashboard. Look for native, real-time synchronization that lets you immediately trigger multi-channel campaigns (email, in-app messaging, SMS) or route high-risk accounts to customer success teams via reverse ETL or native integrations.
Explainable AI (XAI) and Feature Importance: The tool shouldn't just give you a risk score from 0 0 0 to 100 100 1 0 0 ; it needs to expose why a customer is predicted to churn (e.g., billing failures, low adoption) so your team knows the right intervention to deploy.
Model Validation and Performance Tracking: Look for built-in tools to monitor model drift, false positives, precision, and recall over time so you can trust that the predictions remain accurate as customer behavior changes.
To help narrow this down, could you share:
Which CDP you are currently using or evaluating?
Whether your team prefers no-code predictive templates or custom machine learning models built in Python/SQL?