The Markin ROI Report for Enterprise Growth TeamsRead now
MARKIN
Field notes
Guides11 min read

Next best action model: propensity, uplift and ranking

How a next best action model is built: propensity, uplift meta-learners and a ranking function that scores expected incremental margin per action.

Romà Llambés
  • #Next Best Action
  • #Decisioning
  • #Guides
Next best action model: propensity, uplift and ranking

Frequently asked

Questions readers ask about this.

What is a next best action model?
A next best action model is the scoring stack that estimates, for one customer at one moment, the expected incremental value of every eligible action, including doing nothing, and ranks them. It combines a propensity layer, an uplift layer and a constrained ranking layer.
Which algorithms are used for next best action?
Gradient-boosted trees (XGBoost, LightGBM, CatBoost) for propensity on tabular data; uplift meta-learners such as the T-learner, X-learner and R-learner for causal effect; and a constrained argmax ranking layer for the final decision. Contextual bandits are useful for variant-level allocation inside an action.
What is the difference between a propensity model and an uplift model?
Propensity estimates how likely an outcome is for a customer. Uplift estimates how much a specific action changes that outcome. Ranking by propensity spends budget on customers who would have converted anyway; ranking by uplift spends it where the action makes a difference.
How do you validate a next best action model?
Offline, with Qini coefficients and uplift-at-k curves on a randomised held-out sample, with all features frozen at decision time. Online, with a preserved holdout of 5 to 15 percent of eligible customers, reading treated-minus-holdout incremental margin per decision.
How often should uplift models be retrained?
More often than propensity models. Treatment effects decay as the base adapts to the treatment, so keep a permanent randomised slice to re-estimate effects and retrain on a fixed cadence rather than only when accuracy drops.

See it in the product

This runs in Markin today.

The same loops this note describes run 24/7 against your customer base. Watch the workspace decide, experiment and execute 1:1.