Does GDPR affect Page RPM?

Yes, and the gap can be significant

Under GDPR, EU and UK visitors have to actively consent before you can serve personalized ads. Visitors who decline can usually still be shown non-personalized ads, but non-personalized inventory typically earns meaningfully less, because advertisers can't target it as precisely.

Why non-personalized ads pay less

Personalized ads let advertisers bid based on a visitor's interests, browsing history and likely intent, all of which push up the price they're willing to pay. Strip that targeting away and you're left with basic contextual ads: a smaller, less competitive pool of demand bidding on the same inventory.

Consent rates matter as much as the regulation itself

Two sites with identical GDPR compliance can see very different results depending on how many visitors actually accept the consent prompt. A confusing or overly aggressive consent flow that drives rejections will cost you more revenue than the regulation itself does.

This is part of why country tier matters

It's one of the reasons Tier 1 traffic from the US typically out-earns similarly sized EU traffic on a per-pageview basis, alongside the underlying differences in advertiser spend. See our breakdown of Page RPM by country for the fuller picture.

What publishers can actually do

Use a Google-certified Consent Management Platform (CMP), keep the consent prompt simple and honest, and check your ad network's dashboard for a personalized-versus-non-personalized revenue breakdown so you know exactly how much this is costing you.

Want to see how this factors into your overall numbers? Try the Comprehensive Page RPM Calculator.