RFM Transaction Segmentation Workbench

How to use RFM Transaction Segmentation Workbench

One row represents one purchase. For each customer, the tool finds the most recent UTC civil date, counts transactions and sums amounts. Your four cutoffs per measure produce three scores from 1 to 5; their concatenation is a segment label, not a weighted prediction.

1. Enter transaction json (id, customer, date, amount), as-of utc civil date, cutoff json: [recency days, frequency, monetary].
2. Choose the stated convention and check the units and supported model.
3. Calculate, inspect the result, then copy or download it.

Good to know

• Exact-grid inputs are plain decimals with at most six places and magnitude≤1e9. Raw JSON number spelling is checked before conversion; decimal strings can preserve exact grid values. Exact rational intermediates are bounded to 8192 bits. Up to 500 unique transaction IDs and Gregorian dates 0001–9999 no later than the explicit as-of date. Positive amounts only, one currency, no refunds or period filtering. Recency equals a cutoff stays in the better bin; frequency/monetary equal a cutoff enter the higher bin. No upload, identity lookup, marketing action, response probability or automatic customer-worth judgment.
• Local calculation only; no input persistence or external lookup. Text/JSON is limited to 30000 characters and output to 1000000 characters. Numeric model inputs and precision/work limits are stated on this page. Approximate JSON numbers retain full stored values; exact arithmetic outputs retain decimal or fraction strings. Unsupported states fail explicitly.
• Educational user-assumption arithmetic only. No live prices, laws, tax rules, quotes or financial advice.