RPM analyzer
“Revenue is down this month” is not actionable. Monetific imports your earnings export and shows you which day RPM actually broke, how far it fell against the preceding week, and what usually causes a fall of that shape.
What you get
- RPM, CTR and fill rate by day, per network
- Period-over-period comparison against the immediately preceding window of equal length
- Anomaly flags when a day falls more than 35% below the trailing seven-day median — or spikes more than 60% above it, which is worth checking before it is clawed back as invalid traffic
- Best and worst day by RPM, not by raw revenue
Frequently asked
- How is RPM calculated here?
- Revenue divided by pageviews, multiplied by a thousand. Everything is computed in integer micros and only converted for display, so repeated aggregation never introduces rounding drift.
- Why compare against a median instead of an average?
- Because one unusually good day pulls an average up enough to hide the collapse that follows it. Comparing each day against the median of the previous seven makes a genuine drop visible on the day it happens.
- What does an RPM drop usually mean?
- In order of frequency: an ad unit that stopped rendering after a theme change, an ads.txt line that disappeared, a policy action limiting demand, and only then a real change in traffic mix. The first two are the reason Monetific monitors ads.txt alongside this.
- Which CSV exports are supported?
- The standard AdSense and Ezoic day-level exports. Column headers are matched loosely — Date, Day, Report date; Estimated earnings, Revenue, Earnings — so most network exports import without editing.