PushizoDocs
Analytics & data

RFM segmentation

RFM groups users by three measures: how recently they last transacted (recency), how often they transact (frequency) and how much they spend (monetary). Pushizo gives each user a 1–5 score on these measures, derives a ready-made segment from the scores…

RFM groups users by three measures: how recently they last transacted (recency), how often they transact (frequency) and how much they spend (monetary). Pushizo gives each user a 1–5 score on these measures, derives a ready-made segment from the scores and shows how users move between segments. Decision record: docs/adr/0062-rfm-segmentasyonu.md.

Setup

Open the RFM Analysis page in the dashboard and enter the following with Configure model:

FieldDescriptionDefault
EventsEvents that count as purchases, up to 10Required
WindowNumber of recent days to count, 30–730180
Use monetary valueWhen off, the segment is derived from recency and frequency onlyOn
Value propertyEvent property the value is read fromThe event's value field

The first calculation starts when you save. After that, scores are refreshed every day at 04:30 UTC.

Keep in mind:

  • Only events from identified users are counted.
  • Currencies are not converted; events should be sent in a single currency.
  • If your event retention period is shorter than the window, only the retained events are used.
  • Scores come from how users rank relative to each other. With fewer than 100 users the results may be misleading; the dashboard points this out.

Segments

R \ FM12345
5New customersPotential loyalistsPotential loyalistsChampionsChampions
4PromisingPotential loyalistsPotential loyalistsChampionsChampions
3About to sleepAbout to sleepNeed attentionLoyal customersLoyal customers
2HibernatingHibernatingAt riskAt riskAt risk
1LostLostAt riskCan't lose themCan't lose them

FM is the average of the frequency and monetary scores, rounded up. If monetary value is off, or everyone has the same value, FM equals the frequency score.

Names in the API: champions, loyal, potential, new, promising, need_attention, about_to_sleep, at_risk, cant_lose, hibernating, lost.

Using it in audiences

You can create an audience segment with one click from a segment row on the page, or pick the RFM fields in the segment builder:

{ "all": [{ "field": "rfm.segment", "op": "in", "value": ["at_risk", "cant_lose"] }] }
FieldOperatorsValue
rfm.segmenteq, neq, in, not_inSegment name
rfm.recency, rfm.frequency, rfm.monetaryeq, gt, gte, lt, lte, between1–5

A user without a score only matches neq and not_in conditions.

Transitions

The transition table compares each user's segment at the start and at the end of the selected period. Out of scope means the user had no score on that date: they had no events within the window, or the first calculation had not run yet. History is kept for 400 days.

API

curl -X PUT "https://api.pushizo.com/v1/apps/$APP_ID/rfm/config" \
  -H "Authorization: Bearer $PUSHIZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"enabled":true,"event_names":["purchase"],"window_days":180}'
EndpointScopeDescription
GET /v1/apps/{appId}/rfm/configanalytics:readModel and calculation status
PUT /v1/apps/{appId}/rfm/configadminConfigures the model; starts a calculation if enabled
POST /v1/apps/{appId}/rfm/computeadminQueues a calculation (202)
GET /v1/apps/{appId}/rfm/overviewanalytics:readSegment distribution
GET /v1/apps/{appId}/rfm/transitionsanalytics:readTransitions between the from and to dates
GET /v1/apps/{appId}/rfm/usersusers:readUsers, with segment, limit, cursor

Privacy

When a user is deleted, their score and history are deleted too. When app data is purged, both tables are emptied; the model settings remain.

On this page