Gaming Frame Rate A/B Test Monthly Impact Formula
Learn how to estimate monthly conversion lift and added value from testing a higher game frame rate.
This calculation estimates the expected monthly impact of assigning some eligible players to a higher-FPS experience. It combines the traffic split, baseline conversion rate, assumed relative conversion uplift, and value per conversion to show the estimated incremental result against an all-control baseline.
- 100% Free
- No Sign-Up Required
- Private & Secure
- Mobile Friendly
Incremental Monthly Value
Where:
Only players assigned to the test receive the assumed conversion change. The formula calculates the extra conversions expected from that group, then multiplies them by the value of one conversion.
Variables Explained
| Variable | What It Means | Unit |
|---|---|---|
| monthlyPlayers - Monthly eligible players | The number of players who can potentially be included in the experiment during a typical month. | players |
| testAllocation - Test traffic allocation | The percentage of eligible players assigned to the higher-frame-rate variant. | percent |
| controlConversionRate - Control conversion rate | The baseline conversion rate for players receiving the current experience. | percent |
| expectedConversionUplift - Expected conversion uplift | The assumed relative percentage change in conversion rate for the higher-FPS variant. | percent |
| valuePerConversion - Value per conversion | The average revenue or internal value assigned to one conversion. | currency |
| controlFrameRate - Control frame rate | The average FPS of the current player experience. | FPS |
| testFrameRate - Test frame rate | The average FPS available in the test experience. | FPS |
Step-by-Step Calculation
Find the frame rate increase
Subtract the control FPS from the test FPS to show the absolute performance difference being tested.
frameRateIncrease = testFrameRate - controlFrameRate
Split eligible players between groups
Calculate the number of eligible monthly players assigned to the higher-frame-rate variant.
testPlayers = monthlyPlayers * (testAllocation / 100)
Convert the control rate to decimal form
Conversion rates entered as percentages must be divided by 100 before multiplying by player counts.
controlConversionRateDecimal = controlConversionRate / 100
Estimate the test conversion rate
Apply the assumed relative uplift to the control conversion rate. This produces a projected rate, not an observed experiment result.
testConversionRate = controlConversionRate * (1 + expectedConversionUplift / 100)
Calculate projected conversions
Add expected control-group conversions to expected test-group conversions.
projectedMonthlyConversions = monthlyPlayers * (1 - testAllocation / 100) * (controlConversionRate / 100) + testPlayers * (testConversionRate / 100)
Calculate the all-control baseline
This is the expected conversion count if every eligible player received the control experience.
baselineMonthlyConversions = monthlyPlayers * (controlConversionRate / 100)
Calculate lift and value
The difference from the baseline is the expected incremental conversion lift; multiplying it by value per conversion estimates added monthly value.
incrementalMonthlyRevenue = (projectedMonthlyConversions - baselineMonthlyConversions) * valuePerConversion
Example: 60 FPS test versus 30 FPS control
Frame rate increase
60 - 30
30 FPS
Test players
100,000 × 50%
50,000 players
Estimated test conversion rate
5% × (1 + 5% / 100)
5.25%
Projected monthly conversions
50,000 × 5% + 50,000 × 5.25%
5,125 conversions
All-control baseline conversions
100,000 × 5%
5,000 conversions
Incremental conversions
5,125 - 5,000
125 conversions
Incremental monthly value
125 × $10
$1,250
Final Result
With a 30 FPS increase and a 5% assumed relative conversion uplift, the 50/50 experiment is estimated to add 125 monthly conversions and $1,250 in monthly value.
Assumptions
- ✓Eligible player volume remains broadly stable throughout the month.
- ✓The expected uplift is a relative change from the control conversion rate, rather than a percentage-point increase.
- ✓The traffic allocation is implemented as entered and players are exposed to their assigned experience.
- ✓Each conversion has the same average value used in the calculation.
- ✓The higher frame rate is the main meaningful difference between the test and control variants.
Limitations
- !The model estimates an expected outcome and does not establish that frame rate causes a conversion change.
- !Actual effects may vary by game genre, device performance, network conditions, player segment, and conversion event.
- !The calculation does not measure statistical significance, confidence intervals, or experiment power.
- !A monthly player count may include players with unequal exposure time or different opportunities to convert.
- !Average value per conversion can differ across player cohorts and transaction types.
Common Mistakes to Avoid
Entering a percentage-point change as a relative uplift; for example, moving from 5% to 5.25% is a 5% relative uplift, not a 0.25% uplift.
Assuming that a larger FPS increase automatically produces a larger conversion increase.
Using total game installs instead of the players actually eligible to see the experiment.
Treating projected lift as a statistically validated test result.
Using gross purchase value when the intended metric is a different internal conversion value.
Forgetting that only the test allocation receives the projected uplift during the experiment.
Related Formulas
Frequently Asked Questions
How is incremental monthly conversion lift calculated for a gaming FPS A/B test?
It is the difference between projected mixed-group conversions and the conversions expected if all eligible players received the control experience. With a relative uplift assumption, it equals test players multiplied by the control rate and uplift.
How do I calculate the test conversion rate from a relative uplift?
Multiply the control conversion rate by 1 plus the uplift divided by 100. For example, 5% with a 5% relative uplift becomes 5% × 1.05, or 5.25%.
Does the frame rate increase appear directly in the monthly value formula?
No. FPS difference describes the performance change being tested. The financial estimate uses the conversion uplift assumed or observed for that change.
Can expected conversion uplift be negative?
Yes. A negative uplift models a projected decline in conversion for the test variant and produces negative incremental conversions and value.
Why does test allocation change estimated monthly impact?
The assumed effect applies only to players in the test group. More test traffic exposes more eligible players to the projected change during that month.
Ready to calculate your result?
Use the calculator to get instant results with your own inputs.