price-optimization.md

title	description
Price optimization	Price optimization finds the best price points for your passes and developer products, helping you earn more money over time.

<iframe width="800" height="450" src="https://www.youtube-nocookie.com/embed/ULr3CZ8egP8" title="YouTube video player" frameborder="0" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
To run a successful price optimization test, your experience has to have enough transactions to produce significant data. In most cases, this means your experience should have had at least 60,000 transactions over the previous 30 days.

To find how many transactions your experience has had, add the total number of product sales over a 30-day period. For more information, see Pass analytics and Developer Product analytics.

Price optimization lets you find the best price points for your passes and developer products, which can help you earn more money over time while keeping your prices competitive. When you run a price test, subsets of your users see different prices for the same product. At the end of the test, you receive recommendations for the prices that performed best with your audience.

Before using price optimization, you should use the dynamic price check tool to make sure product prices are dynamically scripted inside your experience. After using price optimization, you can run a price review period to track the long-term revenue impact of your price changes.

You can combine price optimization with Regional Pricing for your passes to reach a wider audience and build a more accessible and inclusive global economy. For more information about setting region-specific prices, see Regional Pricing.

Check for dynamic pricing

Price optimization can't collect data from and make changes to prices you have hard-coded into your experience. To run a price optimization test on products with hard-coded prices, you must first update them to be dynamically scripted.

Dynamically scripted prices update through Class.MarketplaceService|MarketplaceService and use functions like Class.MarketplaceService:GetProductInfo()|GetProductInfo() and Class.MarketplaceService:GetDeveloperProductsAsync()|GetDeveloperProductsAsync() to retrieve and display product prices you have set through the Creator Hub. For information on how to dynamically script product prices, see Sell a pass and Sell a developer product.

The dynamic price check tool updates all products for sale with a fake Robux price or a fake economic location to identify which of your product prices are hard-coded and which are scripted with Class.MarketplaceService|MarketplaceService inside your experience. If a product price updates to new price, the price is scripted. If it remains the same, the price is hard-coded.

The `InfoType` parameter in `GetProductInfo()` fetches an asset by default. To fetch a developer product, use `Enum.InfoType.Product`. To fetch a pass, use `Enum.InfoType.GamePasses`.

local productInfo = MarketplaceService:GetProductInfo(PRODUCT_ID, Enum.InfoType.Product)
local price = productInfo.PriceInRobux

local priceInRobux = 500

To use the dynamic price check tool:

1. Go to Creations and select an experience.
2. Go to Monetization > Price Optimization.
3. Click Dynamic Price Check.
4. Under Add test accounts, enter up to five Roblox users to check for hard-coded prices.
5. Select a testing type.
   • Price pinned updates all dynamically-scripted prices with a set fake Robux amount.
   • Location pinned updates all dynamically-scripted prices with a region-specific price for a fake economic location.
6. Click Enable. After a few minutes, you can enter your experience to identify the hard-coded prices.

To disable the dynamic price check tool, go to the Dynamic Price Check page and click Disable.

Use price optimization

To use price optimization:

1. Go to Creations and select an experience.
2. Go to Monetization > Price Optimization.
3. Select the developer products and passes you want to include in the price test. For best results, include all products.
4. Click Start Test. After approximately two weeks, you receive an e-mail notification that the test is complete. The Price Optimization page updates with the optimized product prices, the recommended price percentage change, and the approximate long-term revenue impact of applying the new product prices.
5. Click Review & Apply prices to apply the results of the price optimization test.
6. (Optional) Click Start price review to run a price review period.

You can stop the price optimization test any time by clicking Stop test in the Price Optimization page. If you stop the test, your product prices revert to their original prices.

To make sure your product prices stay optimal, run a price optimization test every three months. You should also consider running a new price test whenever you create new products that account for a significant part of your revenue, or when you make substantial changes to your experience mechanics.

Run a price review period

After you receive the results from a price test, you can start an optional price review period to track the long-term revenue impact of the price recommendations.

The price review period is approximately four weeks long and includes all products that were part of the price optimization test. If you choose to participate in the review period, 98% of your users see the suggested optimized prices while 2% continue to see the original product prices. This makes sure that the optimized prices are performing as expected with your audience.

If the price review period results are favorable, the optimized prices are applied to 100% of your users. If the results aren't favorable, Roblox stops the review process and restores all products back to their original prices. You can also manually stop the review process any time, and either apply the optimized prices to all of your users or revert all products back to their original prices.

To run a price review period:

1. After running a price optimization test, click Start price review in the Price Optimization page. After four weeks, you receive an e-mail notification that the review is complete. The Price Optimization page updates with the reviewed prices, the overall revenue increase, and the approximate long-term revenue impact of applying the new product prices.
2. Click Finish to complete the review.

Limitations

• You can only optimize the prices of developer products and passes. Price optimization isn't available for subscriptions.
• If you start a price optimization test while the dynamic price check tool is running, the dynamic price check tool is automatically disabled.
• You can't make changes to the prices of products involved in price tests while the tests are in progress.
• After running a price test, the price optimization tool lets you apply the optimized prices to either all of the involved products or to none of them. To apply the optimized prices to just a selection of the products, take the price test recommendations and manually update the products in the Creator Hub.
  • The projected revenue impact is based on applying the optimized prices to all of the involved products, so manually updating some product prices means the projected revenue impact is no longer accurate. You're also not able to run a price review period on just a selection of the products.

Glossary

**Term**	**Definition**
**Test period**	The price optimization test period or the price review period.
**Price groups**	The test groups involved in the price optimization tests.
**Paying users**	The number of users who purchased at least one tested product during the test period.
**Sales**	The number of products sold during the test period.
**Total playtime**	The total time users spent inside the experience during the test period.
**Daily active users**	The number of active users during the test period.
**Short-term revenue**	The amount of Robux spent on tested products during the two-week price optimization test period.
**Long-term revenue**	The amount of Robux spent on tested products during the four-week price review period.
**Approximate long-term revenue impact**	The projected long-term revenue increase if the optimized prices are applied to the tested products.
**Tested products revenue increase**	The revenue of the tested products shown to 98% of users during the price review period.
**Overall revenue increase**	The combined revenue of the tested products during the price review period, including the 2% of users shown the original prices.
**ARPPU**	The average revenue per paying user during the price review period.