---
title: "Propensity score vs intent bucket | Snowplow Signals"
description: "A propensity score is a continuous probability; an intent bucket is a named state from a finite set. The bucket is easier to read, act on and change."
source: https://signals.snowplow.io/learning/intent-and-propensity/propensity-score-vs-intent-bucket
---

[Learning](https://signals.snowplow.io/learning) / [Intent and propensity](https://signals.snowplow.io/learning/intent-and-propensity) 

# Propensity score vs intent bucket

A propensity score represents a customer as a continuous probability. An intent bucket represents them as one named state from a small, finite set, like browsing, comparing or ready. The two are different ways to carry the same decision, and they behave differently.

By [Alex Dean](https://signals.snowplow.io/blog/authors/alex-dean) Published Oct 26, 2026 

## A score versus a labeled state

A propensity score places a customer on a scale from zero to one. An intent bucket places them in one of a handful of named states: browsing, comparing, hesitating, ready, stuck. The score is continuous and the bucket is a label, so they carry the same decision in two different shapes.

## Why a bucket is easier to act on

A label is easier to read and agree on than a number. Product, marketing and support can look at “comparing” and settle on what to do; a value of around six in ten needs a threshold argument first. The named state also carries a reason the score leaves out, which makes a decision easier to explain and to debug when it looks wrong.

## What each costs to change

Changing a bucket is changing the plain-English definition of a state and shipping it. When a bucket turns out to cover two different things, you split it in a pull request. Changing what a propensity score means is a retrain and a revalidation of the model. The bucket trades the fine gradation of a score for speed to define and to iterate.

## Put it to work

* [Sort visitors by intent without a propensity model →](https://signals.snowplow.io/lp/intent-buckets)
* [Act on live behavior the moment it happens →](https://signals.snowplow.io/use-cases/act-in-the-moment)

## See it on your own traffic 

Add the SDK, define one attribute, and see an attribute updating against your own traffic in the first session. The free tier runs on the real engine: no card, no sales call.

[Start free](https://signals.snowplow.io/start) [Talk to an engineer](https://signals.snowplow.io/start?intent=engineer) 

More explainers in the [Learning Center →](https://signals.snowplow.io/learning)
