Pub360Publisher operating system
Ad Monetization

RPM, CPM, and Clicks: Ad Metrics Explained for Editors

A plain-English explanation of RPM, CPM and clicks for editors, using a small publisher example and common mistakes.

Lena Patel
Lena PatelAd Monetization Contributor4 min read
Revenue metrics workbook with pageview bars and click-rate calculation blocks

Editors do not need to become ad analysts, but they do need to know when a revenue chart is lying by omission. RPM, CPM, and clicks answer different questions. Mixing them up leads to bad editorial decisions: more ads on the wrong page, panic over a normal traffic change, or a headline strategy that chases accidental clicks.

Here is the clean version.

RPM tells you what pages earned per thousand views

RPM means revenue per thousand pageviews. If an article made $18 from 12,000 pageviews, its page RPM is $1.50. That number helps editors compare pages with different traffic levels.

Use RPM when the question is editorial: “Which type of article earns enough to justify more coverage?” It is not perfect, but it is more useful than total revenue when one page had 100,000 visits and another had 4,000.

Small publisher metrics notes comparing RPM, CPM, clicks and pageviews

CPM belongs closer to the ad buyer and placement

CPM means cost per thousand ad impressions. It is often tied to ad impressions rather than pageviews. One pageview can create several ad impressions, or none if the reader leaves quickly or an ad fails to load.

Editors should be careful with CPM because it can make a placement look healthy even when the page experience is poor. A high CPM unit that appears too early may earn money while lowering reader trust, newsletter signups, or return visits.

Clicks are a warning light, not an editorial goal

Clicks matter for some ad models, but editors should not write or arrange pages to encourage accidental clicks. A sudden click spike can mean interest, but it can also mean confusing layout, a too-close button, or mobile spacing that needs review.

If clicks rise while time on page falls or complaints increase, treat it as a layout problem first. The best small publishers protect the difference between a reader choosing an ad and a reader being tricked by the page.

A tiny example

Imagine three articles in one week.

Article Pageviews Revenue Page RPM Editorial read
Tax deadline explainer 20,000 $24 $1.20 Useful traffic, moderate value.
Niche software comparison 3,000 $18 $6.00 Small audience, strong commercial intent.
Viral opinion post 80,000 $32 $0.40 Big reach, weak monetization.

The wrong conclusion is “write only viral opinion because it made the most money.” The better conclusion is that niche comparison topics may deserve careful expansion, while viral posts may serve audience growth rather than direct ad value.

What editors should ask in revenue meetings

Ask which page type changed, which device changed, and whether the ad layout changed at the same time as traffic. A revenue dip after a template release means something different from a revenue dip after a holiday weekend.

Also ask for ranges. Editors do not need five decimal places. They need to know whether a story type is low, steady, unusually high, or too volatile to trust.

After the metrics make sense, review these next

Mapping Ad Inventory Before You Change Your Theme, A Monthly Ad Policy Review Routine for Lean Teams, and AdSense Layout Basics for Reader-Friendly Pages.

The metric hierarchy I prefer

For editorial planning, start with reader intent, then page RPM, then recirculation or signup behavior. CPM and click data are useful diagnostic tools, but they should not run the calendar.

A small publisher grows stronger when editors can read the money without letting the money flatten the editorial judgment.

Do not compare metrics across unrelated pages

A glossary-style explainer, a tool comparison, and a breaking-news post have different reader intent. Comparing their RPM without context can push the calendar toward the wrong work. Group pages by type before drawing conclusions. A low-RPM article that brings loyal newsletter subscribers may still be valuable.

Editors should ask what job the page performs. Some pages earn directly. Some build trust. Some bring new readers into a sequence that earns later.

Use metric changes as prompts for questions

If RPM drops, ask whether traffic source changed, ad viewability changed, page speed changed, or topic mix changed. If clicks rise suddenly, check layout before celebrating. If CPM looks strong but revenue is flat, inspect ad impressions per pageview and fill rate.

The numbers are not commands. They are prompts for better questions. That distinction keeps editors involved without making them chase every fluctuation.

Read next