AVAIVUVPublisher Lab
Scenario planning

Ad Revenue Scenario Planner

Explore how a change in traffic and page RPM could affect a monthly estimate. Define a downside and upside case rather than treating one RPM as certain.

Enter your report values

Use a representative monthly pageview total.
Use a measured, comparable page RPM.
Percentage change applied to baseline traffic; cannot be below -100%.
Percentage change applied to baseline RPM; cannot be below -100%.
Change for the upside case; choose an evidence-based assumption.
Change for the upside case; it is not a promise.

Your result

Enter your values and select Calculate to see the result.

Formula used

Scenario revenue = adjusted pageviews ÷ 1,000 × adjusted page RPM

Worked example

With 100,000 pageviews and a $4.50 RPM, the baseline is $450. A case with 15% less traffic and 20% less RPM estimates $306; a case with 15% more traffic and 10% more RPM estimates $568.13. All three are assumptions, not forecasts.

Why use scenarios?

Publisher earnings can move because traffic changes, the value of each pageview changes, or both. A single number hides that uncertainty. Low, base and high cases make the assumptions visible so a business plan does not depend on one optimistic result.

Worked scenario

Start with 100,000 pageviews and a $4.50 page RPM, yielding a $450 baseline estimate. In the downside case, reduce traffic by 15% and RPM by 20%: 85,000 pageviews × $3.60 ÷ 1,000 = $306. In the upside case, increase traffic by 15% and RPM by 10%: 115,000 × $4.95 ÷ 1,000 = $569.25. The calculator uses your exact inputs and rounds only for display.

Choosing assumptions responsibly

Use measured historical periods and explain why each assumption is plausible. Do not use the largest RPM ever recorded as the baseline without checking whether the sample was unusual. If the site is seasonal, compare similar months or weekdays. If you recently changed ads or content, separate the period before the change from the period after it.

What the model leaves out

This model assumes one pageview-level RPM can summarize the selected traffic. It does not model auction demand, country and device mix, consent, ad density, viewability, invalid traffic adjustments, reporting delays, taxes or operating costs. It also does not predict whether new content will rank or attract users.

Use the model as a decision aid

  1. Record the baseline and source period.
  2. Enter conservative downside changes first.
  3. Write a short reason for each upside assumption.
  4. Check the range against actual results as new data arrives.
  5. Update the model only when the underlying evidence changes, not to make a target look achievable.

Google describes RPM as a ratio of estimated earnings to a chosen denominator, multiplied by 1,000. The denominator must match the metric. This planner specifically uses pageviews and page RPM.

Frequently asked questions

Are the high and low cases predictions?

No. They are transparent what-if calculations driven by the assumptions you enter.

Can an RPM rise while total revenue falls?

Yes. If pageviews decrease enough, the higher revenue per thousand views may not offset the traffic decline.

Should I enter a 100% downside RPM change?

It yields zero RPM and zero estimated revenue; it is mathematically permitted but usually represents an extreme stress case.

Related tools

These tools summarize the values entered. Check the source report and keep metric definitions consistent before making a publishing decision.