Crafte Sessions analysis 2026 09 29 2026 10 29
sessions_analysis-2026-09-29-2026-10-29.csv · 2,246 rows · 15 columns · definition v3 saved 29 Oct 2026 14:08
Segments v6 built 29 Oct 2026 12:51 on feature set v3
What to do
From these segments' numbers. Setting buttons fill in the Build segments tab (then Build segments); merge buttons change the table below (then Save labels, no refit).- Worth doingaddedToCart: use S5, S3 as the targets on Outcomes
S5, S3 hold 35% of addedToCart in 14% of the snapshots (2.6× the overall rate).
- Worth doingreachedCheckout: use S5, S3 as the targets on Outcomes
S5, S3 hold 39% of reachedCheckout in 14% of the snapshots (2.9× the overall rate). Leaving out S2 (11% of snapshots) would also leave out 4% of reachedCheckout: that's the trade-off of the reduction.
- Fine as isUnknowns: 1.0% of snapshots
A small unknown share means nearly everyone fits a segment, while the odd ones aren't forced in.
- Fine as isordered: use S5, S3, S6 as the targets on Outcomes
S5, S3, S6 hold 51% of ordered in 15% of the snapshots (3.4× the overall rate). Leaving out S1, S2 (80% of snapshots) would also leave out 37% of ordered: that's the trade-off of the reduction.
Outcome concentration
Share of each segment's snapshots whose entity eventually had the outcome. Lift = rate ÷ overall rate.- S5 has the highest rate: 15% for ordered, 3.9× the overall 3.8%.
- Rate: share of a segment's snapshots whose entity eventually had the outcome. Everyone together: 3.8% for ordered.
- Lift = rate ÷ overall rate. S5 has 15% for ordered, so 3.9× the average; above 1 is better than average.
- Captured: the segment's share of all the outcomes (each Captured column adds to 100%). Compare it with Share: S1 is 69% of snapshots and holds 33% of ordered, so it dilutes it.
- Segments that capture much more than their share are the ones to take to Outcomes as targets.
| Segment | Snapshots | Share | addedToCart | reachedCheckout | ordered | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Rate | Lift | Captured | Rate | Lift | Captured | Rate | Lift | Captured | |||
| S1 | 1,558 | 69.4% | 9.2% | 0.7× | 47% | 6.2% | 0.6× | 44% | 1.8% | 0.5× | 33% |
| S2 | 241 | 10.7% | 9.5% | 0.7× | 8% | 3.3% | 0.3× | 4% | 1.7% | 0.4× | 5% |
| S3 | 216 | 9.6% | 31.0% | 2.3× | 22% | 23.6% | 2.4× | 23% | 13.4% | 3.5× | 34% |
| S4 | 88 | 3.9% | 8.0% | 0.6× | 2% | 6.8% | 0.7× | 3% | 3.4% | 0.9× | 3% |
| S5 (S5, S7 merged) | 88 | 3.9% | 43.2% | 3.2× | 13% | 39.8% | 4.1× | 16% | 14.8% | 3.9× | 15% |
| S6 | 32 | 1.4% | 9.4% | 0.7× | 1% | 9.4% | 1.0× | 1% | 6.2% | 1.6× | 2% |
| Unknown: fits no segment | 23 | 1.0% | 91.3% | 6.8× | 7% | 91.3% | 9.3× | 10% | 30.4% | 7.9× | 8% |
| Everyone | 2,246 | 100% | 13.4% | 9.8% | 3.8% | ||||||
How each segment differs
Average of each input, in standard deviations from everyone. Red higher, blue lower.landingPage=/product/474-port-and-prune-pudding-800g-log-in-cloth separates the segments most: from -0.1 sd in S5 to +8.3 sd in S6.- Each column is a segment and each row an input. A cell is how far the segment's average sits from everyone's, in standard deviations: +1 is clearly higher than typical (red), −1 clearly lower (blue), and near 0 is typical. Below, "slightly" means under 0.6 and "much" means over 1.5.
landingPage=/product/474-port-and-prune-pudding-800g-log-in-clothseparates the segments most: from -0.1 sd in S5 to +8.3 sd in S6.- S1 (1,558 snapshots): nothing stands out (every input within ±0.3), so it's the typical group.
- S2 (241 snapshots): much more often device is tablet (+2.6).
- S3 (216 snapshots): much longer-standing (returning) (+2.3); much more visits so far (+2.3); higher pages (+1.3).
- S4 (88 snapshots): much more often landingPage is /product/79-chocolate-fruit-cake-500g-boxed (+5.0).
- S5 (88 snapshots): much less often source is Facebook (-4.8); much lower newVisitor (-2.1); more often landingPage is other (+1.1).
- S6 (32 snapshots): much more often landingPage is /product/474-port-and-prune-pudding-800g-log-in-cloth (+8.3).
- Read a segment down its column to describe it; read across a row to see which segments differ on that input.
| S1 | S2 | S3 | S4 | S5 | S6 | Novel | |
|---|---|---|---|---|---|---|---|
landingPage=/product/474-port-and-prune-pudding-800g-log-in-cloth | -0.1 | -0.1 | -0.1 | -0.1 | -0.1 | +8.3 | -0.1 |
actions[add_recommended] | -0.1 | -0.1 | -0.1 | -0.1 | -0.1 | -0.1 | +5.8 |
landingPage=/product/79-chocolate-fruit-cake-500g-boxed | -0.2 | -0.2 | -0.2 | +5.0 | -0.2 | -0.2 | -0.2 |
source=Facebook | +0.2 | +0.2 | +0.2 | +0.2 | -4.8 | +0.2 | -1.1 |
source=Direct | -0.2 | -0.2 | -0.2 | -0.2 | +4.1 | -0.2 | +0.6 |
pages | -0.2 | -0.3 | +1.3 | +0.3 | +0.9 | -0.2 | +2.9 |
actions[add_checkout] | -0.0 | -0.0 | -0.0 | -0.0 | -0.0 | -0.0 | +2.9 |
device=tablet | -0.4 | +2.6 | -0.0 | +0.1 | -0.1 | -0.2 | +0.1 |
tenure_days | -0.3 | -0.3 | +2.3 | -0.0 | +0.1 | +0.3 | +1.0 |
rows | -0.3 | -0.3 | +2.3 | -0.0 | +0.3 | +0.2 | +1.1 |
landingPage=/ | +0.2 | +0.3 | -0.3 | -2.2 | -0.9 | -2.2 | -0.3 |
actions[co_cardpay] | -0.1 | -0.1 | +0.6 | +0.1 | -0.1 | +0.2 | +2.1 |
newVisitor | +0.1 | +0.1 | +0.1 | +0.1 | -2.1 | +0.1 | +0.1 |
actions[add_search] | -0.0 | -0.0 | -0.0 | -0.0 | -0.0 | -0.0 | +2.0 |
actions[co_fail] | -0.0 | -0.0 | -0.0 | -0.0 | -0.0 | -0.0 | +2.0 |
actions[sub_start] | -0.0 | -0.0 | -0.0 | -0.0 | -0.0 | -0.0 | +2.0 |
device=mobile | +0.3 | -1.7 | -0.0 | -0.0 | -0.3 | +0.1 | -0.1 |
minutes | -0.1 | -0.2 | +0.8 | -0.0 | +0.7 | -0.3 | +1.7 |
landingPage=other | -0.1 | -0.1 | +0.1 | -0.2 | +1.1 | -0.2 | +0.3 |
landingPage=/product/75-christmas-cake-boxed | -0.1 | +0.1 | +0.7 | -0.1 | -0.1 | -0.1 | +0.7 |
device=desktop | +0.0 | -0.4 | +0.1 | -0.1 | +0.6 | +0.0 | +0.0 |
Movement between segments
Where each entity's next snapshot lands, as a share of the row- Rows are where an entity's snapshot was; columns are where its next snapshot landed. Each row adds to 100%. The diagonal is staying put; anything else is a move.
- There are 232 steps from one snapshot to the next. 32% stayed in the same segment, so people often change segment between visits.
- Most common moves: S1 → S3 (111); S2 → S3 (20); S1 → S6 (6).
| From ↓ to → | S1 | S2 | S3 | S4 | S5 | S6 | Novel | moves |
|---|---|---|---|---|---|---|---|---|
| S1 | 91% | 3% | 5% | 1% | 122 | |||
| S2 | 91% | 9% | 22 | |||||
| S3 | 98% | 2% | 57 | |||||
| S4 | 56% | 44% | 9 | |||||
| S5 | 6% | 69% | 25% | 16 | ||||
| S6 | 33% | 33% | 33% | 3 | ||||
| Unknown: fits no segment | 100% | 3 |
Segments over time
How good are these segments?
Choosing the number of segments
- The number of segments was fixed at 7, so there's nothing to compare.
Fixed at 7 segments, so there was nothing to compare.
The unknowns
- 23 snapshots (1.0%) are unknown: 0 too little history, 0 between segments, 23 fit no segment.
- Too little history (0, 0.0%): fewer rows so far than the minimum you set.
- Between segments (0): no segment was a clear best fit; often someone changing pattern.
- Fits no segment (23): the oddest snapshots. Worth a look: new behaviour (or fraud) tends to show up here first.
- Nearest segment says which segment each would have joined if forced.
| Kind | Snapshots | Nearest segment |
|---|---|---|
| Unknown: fits no segment Doesn't resemble any segment. Worth a look: new patterns and fraud often start here. | 23 | S3 (16), S5 (3), S1 (2) |
Boundary rules
How to recognise each segment- Read each line as IF these conditions THEN this segment, using the inputs in their own units (minutes, page counts).
- Covers is the share of the segment the rule finds; correct is how many of the snapshots it finds really are in that segment.
- Together the rules agree with the model 97% of the time: good enough to use as a description.
S1 1 rule covering 91% of the segment
- device is not tablet and tenure_days ≤ 0.00638 and landingPage = / · covers 91% of the segment, 97% correct
S2 1 rule covering 100% of the segment
- device = tablet and rows ≤ 1.5 and landingPage is not /product/79-chocolate-fruit-cake-500g-boxed · covers 100% of the segment, 97% correct
S3 2 rules covering 95% of the segment
- rows > 1.5 and newVisitor > 0.5 and landingPage is not /product/79-chocolate-fruit-cake-500g-boxed · covers 89% of the segment, 96% correct
- rows ≤ 1.5 and landingPage = /product/75-christmas-cake-boxed and device is not tablet · covers 6% of the segment, 100% correct
S4 1 rule covering 100% of the segment
- landingPage = /product/79-chocolate-fruit-cake-500g-boxed · covers 100% of the segment, 100% correct
S5 1 rule covering 100% of the segment
- source is not Facebook and newVisitor > 0.5 · covers 100% of the segment, 100% correct
S6 1 rule covering 100% of the segment
- landingPage = /product/474-port-and-prune-pudding-800g-log-in-cloth · covers 100% of the segment, 100% correct
S7 1 rule covering 100% of the segment
- newVisitor ≤ 0.5 · covers 100% of the segment, 100% correct
Compare runs
Find the best segmentation- Each row is one segmentation run. Click the version to open it; the highlighted row is the one shown above.
- Separation and Stability describe the whole segmentation: are the segments distinct, and do they come back when refitted?
- The last four columns are about ordered: Targets are the segments at 1.5× the overall rate or more; Captured is the share of all ordered they hold (and the share of snapshots they are); Lift is how concentrated they are; Target stability is whether those particular segments come back when refitted.
- Read Captured and Lift together: a high lift on a sliver of the outcome is less useful than a slightly lower lift that holds most of it. pick marks the best mix: captured × lift, with full credit only when the targets' stability is 0.5 or more. ★ marks the best value in each column.
- Change one thing per run (the group handling, the number of segments, the shape or the feature set) so you can see what made the difference. Runs built before this table existed show '-'.
| Run | Features | Groups | Shape | Segments | Unknown | Separation | Stability | Targets | Captured | Lift | Target stability |
|---|---|---|---|---|---|---|---|---|---|---|---|
| v29 30 Oct 2026 12:50 |
v8 | device evened out | Full | 8 | 1.1% | 0.64 | 0.88 | S2, S5, S6 | 33% in 12% | 2.8× | 0.96 ★ |
| v28 30 Oct 2026 09:20 |
v7 | device evened out | Diagonal | 8 | 1.3% | 0.54 | 0.92 ★ | S2, S3, S5, S6 | 81% in 30% | 2.7× | 0.66 |
| v27 29 Oct 2026 17:17 |
v6 | device evened out | Diagonal | 8 | 1.3% | 0.54 | 0.92 ★ | S2, S3, S5, S6 | 81% in 30% | 2.7× | 0.66 |
| v26 29 Oct 2026 16:29 |
v6 | - | Diagonal | 5 | 1.0% | 0.45 | 0.59 | S3, S4 | 19% in 5% | 3.4× ★ | 0.21 |
| v25 29 Oct 2026 16:28 |
v6 | device evened out | Diagonal | 5 | 1.0% | 0.49 | 0.41 | S2, S3 | 83% in 31% ★ | 2.7× | 0.39 |
| v24 29 Oct 2026 16:27 |
v6 | device separately | Diagonal | 15 | 1.0% | 0.66 ★ | 0.54 | S5, S6, S7 | 31% in 10% | 3.1× | 0.62 |
| v23 29 Oct 2026 16:26 |
v6 | device ignored | Full | 5 | 0.7% ★ | 0.63 | 0.37 | S2, S3 | 41% in 18% | 2.2× | 0.42 |
| v22 29 Oct 2026 16:26 |
v6 | - | Full | 5 | 1.0% | 0.44 | 0.60 | S3, S4 | 19% in 6% | 3.4× | 0.21 |
| v21 29 Oct 2026 16:26 |
v6 | device separately | Full | 15 | 1.0% | 0.65 | 0.51 | S5, S6 | 27% in 9% | 3.0× | 0.57 |
| v20 pick 29 Oct 2026 16:24 |
v6 | device evened out | Full | 5 | 1.0% | 0.50 | 0.27 | S2, S4 | 83% in 25% ★ | 3.3× | 0.52 |
| v19 29 Oct 2026 16:22 |
v6 | - | Full | 5 | 1.0% | - | - | - | - | - | - |
| v18 29 Oct 2026 16:20 |
v6 | - | Full | 5 | 1.0% | - | - | - | - | - | - |
| v17 29 Oct 2026 16:20 |
v6 | - | Full | 5 | 1.0% | - | - | - | - | - | - |
| v16 29 Oct 2026 16:19 |
v6 | - | Full | 5 | 1.0% | - | - | - | - | - | - |
| v15 29 Oct 2026 14:10 |
v6 | - | Full | 5 | 1.0% | - | - | - | - | - | - |
| v14 29 Oct 2026 14:09 |
v6 | - | Diagonal | 4 | 1.0% | - | - | - | - | - | - |
| v13 29 Oct 2026 14:08 |
v6 | - | Diagonal | 9 | 1.1% | - | - | - | - | - | - |
| v12 29 Oct 2026 14:08 |
v6 | - | Diagonal | 7 | 1.0% | - | - | - | - | - | - |
| v11 29 Oct 2026 14:01 |
v5 | - | Diagonal | 7 | 1.0% | - | - | - | - | - | - |
| v10 29 Oct 2026 13:10 |
v4 | - | Diagonal | 7 | 1.0% | - | - | - | - | - | - |
| v9 29 Oct 2026 13:10 |
v4 | - | Diagonal | 7 | 89.8% | - | - | - | - | - | - |
| v8 29 Oct 2026 13:10 |
v4 | - | Diagonal | 10 | 1.0% | - | - | - | - | - | - |
| v7 29 Oct 2026 13:09 |
v4 | - | Diagonal | 7 | 1.0% | - | - | - | - | - | - |
| v6 29 Oct 2026 12:51 |
v3 | - | Diagonal | 7 | 1.0% | - | - | - | - | - | - |
| v5 29 Oct 2026 12:51 |
v3 | - | Diagonal | 10 | 1.0% | - | - | - | - | - | - |
Search results
49 setups · 30 Oct 2026 12:43 · judged on orderedBest: K-means · device evened out (8 segments). Its target segments (S2, S3, S4) hold 77% of ordered in 20% of the training snapshots, 3.8× the overall rate, and come back at 0.96 stability when refitted.
- Every setup was fitted on the same 1,828 training snapshots (1,611 people); the 20% of people held out for testing weren't used, so Outcomes can still test the winner honestly.
- Score = share of ordered captured × lift, with full credit only when the target segments' stability is 0.5 or more. Setups with over 25% unknown are halved.
- Stability is for the whole segmentation, Target stability just for the target segments. A setup with a slightly lower score but much higher stability can be the safer choice.
- Build on full data makes the real segmentation with that setup on everyone. It then appears below as a normal run: name the segments, compare, take it to Outcomes, and export it.
| # | Setup | Segments | Unknown | Separation | Stability | Captured | Lift | Target stability | Score | |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | K-means · device evened out | 8 | 1.3% | 0.64 | 0.96 | 77% in 20% | 3.8× | 0.96 | 2.93 | |
| 2 | Bayesian Gaussian mixture · Diagonal · device evened out | 8 | 1.0% | 0.54 | 0.63 | 84% in 31% | 2.7× | 0.75 | 2.25 | |
| 3 | Bayesian Gaussian mixture · Full · source ignored | 8 | 1.0% | 0.60 | 0.69 | 78% in 27% | 2.9× | 0.54 | 2.23 | |
| 4 | K-means · device separately | 18 | 1.3% | 0.73 | 0.90 | 57% in 14% | 3.9× | 0.94 | 2.23 | |
| 5 | K-means · source evened out | 8 | 1.1% | 0.63 | 0.76 | 59% in 16% | 3.7× | 0.72 | 2.19 | |
| 6 | Gaussian mixture · Diagonal · device evened out | 8 | 1.0% | 0.55 | 0.63 | 81% in 31% | 2.6× | 0.72 | 2.14 | |
| 7 | Gaussian mixture · Full · device evened out | 8 | 1.0% | 0.55 | 0.61 | 81% in 31% | 2.6× | 0.78 | 2.13 | |
| 8 | Bayesian Gaussian mixture · Diagonal · device ignored | 8 | 1.0% | 0.67 | 0.81 | 81% in 31% | 2.6× | 0.77 | 2.11 | |
| 9 | Gaussian mixture · Full · device ignored | 8 | 1.0% | 0.66 | 0.77 | 81% in 33% | 2.5× | 0.72 | 2.00 | |
| 10 | Bayesian Gaussian mixture · Full · device evened out | 8 | 1.0% | 0.55 | 0.59 | 78% in 31% | 2.5× | 0.74 | 2.00 | |
| 11 | Gaussian mixture · Diagonal · device ignored | 8 | 1.0% | 0.67 | 0.84 | 78% in 31% | 2.5× | 0.75 | 1.99 | |
| 12 | Gaussian mixture · Full · device separately | 19 | 1.1% | 0.67 | 0.82 | 62% in 20% | 3.1× | 0.56 | 1.96 |