Back to Blog
GoScript Journal

RPM vs CPM and What They Mean for Your Revenue

·7 min read·GoScript Team /Research

The direct answer to reading the gap

RPM is the number to watch for your actual take-home from views, not CPM. CPM tells you what an ad buyer paid, but after splits and ad load, the number left for you is RPM. So when you scan analytics, compare RPMs between videos before comparing raw CPMs for any guess about income.

In practice, a video with a lower CPM can still earn more if it has a higher ad load or longer watch time. That gap is why reading revenue analytics means stopping at CPM and going straight to RPM for a fair look at what each view puts in your pocket.

How to read them side by side

Pull RPM and CPM for the same date range for a single video in your analytics panel. Do not mix all-time with a 28-day window, as shifts in traffic will skew the numbers. For each clip, note the views, RPM, estimated revenue, and traffic source to spot a pattern over time.

When two videos have close views, the one with a few extra cents of RPM will often pull ahead. This only holds true if the sample size is not one day of traffic. Let at least seven days run before judging a small lift as real.

When the gap widens

Some niches pay well for ads but run fewer of them, so CPM looks high while RPM stays flat. Other niches run more ads and keep viewers longer, so RPM climbs even if CPM looks modest. Your job is to find where those two meet for the content you already have.

Keep notes on video length for any test. Going from short clips to longer explainers may not spike CPM, but it can raise RPM enough to cover the effort if watch time holds steady.

Key takeaways

  • Watch RPM, not CPM, to judge your real take-home from views.
  • Compare the same date range and avoid single-day samples.
  • Look for ad load and watch time as the hidden drivers.
  • Test length changes against RPM, not just CPM.
  • Track one variable at a time to keep results clear.

Small test to run this week

Pick three of your highest-view videos from the last 30 days. For each, log RPM, CPM, views, and traffic source in one row. After seven more days, log the same row again and see which one moved most. That single table will tell you more than guessing at broad averages for your channel.

Turn this into your next script.

Analyze a channel, extract its structural DNA, and generate scripts engineered from patterns that actually work.

Analyze a Channel