How this calculation works
Use an entered creator RPM after platform share, or model one from advertiser CPM, ad impressions per thousand total video views and an explicit share. Divide the revenue goal by that rate and round views up to the next whole count. Divide the whole monthly target by the stated month length for a daily average.
Required whole views = ceil(revenue goal × 1,000 / creator RPM)A worked example
A 2,000 revenue goal with a creator RPM of 6.60 needs 303,031 whole monthly views. The old CPM scenario reaches the same modeled RPM with 12 advertiser CPM, 1,000 ad impressions per 1,000 video views and a 55% share; those are assumptions rather than a universal rate conversion.
Good to know
Constant-rate revenue target with no costs, taxes, audience growth, eligibility or future rate prediction. CPM mode requires a separately justified ad-impression to total-view assumption. A positive goal needs a positive effective RPM. Whole-view rounding can make modeled revenue slightly exceed the goal.
Reference: YouTube: distinguish creator RPM from advertiser CPM (opens in a new tab) ↗
Reverse the revenue calculation without reversing its meaning
The familiar revenue identity multiplies total views by creator revenue per thousand views and divides by one thousand. This tool solves for the view count instead. For a goal of 2,000 and a creator RPM of 6.60, the unrounded requirement is about 303,030.303 views. Because a whole view target must not fall short of the goal under the stated model, the displayed minimum is 303,031.
A target calculated this way is not a forecast of how many views a channel will obtain. It is conditional on the revenue basis remaining constant. The YouTube income scenario calculator goes in the opposite direction, combining entered views with separate revenue and cost assumptions. Use the same currency and event definition when moving a result between the two tools.
Advertiser CPM needs an impression assumption before it becomes creator RPM
Advertiser CPM prices ad impressions. Creator RPM summarizes creator revenue against total video views after the relevant platform share. Multiplying every advertiser CPM by a share does not account for the possibility that ad-impression counts differ from total video views. The explicit CPM mode therefore asks for ad impressions per thousand total video views as well as the assumed share.
The defaults preserve the original page’s scenario of one ad impression per video view and a 55% share. They are editable assumptions, not claims that finance content always attracts a certain rate or that every view shows exactly one ad. If you already have creator RPM on a matching basis, enter it directly and avoid applying a second share deduction. The RPM CPM calculator can help inspect a separately supplied amount and event count.
A monthly target and a daily average use different rounding conventions
The monthly target rounds upward once to a whole view count. Its daily average divides that target by the month length you entered, so it can be fractional. The tool does not round every daily average upward and then claim that the sum exactly equals the original monthly target. Choose actual calendar days if you need a particular month rather than an average-month scenario.
The sensitivity table halves and doubles the entered or modeled RPM while holding the goal fixed. These are arithmetic comparisons rather than industry benchmarks. A lower rate increases the required view count, and a zero rate cannot reach a positive revenue goal in this model. Production costs, taxes, seasonality, eligibility and uncertain audience growth remain separate questions rather than hidden adjustments to the target.
A few questions, answered
Should I enter CPM or RPM?
Use creator RPM when you have a rate per thousand total video views after platform share. CPM mode needs additional explicit ad-impression and share assumptions.
Why round the monthly views upward?
Rounding down can leave modeled revenue below the stated goal. The unrounded requirement is shown separately.
Can a zero goal have a result at zero RPM?
Yes. A zero goal needs zero views in this model. A positive goal at zero effective RPM is rejected as unattainable.