RPM Drop Diagnosis Checklist

RPM Drop Diagnosis Checklist helps a publisher or creator separate normal volatility from a change that deserves investigation.

Start by naming the metric. Page RPM, ad request RPM, CPM, YouTube RPM, Shorts RPM, and sponsorship revenue per view do not describe the same thing. Each metric has a different denominator and a different business meaning. Before comparing numbers, write what metric is being reviewed and where it was measured.

Next choose the comparison window. A single day can be misleading. Compare against the previous similar weekday, the previous four-week average, the same season last year if available, and a period before any major content, template, traffic, or platform change. If the site or channel had a recent viral spike, use a baseline that excludes the spike. The point is to avoid treating an unusual high as normal.

Then segment traffic. Look at country, device, source, page group, content category, new versus returning users, search versus social, and video surface when available. A lower-RPM traffic source can grow and pull the average down even if monetization on the original audience remains stable. Conversely, traffic can stay flat while monetization coverage or ad demand changes.

After that, check monetization coverage. For websites, review ad impressions, ad requests, coverage, viewability, policy center status, consent behavior, template changes, and page speed changes. For video, review monetized playbacks, revenue source mix, geography, long-form versus Shorts mix, upload type, and whether any content has limited eligibility. Do not assume the answer before segmenting.

Finally write the action state: wait and monitor, revert a recent change, run a controlled layout test, inspect policy/eligibility, or escalate with a clean packet. The checklist does not guarantee recovery. It prevents random fixes from making the signal harder to read.

RPM Drop Diagnosis Checklist

// COMMENTS

ON THIS PAGE