MARPLA / Help center

User guide

Understand sales totals

Payment analytics helps compare revenue, products and income sources.

How to use it

  1. Open Payments for the game you need.
  2. Choose a range and income source.
  3. Compare sales totals in Robux with units sold in the product table.

Advice and practical context

A total describes flow, not balance

Robux sales belong to the selected report and range. They are not the withdrawable balance and do not by themselves account for every cost.

Breaking down a revenue change

Example: when sales rise, review units and product composition: the cause may be higher volume, a different price or one product.

Break a change in the total down by income source and product. Higher Robux with fewer purchases may reflect a more expensive mix; more purchases without similar revenue growth may indicate a different mix. Check the metric currency and selected range before calculating an average. For a financial decision, separately account for payouts, fees and costs that this sales total does not describe.

Compare matching periods

Do not compare a partial day with a complete one or combine different income sources without checking their definitions.

Technical detailsCalculations, permissions and behavior

Understanding totals

These are stored Roblox aggregates for completed UTC days, not an individual receipt ledger. The interface calls this Robux income, but technically the source reports gross player spending before Roblox fees—not a confirmed creator payout. An incomplete range shows the received subtotal and actual coverage instead of a misleading no-data state; gaps are not zero sales.

Product charts start with a separately toggleable All products total line and the ten largest products enabled; other products start disabled in an expandable group with bulk and individual controls. The point tooltip mirrors the selected lines: the total, selected top-10 products, and one combined Other products row for selected items from the expandable group. One full-width selected-day panel follows, with Robux, Units, and Table switches.

Rankings show the current base price first, then the scale and exact value. The table shows price, purchases, and Sales total together, while its growth index compares the selected day with the previous available day. Arrows and the calendar move through available days.

Products are matched by the official ProductKey. The Units purchased chart uses the official ItemMonetizationSales by ProductKey—the same Sales metric used by Creator Dashboard. Counts are never inferred from current prices.

Overall totals and product-level details may temporarily differ while data is arriving.