A reader your ad server actually recognizes is worth more than one it doesn’t. Sites using first-party identity data see CPM uplifts of 25-40% and roughly double the ad fill rate compared to anonymous traffic (Ezoic ezID data). That’s not a marketing number. It’s more buyers competing for the same impression, because they pay more for someone they can target with confidence.
If you run an ad-supported or hybrid site, that gap is the single biggest lever left on your page. Here’s what’s driving it, and how to close it.
Third-party cookies didn’t die. They just stopped being enough.
Google backed off its plan to kill third-party cookies in Chrome. It announced it would keep cookies enabled by default and drop the standalone opt-out prompt it had been testing. Not long after, it shut down most of Privacy Sandbox, the replacement tracking system it had spent years building, citing low adoption.
If you stopped worrying about cookie deprecation after that news, you stopped too early.
Chrome keeping cookies doesn’t put the identity landscape back the way it was. Safari has blocked third-party cookies since 2020. Firefox partitions them by default through Total Cookie Protection. Together with Brave, that covers 17-20% of global traffic where third-party cookies already don’t work, and more than half of iOS traffic specifically.
Consent law hasn’t relaxed either. GDPR requires consent before tracking. The CCPA gives readers the right to opt out of having their data sold or shared. Different mechanisms, same direction: regulators keep tightening the rules around anonymous tracking, cookie or no cookie (France fined Google 325 million euros over cookie consent violations).
The cookie didn’t die in one headline. It’s been dying browser by browser and law by law for years, and Chrome’s reversal doesn’t undo that. Your match rates on the open exchange keep sliding whether or not “deprecation” is in the news this week.
First-party data sidesteps the consent problem too. When a reader creates an account on your site, they’re handing you their email address directly, with full knowledge of who’s getting it and why. There’s no third-party sharing to disclose, and nothing complicated to explain in a privacy policy. The data is clean because you collected it the honest way.
What an identified reader is actually worth
Here’s the mechanism behind the CPM gap. When a buyer can bid on a known reader instead of a guess, it bids with more confidence, and confidence shows up as price. Ezoic’s platform data shows Prebid partners paying about 25% more on average for identified inventory, and Google demand paying up to 40% more on the same traffic. Fill rate roughly doubles, because more buyers are willing to bid at all once they know who they’re bidding on instead of passing on the impression entirely.
Run that across your own traffic and the math gets concrete fast. A site pulling 2 million monthly pageviews at a $4 blended CPM is running about $8,000 a month in ad revenue. Move a third of that traffic from anonymous to identified at a 30% CPM lift. That’s roughly $800 a month added, before the fill rate gains are even counted. Scale that to a year and you’re funding a hire.
Looking to grow your publication?
Sign up for expert advice straight to your inbox.Publishers have noticed the shift. 71% now say first-party data plays the most significant role in their ad revenue performance, up from 64% the year before. 85% expect it to be their single biggest driver next year (Digiday+ Research). That’s not a fringe opinion inside ad ops. That’s most of the industry telling you where the money already moved.
It’s not just CPM. It’s deals you can’t get with a cookie.
Identity data doesn’t only help you win more on the open exchange. It’s what lets you sell direct.
Selling direct means selling an audience you can describe with confidence: readers who follow your local government coverage, your outdoor gear reviews, or your high school sports section. A cookie can approximate that audience. A registered reader who told you their interests, or whose reading history lives in your own database, is that audience, verified.
Buyers pay a premium for certainty. First-party data is what turns “we think this traffic skews toward X” into “here are 40,000 readers who opened our food newsletter last month.” That’s a sentence that closes a direct deal instead of stalling one.
The same segmentation works for house ads and sponsored content, not just programmatic. A sponsor who wants outdoor-gear readers doesn’t want your whole homepage. They want the segment, and a registration wall is what lets you hand them one with a real number attached instead of a guess.
The fastest way to build first-party data: make readers log in
Cookies, fingerprinting, and third-party tracking networks are all workarounds for one problem: you don’t actually know who’s reading you. A registration wall solves that directly. It asks for an email address in exchange for continued access, and it asks before the reader leaves your site, not after they’ve already gone.
This isn’t a marginal edge over a newsletter popup. Salem Reporter ran a registration wall against its standard newsletter signup forms in a clean 30-day head-to-head test. The wall captured 16 times more email addresses (we’ve watched this margin hold up on other sites, not just Salem’s).
Small changes to the ask compound fast. The Fisherman swapped an in-content, email-and-password prompt for a full-width, email-only overlay. Nothing else on the page changed, and registrations jumped 10x in two weeks. You don’t need to rebuild your whole registration flow. You need to make the ask easy to say yes to.
Leaky Paywall’s List Builder is built for exactly this. It puts a registration wall in front of gated content, natively inside WordPress, and syncs every signup straight into your existing email platform. Because it runs on WordPress instead of a JavaScript overlay, it also blocks the AI scrapers that read your content for free and never send a click back.
“Won’t a registration wall cost me pageviews?”
This is the objection every ad-supported publisher raises before testing one, and it’s worth answering directly instead of dodging it.
A registration wall placed after the first article doesn’t block search traffic or homepage browsing. It only fires when an anonymous reader tries to go past what you’ve decided to give away for free. Mexico News Daily put a registration wall on article two and a paywall on article three. In about a year and a half, their monthly traffic grew from under 500,000 to 1.4 million visitors. Their email list tripled over the same stretch.
Traffic didn’t drop. It grew, because a chunk of readers who used to leave with nothing now leave with an account, an email address, and a reason to come back. Every one of those accounts is inventory your ad server can price with confidence next time that reader shows up.
Where to start
You don’t need to rebuild your ad stack to act on this. Three steps get most publishers moving:
Audit what you’re gating today. If you’re running a newsletter popup and nothing else, you’re leaving registrations on the table. A wall placed after the first free article outperforms a popup on every metric that matters, including how many of those signups turn into repeat, identifiable visits.
Set the wall to fire early. One free article, then a registration prompt, catches far more of your traffic than a wall that waits until article three or four. Most readers never get that far.
Connect the signups to your ad stack, not just your ESP. An email address that only lives in your newsletter tool isn’t doing anything for your CPM. It has to reach your ad server as an identified-user signal for the uplift to show up in your revenue.
Your data, on your site, under your control
There’s a second reason this matters beyond CPM. Data captured through a WordPress-native registration wall stays in your own site’s database. It isn’t routed through a third-party JavaScript embed, stored on someone else’s servers, or subject to someone else’s data-sharing terms. You own it the way you own your content.
That matters for CPM today. It matters more every time a browser update, a consent law, or a platform policy shifts the ground under identity data that was never yours to begin with.
The publishers pulling ahead on ad revenue right now aren’t waiting on Google’s next Privacy Sandbox move. They’re building the list themselves, one registration at a time, and getting paid 25-40% more for every reader on it.
