<b>Optimizing Session RPM, not Page RPM</b>

<b>Optimizing Session RPM, not Page RPM</b>

What it does: not a plugin — a measurement switch. Judge every ad lever by revenue per session, not per pageview, so you stop rewarding tactics that boost one page while killing return visits.

Setup effort: 2/5 — it's an analytics view (revenue / sessions), available in GA4 + your ad reporting.

RPM lift seen: no lift by itself, but it reframes every other test. Density and refresh changes that 'win' on Page RPM often lose on Session RPM once pages/session drops. Switching the target metric typically reveals 10-20% of phantom gains.

Pros
— Catches UX damage that Page RPM hides
— Aligns monetization with retention and LTV

Cons
— Noisier metric; needs more traffic for significance
— Forces honesty about tactics you liked

Verdict: make Session RPM the headline number for every ad experiment. Page RPM lies by omission. Lift: ★★★★☆ — Risk: ★☆☆☆☆
Best for: anyone running multiple ad tests. No one optimizing seriously should skip this.