Report the customer base by RFM segment (segment client)

Computes an RFM (Recency / Frequency / Monetary) segmentation over the whole customer base and returns the per-bucket population plus ONE PAGE of the individual customer rows. Reach for this to answer ‘who should I target’ or ‘how healthy is the base’; use listCustomers when you just need the directory. Buckets: champions (recent, frequent, high value), loyal, at_risk (was good, has gone quiet), new (never purchased) and lost. The optional segment / tier / postalCodePrefix / optIn / min-maxMonetaryCents / min-maxFrequency / min-maxRecencyDays facets are the saved-segment predicate — the same criteria a campaign’s custom list is built from — combined as AND. They narrow the returned rows ONLY: baseTotal and counts always describe the whole base, so a bucket keeps its true size. Mind the two totals: total counts the rows the PREDICATE matched across all pages (pair it with page/pageSize, default 20, max 100, and stop at pageCount), while baseTotal is the size of the base itself. monetaryCents is integer cents; recencyDays is null for a customer who never bought, and the recency facets never match those customers (target them with segment=new). Feed the same facets to createCampaign to target this audience — but note the campaign re-evaluates them at send, so this response is the audience NOW, not the audience the send will resolve. To size a predicate WITHOUT pulling contact details, request pageSize=1 and read total (the match count) together with referenceDate (the instant it was computed). Each row carries the customer’s raw email/phone, so these are contact details: narrow with the facets rather than walking every page.