Plugin workflow
Reading the PushRPM Dashboard
Make sense of the PushRPM dashboard — the site scan score, the revenue leak detector, and before/after proof — and know what each number means.
Main intent
Orient new customers so they can interpret the core dashboard surfaces and trust the numbers.
Short answer
The dashboard has three pillars: the scan score grades how well your monetization and Core Web Vitals are set up, the leak detector estimates revenue you are losing, and proof shows measured before/after results once AdSense is connected.
The site scan score
PushRPM crawls your real pages with a headless browser and measures placement quality, ad density, viewability, and Core Web Vitals (real LCP and CLS, not guesses). The 0–100 score summarizes how healthy your monetization setup is. A lower score means more opportunity; tap into it to see the specific findings behind the number.
- Built from real page scans, not a checklist.
- Core Web Vitals (LCP, CLS) are measured live during the scan.
- Per-article scores show which posts have the most room to improve.
The revenue leak detector
Each leak is an estimate of revenue you are likely losing, calculated as the gap between your RPM and a niche benchmark, applied across your pageviews and scaled by a confidence range. Before AdSense is connected the RPM is an estimate; after connecting, leaks use your measured RPM and become much sharper. Leaks are framed as ranges, never false-precision single numbers.
- Formula: (benchmark RPM − your RPM) × pageviews ÷ 1000 × confidence.
- Shown as a range with a confidence level, not a guaranteed figure.
- Measured RPM (after AdSense connect) tightens every estimate.
Before/after proof
Proof shows the measured impact of changes PushRPM applied: revenue, RPM, or Core Web Vitals before a change versus after. Per-article proof uses per-page AdSense revenue where available. Proof is only as strong as the data behind it — early on, with little measured history, ranges are wide and clearly labelled.
The cross-site brain (cold start)
PushRPM gets smarter as more sites in your niche are optimized, using only anonymized, aggregated, minimum-cohort patterns — never another site's raw data. When your niche has too few sites yet, the brain is in cold start and falls back to seed benchmarks; it is honest about this rather than inventing confidence.
Measured vs estimated — read the labels
Throughout the dashboard, numbers are labelled measured (from your connected AdSense) or estimated (from niche benchmarks). Treat estimated figures as direction, not promises, and connect AdSense to move them to measured.
Implementation checklist
- Run a scan and review the score plus its findings.
- Open the leak detector and read leaks as ranges, not guarantees.
- Connect AdSense to switch estimates to measured RPM.
- Check proof after PushRPM applies changes.
- Note the measured-vs-estimated label on every figure.
Common mistakes
- Reading an estimated leak as guaranteed recoverable revenue.
- Expecting strong proof before enough measured history exists.
- Ignoring the scan findings and looking only at the score number.
Example
A new site shows an estimated leak range and a cold-start brain. After connecting AdSense and applying a few safe changes, the same surfaces show measured RPM and a real before/after in proof.
Use a related tool
Continue in PushRPM
FAQ
Why is my RPM 'estimated'?
Until you connect AdSense, PushRPM uses niche benchmark RPM. Connect AdSense and the figure becomes measured from your real revenue.
Are leak amounts guaranteed?
No. Leaks are confidence-ranged estimates of likely lost revenue, not promises. They get sharper once measured data is flowing.
Why does the brain say cold start?
Your niche does not yet have enough optimized sites to form an anonymized cohort, so PushRPM uses seed benchmarks until it does — and tells you so.
Related docs
Connect Your AdSense Account to PushRPM
Link your Google AdSense account to PushRPM with one click so the engine measures real RPM and revenue per page instead of estimates.
PushRPM Autopilot Modes Explained
Understand PushRPM's autopilot modes — manual, assisted, autopilot safe, and autopilot growth — and choose how much PushRPM applies on its own.
Ad Performance and Core Web Vitals
Understand how ad scripts, layout stability, loading behavior, and placement decisions affect Core Web Vitals.