AdSense Page RPM or Active View: Which Metric?

Small-blog owners Google two different questions with similar anxiety: “Am I earning fairly per visit?” and “Are ads actually visible?” Page RPM and Active View answer different ones. Mixing them creates layout churn while earnings noise is really low traffic—or RPM panic while the real issue is unfilled requests.

Early owners for this cluster:

• AdSense Page RPM report basics for small blogs
• AdSense Active View viewability basics
• AdSense CPM vs RPM for small blogs
• AdSense Ad units report basics for small blogs

Earnings rate per pageview → Page RPM owner. Visibility on measurable impressions → Active View owner. This page routes only.

Official Help: Page RPM · Active View data in reporting · Active View Viewable · Revenue per thousand impressions (RPM) · Overview of AdSense Reports. Confirm live.

Disclosure: Educational AdSense reporting only. No niche RPM or viewability benchmarks, no guaranteed earnings from layout tweaks.

Table of contents

1. Why RPM and Active View collide in search
2. What Page RPM is for
3. What Active View is for
4. Which report to open first
5. Reading both without false causation
6. Scenarios on low traffic
7. When ad units report enters the stack
8. Mistakes this router stops
9. FAQ
10. Pick one metric job and leave

Why RPM and Active View collide in search

Both metrics appear in Reports, both relate to ads on pages, and forum threads use “RPM” and “viewability” in the same breath. Google defines them separately:

Page RPM (Help): estimated earnings divided by pageviews, times 1,000—a rate tied to pageviews.

Active View Viewable (Help): percentage of measurable impressions that were viewable under IAB rules—a visibility statistic on ad impressions, not on pageviews.

Beginners merge them because a layout change can coincide with an earnings swing on a 30-pageview day. Coincidence is not definition. CashPilot splits owners so each searcher gets depth without cloning both walkthroughs.

If I were advising a publisher who said “RPM crashed after I moved the sidebar,” I would confirm pageview volume and estimated earnings first on the Page RPM owner, then ask whether impressions still serve—only then open Active View if visibility is the actual hypothesis.

What Page RPM is for

Use Page RPM when you need earnings scaling language:

• Compare weeks on the same site with enough pageviews to dampen noise.
• See whether estimated earnings fell because traffic dropped or because rate moved.
• Pair with CPM vs RPM when someone cites Ad RPM but you filtered Page RPM—or vice versa.

Page RPM does not prove:

• Cash in bank (estimates finalize later).
• That readers looked at ads (visibility is Active View).
• That a single unit caused site-wide change without ad units report scope.

Help formula reminder: Page RPM = (Estimated earnings ÷ Pageviews) × 1,000. Illustrations in Help teach math—not niche benchmarks.

What Active View is for

Use Active View when ads serve but you need visibility literacy:

• Active View Viewable = viewable measurable impressions ÷ measurable impressions (Help).
• Display viewability generally requires 50% of ad area on screen for one continuous second (Help); video thresholds differ.
• Not all impressions are measurable—cross-domain iframes and early exits shrink measurable denominators.

Active View does not replace:

• Coverage/fill diagnosis when requests fail to return ads.
• Page RPM when the question is earnings per visit.
• Content strategy or traffic growth.

Inventory note from Help: Active View Viewable includes regular AdSense for Content and AdSense for Video units; link units and Ad Manager dynamic allocation are excluded—your columns tell a partial story if those formats dominate.

Which report to open first

Router rule: no impressions → fix serving/fill first. Impressions with earnings noise → Page RPM with stable dates. Impressions with layout suspicion after fill is healthy → Active View.

Reading both without false causation

Strong Active View does not cause strong Page RPM—advertiser demand, geo mix, and seasonality move rates independently. Weak Active View on a long article with below-fold units may coexist with acceptable RPM on short pages where ads sit high.

Mechanism: RPM aggregates money estimates; Active View aggregates visibility counts on a subset of impressions. A page can earn modest RPM while viewability looks fine if CPMs are soft, or RPM can spike on low traffic while viewability looks ugly on one heavy unit.

Read both over matching date ranges but do not merge columns into one “health score” unless you enjoy false alarms.

Scenarios on low traffic

Scenario A — 40 pageviews, Page RPM doubles overnight
Likely sample noise. Widen the window; check estimated earnings numerator before moving ads.

Scenario B — 400 pageviews, earnings flat, Active View Viewable drops on one unit
Open ad units report for that unit name; compare mobile vs desktop if your report allows; read Help viewability best practices before deleting units.

Scenario C — RPM down, Active View unchanged
Suspect traffic quality, geo, or rate factors—not visibility alone. Return to Page RPM owner habits.

Small blogs should prefer weekly or monthly slices once pageviews allow—single-day cells lie.

When ad units report enters the stack

Site-wide Page RPM hides placement stories. Active View added by unit (when your report supports the dimension) helps explain “sidebar dead on mobile” without blaming account-wide RPM.

Sequence:

1. Confirm impressions exist (Performance overview or unit report).
2. Page RPM at site scope for earnings context.
3. Active View at unit scope if visibility is the hypothesis.
4. Layout experiments one change at a time—no benchmark promises on this page.

Mistakes this router stops

1. Treating Active View as an earnings grade — It is visibility on measurable impressions.
2. Optimizing viewability before fill — Coverage issues masquerade as layout problems.
3. Comparing Page RPM to Active View numerically — Different denominators and meanings.
4. Booking income from one RPM cell — Estimates ≠ payments.
5. Deleting units off one day of Active View — Low measurable counts exaggerate swings.
6. Skipping ad unit scope — Site totals blame the wrong placement.

FAQ

Frontmatter holds eight schema-ready answers. Short version: Page RPM = earnings rate per pageview; Active View = viewability on measurable impressions; use owners for depth; router picks order.

Pick one metric job and leave

Name the question aloud before you open Reports. If the sentence includes “per thousand pageviews” or “earnings rate,” open Page RPM basics. If it includes “viewable” or “on screen,” open Active View basics. If it includes “which ad block,” open ad units report basics. Mixing all three on day one is how small blogs rearrange themes while requests still return no ads—pick one job, finish it, then return only if the next question is different.