Reward mode: purchase conversion
How the bandit allocates traffic when Purchase conversion is selected.
TL;DR
Only one thing matters: what share of article visits ended in a purchase.
Visit with a purchase = success (1). Without = 0.
Order amount does not matter. Reaching checkout without paying does not matter.
Article effectiveness ≈ purchases / journeys. Higher → more traffic (via Thompson Sampling), but not 100% to one article: others keep being tested.
Details
Per-visit formula
Funnel stage and purchase_value are ignored.
Article score
Dashboard Effectiveness = (\text{mean_reward}) (conversion (0\ldots 1)).
How it differs
| Conversion | Depth | Revenue | |
|---|---|---|---|
| Checkout, no pay | 0 | high | weak depth |
| $10 vs $100 purchase | same (1) | same (1.0) | different |
| Goal | purchase event | funnel path | money |
Traffic
Same Thompson / selected algorithm. Below min_journeys — uniform.
A first purchase on one article does not lock 100% traffic forever: low-N competitors stay uncertain and keep getting explored.
Example
| Article | Visits | Purchases | CR | Expected share (approx.) |
|---|---|---|---|---|
| A | 385 | 10 | 2.6% | solid, not 100% |
| B | 84 | 2 | 2.4% | may beat A due to smaller N (explore) |
| C | 245 | 5 | 2.0% | mid share |
| D | 100 | 0 | 0% | little traffic |
Typical picture: leader 30–45%, other converters share the rest — not a single winner takes all.
When to use it
- Goal is purchase conversion, not revenue or “reached the store”
- Tracking reliably sends the purchase event (
purchased) - With very few purchases the metric is noisy — keep a sensible
min_journeys
Switch in bandit settings. Effectiveness recomputes immediately after save.