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

A newer feature set (v8) exists. These segments were built on v3.
Segments found
7
fixed
In a segment
99%
2,223 of 2,246 snapshots
Unknown
1.0%
0 history · 0 between · 23 novel
Rules match the model
97%
for named segments

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.

Segments

Name them, merge near-duplicates, or send one to unknown. Nothing is refitted.
SegmentLabelSnapshotsShare What sets it apartMerge intoUnknown
S1 1,55869.4% Typical: nothing stands out
S2 24110.7% Much more often device is tablet
S3 2169.6% Much longer-standing (returning); much more visits so far; higher pages
S4 883.9% Much more often landingPage is /product/79-chocolate-fruit-cake-500g-boxed
S5 723.2% Much more often source is Direct; more often landingPage is other; more often device is desktop
S6 321.4% Much more often landingPage is /product/474-port-and-prune-pudding-800g-log-in-cloth
S7 → S5 160.7% Much lower newVisitor; much less often source is Facebook; much higher pages
? Unknown: fits no segment 231.0% high actions[add_recommended] (+5.8 sd), high pages (+2.9 sd), high actions[add_checkout] (+2.9 sd)

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%.
SegmentSnapshots ShareaddedToCartreachedCheckoutordered
RateLiftCapturedRateLiftCapturedRateLiftCaptured
S11,55869.4%9.2%0.7×47%6.2%0.6×44%1.8%0.5×33%
S224110.7%9.5%0.7×8%3.3%0.3×4%1.7%0.4×5%
S32169.6%31.0%2.3×22%23.6%2.4×23%13.4%3.5×34%
S4883.9%8.0%0.6×2%6.8%0.7×3%3.4%0.9×3%
S5 (S5, S7 merged)883.9%43.2%3.2×13%39.8%4.1×16%14.8%3.9×15%
S6321.4%9.4%0.7×1%9.4%1.0×1%6.2%1.6×2%
Unknown: fits no segment231.0%91.3%6.8×7%91.3%9.3×10%30.4%7.9×8%
Everyone2,246100%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.
S1S2S3S4S5S6Novel
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
There are 232 steps from one snapshot to the next. 32% stayed in the same segment, so people often change segment between visits.
From ↓   to →S1S2S3S4S5S6Novelmoves
S191%3%5%1%122
S291%9%22
S398%2%57
S456%44%9
S56%69%25%16
S633%33%33%3
Unknown: fits no segment100%3

Segments over time

Rebuild to see how the segments change over time.

How good are these segments?

Rebuild to measure separation and stability.

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.
KindSnapshotsNearest segment
Unknown: fits no segment
Doesn't resemble any segment. Worth a look: new patterns and fraud often start here.
23S3 (16), S5 (3), S1 (2)

Boundary rules

How to recognise each segment
Together the rules agree with the model 97% of the time: good enough to use as a description.
Each segment gets its own short rules for picking it out from everyone else, in each feature's own units. Taken together, simple rules reproduce 97% of the assignments. Rules show where the lines fall, not why: use the profile above for what defines a segment. Unknowns have no rules; they come from how well a snapshot fits, not from where it sits.
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
The pick is v20: its targets hold 83% of ordered in 25% of snapshots (3.3× the rate), with target stability 0.52.
RunFeaturesGroupsShapeSegmentsUnknownSeparationStabilityTargetsCapturedLiftTarget stability
v29
30 Oct 2026 12:50
v8device evened outFull81.1% 0.640.88 S2, S5, S633% in 12%2.8× 0.96 ★
v28
30 Oct 2026 09:20
v7device evened outDiagonal81.3% 0.540.92 ★ S2, S3, S5, S681% in 30%2.7× 0.66
v27
29 Oct 2026 17:17
v6device evened outDiagonal81.3% 0.540.92 ★ S2, S3, S5, S681% in 30%2.7× 0.66
v26
29 Oct 2026 16:29
v6-Diagonal51.0% 0.450.59 S3, S419% in 5%3.4× ★ 0.21
v25
29 Oct 2026 16:28
v6device evened outDiagonal51.0% 0.490.41 S2, S383% in 31% ★2.7× 0.39
v24
29 Oct 2026 16:27
v6device separatelyDiagonal151.0% 0.66 ★0.54 S5, S6, S731% in 10%3.1× 0.62
v23
29 Oct 2026 16:26
v6device ignoredFull50.7% ★ 0.630.37 S2, S341% in 18%2.2× 0.42
v22
29 Oct 2026 16:26
v6-Full51.0% 0.440.60 S3, S419% in 6%3.4× 0.21
v21
29 Oct 2026 16:26
v6device separatelyFull151.0% 0.650.51 S5, S627% in 9%3.0× 0.57
v20 pick
29 Oct 2026 16:24
v6device evened outFull51.0% 0.500.27 S2, S483% in 25% ★3.3× 0.52
v19
29 Oct 2026 16:22
v6-Full51.0% -- --- -
v18
29 Oct 2026 16:20
v6-Full51.0% -- --- -
v17
29 Oct 2026 16:20
v6-Full51.0% -- --- -
v16
29 Oct 2026 16:19
v6-Full51.0% -- --- -
v15
29 Oct 2026 14:10
v6-Full51.0% -- --- -
v14
29 Oct 2026 14:09
v6-Diagonal41.0% -- --- -
v13
29 Oct 2026 14:08
v6-Diagonal91.1% -- --- -
v12
29 Oct 2026 14:08
v6-Diagonal71.0% -- --- -
v11
29 Oct 2026 14:01
v5-Diagonal71.0% -- --- -
v10
29 Oct 2026 13:10
v4-Diagonal71.0% -- --- -
v9
29 Oct 2026 13:10
v4-Diagonal789.8% -- --- -
v8
29 Oct 2026 13:10
v4-Diagonal101.0% -- --- -
v7
29 Oct 2026 13:09
v4-Diagonal71.0% -- --- -
v6
29 Oct 2026 12:51
v3-Diagonal71.0% -- --- -
v5
29 Oct 2026 12:51
v3-Diagonal101.0% -- --- -

Search results

49 setups · 30 Oct 2026 12:43 · judged on ordered

Best: 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.
#SetupSegments UnknownSeparationStabilityCaptured LiftTarget stabilityScore
1K-means · device evened out81.3% 0.640.9677% in 20%3.8× 0.962.93
2Bayesian Gaussian mixture · Diagonal · device evened out81.0% 0.540.6384% in 31%2.7× 0.752.25
3Bayesian Gaussian mixture · Full · source ignored81.0% 0.600.6978% in 27%2.9× 0.542.23
4K-means · device separately181.3% 0.730.9057% in 14%3.9× 0.942.23
5K-means · source evened out81.1% 0.630.7659% in 16%3.7× 0.722.19
6Gaussian mixture · Diagonal · device evened out81.0% 0.550.6381% in 31%2.6× 0.722.14
7Gaussian mixture · Full · device evened out81.0% 0.550.6181% in 31%2.6× 0.782.13
8Bayesian Gaussian mixture · Diagonal · device ignored81.0% 0.670.8181% in 31%2.6× 0.772.11
9Gaussian mixture · Full · device ignored81.0% 0.660.7781% in 33%2.5× 0.722.00
10Bayesian Gaussian mixture · Full · device evened out81.0% 0.550.5978% in 31%2.5× 0.742.00
11Gaussian mixture · Diagonal · device ignored81.0% 0.670.8478% in 31%2.5× 0.751.99
12Gaussian mixture · Full · device separately191.1% 0.670.8262% in 20%3.1× 0.561.96

Settings

One segmentation with exactly these settings. To try many automatically, use Find the best.
Feature set

The inputs to segment on.

Number of segments

Search a range and let the fit decide, or fix it.

When to say "unknown"

Rather than forcing everyone into a segment.

Groups

A column such as device or caseworker that should be treated differently in this run.

Each segment count is fitted 2 times on up to 60,000 snapshots. A range of 8 counts on 20,000 snapshots takes about half a minute; "Diagonal" is several times faster.