Payments & products
Monetization, passes and catalog settings.
Quick start
- 1Open payment analytics for the game in My games.
- 2Choose a range and compare player spending and product data.
- 3In Price management, wait for a complete window, review both effects, and confirm the next price test.
- 4When editing, review the new name, price and sale status before confirming.
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 Robux received 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.
Product card
- Pass / developer product
- Different Roblox product types. Editing depends on permissions and API support; unavailable actions are disabled.
- Name / description / price
- After confirmation, changes update the live Roblox product, not just its display in MARPLA.
- Regional pricing / optimization
- The base price can differ from a particular player's price. Account for active Roblox settings.
Price management
MARPLA stores the base price of every pass and developer product each day and separately records detected changes. It compares consecutive stable price windows against two objectives: average daily gross Robux revenue and gross revenue divided by every active player that day. The first window is one complete UTC day. If the audience is below 500 players or the daily result is noisy, the minimum window expands to 3 days; below 100 players or with high volatility it expands to 7 days. This is supervised optimization: MARPLA suggests the next price, but a live Roblox product is updated only after review and confirmation by an owner or game admin. Roblox Price Optimization and immutable products are never edited.
Price-effect charts
The gross-revenue chart shows daily Item Monetization Revenue for an exact ProductKey. The per-player chart divides it by official Daily Active Users for the same complete day. Missing overall analytics is never turned into zero; a zero item row is allowed only when Roblox returned the day's overall item metric. Percentages compare the current stable price window with the immediately preceding one. Roblox Analytics does not provide per-row costs and fees, so this measures gross-revenue impact rather than accounting net profit.