As a Roblox developer, it is currently too hard to determine how much USD a single transaction actually earned. Since the introduction of boosted Robux-to-USD conversion rates for earnings from 18+ users, the effective conversion rate varies depending on the age bracket of the purchaser — but sales data in developer analytics is still reported only in Robux, with no age-bracket split and no USD value attached at the transaction level.
Our use case
We license third-party IP for our experiences and are contractually required to report revenue to the rights holder every month for royalty calculations. Those calculations are done in USD, so we need to convert monthly transaction data into USD accurately.
Before the change, this was trivial: a single conversion rate applied to every sale, so Robux totals mapped cleanly to USD. Now the same Robux total can correspond to materially different USD amounts depending on the mix of 18+ and under-18 purchasers behind it — and we have no way to see that mix.
If this issue is addressed, it would improve my development experience because we would be able to continue reporting royalty-bearing revenue to our IP partner at the accuracy our agreement requires, without maintaining a manual estimation process or having to caveat the numbers we send. It would also let us evaluate the actual USD performance of individual products and experiences.
Minor note on possible solutions
Exposing the USD value of each transaction in analytics and the associated exports would solve this directly. Alternatively, surfacing the purchaser age bracket (18+ vs. under-18) per transaction, or the effective conversion rate applied, would let us compute it ourselves. We don’t have a preference between these — anything that makes per-transaction USD derivable would work.