Why Session RPM Should Replace Page RPM as Your North Star Metric

Page RPM rewards decisions that quietly shrink your audience. Session RPM captures the full trade-off between ad load and reader behavior — and changes what you optimize.

Page RPM has a flaw that costs publishers real money: it can't see the reader leave. Add a third interstitial and page RPM rises — while sessions shorten, return visits decline, and total revenue eventually falls. The metric applauded the decision that hurt you.

Session RPM — revenue per thousand sessions — internalizes the trade-off. Aggressive ad load that truncates sessions shows up immediately as flat or falling session RPM even while page RPM climbs. It converts the ads-versus-experience debate from a values argument into an empirical question with one answer.

In practice, switching north-star metrics changes decisions within weeks. Density tests get judged on whether readers consume fewer pages, not just whether each page earns more. Refresh strategies get evaluated against session depth. Layout experiments that page RPM would have shipped get correctly killed.

The migration is straightforward: reconcile ad revenue against analytics sessions daily, segment by traffic source and template, and re-baseline your historical experiments. Most publishers discover at least one 'winning' change from the past year that session RPM would have rejected — which is precisely the point.