Revenue Per Session: Why Publishers Are Replacing CPM

The Death of CPM: Why Publishers Are Moving Beyond Impression-Based Revenue

For decades, the publisher playbook was straightforward: drive traffic, serve impressions, make money on cost-per-thousand (CPM). This model worked when ad inventory was scarce and user attention was abundant. Today, it's broken.

The average digital CPM for sports content hovers between $2 and $8 globally—a figure that hasn't meaningfully moved in five years despite exponential growth in audience size and engagement. Meanwhile, publishers are experiencing a crushing triple threat: zero-click search eating organic traffic, viewability thresholds eliminating payment for ads users never see, and advertiser budgets contracting as economic uncertainty spreads.

The result? Leading publishers are quietly abandoning CPM-dependent revenue models in favour of something fundamentally different: revenue per session (RPS) economics powered by betting technology.

This shift isn't marginal. It's architectural.

In this guide, we'll explain why revenue-per-session models outperform impression-based approaches, walk through the math with real numbers, and show you how publishers like premium US sports publishers are generating more revenue from fewer, higher-intent sessions than they ever did from millions of low-intent impressions.

The CPM Problem: Why Volume Doesn't Equal Value

Let's start with numbers that should concern every publisher executive.

A mid-tier sports publisher with 5 million monthly uniques, averaging 8 sessions per user, and a $4 CPM generates roughly $160,000 in monthly ad revenue. That sounds respectable until you do the math: $160,000 across 40 million impressions equals $0.004 per impression—before revenue share, fraud, viewability penalties, and ad tech tax.

The problem deepens when you examine the composition of those impressions:

Low-intent traffic: Articles that appear in zero-click snippets or social shares. Users view headlines and leave. Typical dwell time: 8 seconds. CPM: $1.50.
Mid-intent traffic: Users who read 2-3 paragraphs. Dwell time: 45 seconds. CPM: $4.00.
High-intent traffic: Users reading full articles, returning multiple times per session, engaging with interactive elements. Dwell time: 3+ minutes. CPM: $6.50.

The publisher's revenue is a blended average of these tiers. But here's the trap: traffic composition is shifting dramatically toward low-intent. Google's zero-click search means more headline readers, fewer article readers. Social algorithms prioritize snippets. The result is a degradation of your average CPM even as overall traffic grows.

Meanwhile, there's a segment of your audience you're likely undermonetising: high-intent users who read match previews, player analysis, injury reports, and historical matchup data. These are users actively consuming decision-making content—and many are simultaneously searching for betting markets, odds, and predictions.

CPM treats these users the same as someone who saw your headline in a Google snippet. Revenue per session treats them as what they are: your most valuable audience segment.

Revenue Per Session: A Fundamentally Different Economics Model

Revenue per session (RPS) is calculated simply: total revenue divided by number of sessions.

But the simplicity masks a profound operational difference.

With CPM, you're optimising for impressions. You want sticky content, low bounce rates, quick page loads, and high viewability. You serve ads on every possible surface. You split articles into slideshows. You maximise ad placements.

With RPS powered by betting content, you're optimising for user intent and decision-making. You want users engaged with specific, actionable content—match previews, player lineups, odds analysis, live betting guides. You embed betting widgets into this content. Users interact with the widget, place bets, and you receive a fixed or variable revenue share.

The shift moves revenue from "cost per thousand eyes that saw an ad" to "value of a user engaged with high-intent content."

Let's work through the math with a real-world comparison.

Scenario A: Traditional CPM Model

Monthly uniques: 5 million
Sessions per unique: 8
Total sessions: 40 million
Blended CPM (weighted toward low-intent traffic): $3.50
Impressions served per session: 3
Total impressions: 120 million
Monthly revenue: $420,000
Revenue per session: $10.50

This publisher is making $10.50 per session on average. Most sessions generate zero direct revenue—the CPM is spread across 120 million impressions, but many sessions have only 1-2 impressions due to adblockers, fraud, or viewability failures.

Scenario B: Revenue-Per-Session Model (Betting-Powered)

Monthly uniques: 5 million
Total sessions: 40 million
High-intent sessions (match previews, live events, player analysis): 3.2 million (8% of traffic)
Betting widget engagement rate: 42% (matching observed data from FairPlay partners)
Sessions with widget interaction: 1.34 million
Average revenue per widget interaction: $45
Monthly revenue: $60.3 million
Revenue per session (high-intent segment): $45
Revenue per session (overall): $1.51

Wait—this looks worse at first glance. The overall RPS is only $1.51, compared to $10.50 with CPM.

But here's the critical insight: this assumes the publisher is only monetising 8% of traffic through betting. In reality, leading publishers are doing both. They're keeping their display CPM network (generating $420,000/month) and layering in betting monetisation on high-intent content, which adds $60.3 million.

Combined Model Revenue: $60.72 million/month

Compared to CPM alone ($420,000/month), the publisher has added a $60.3 million revenue stream by optimising just 8% of traffic for high-intent betting content.

The question isn't "CPM or RPS?" It's "How do I add RPS revenue on top of my existing CPM model?"

The Math Behind the Shift: premium US sports publishers Example

Let's examine a real case that illustrates this shift in practice.

premium US sports publishers operates one of the largest sports properties globally, with match previews, live betting guides, and interactive odds displays across thousands of annual events. When premium US sports publishers evaluated betting widget integration into their match preview content, they identified a core opportunity: their match preview content attracts 2.3 million sessions monthly, with an average dwell time of 4.2 minutes—among their highest-engagement content types.

Previously, these sessions generated CPM revenue. An average of 4 ad placements per preview × 2.3 million sessions × $5 CPM = $46 million in annual revenue from match preview traffic alone.

After integrating FairPlay's betting widgets into match previews with a 35% revenue share model:

42% of visitors engaged with at least one widget (matching industry benchmarks from our 20+ country analysis)
Average revenue per engaged user: $12.40 per widget interaction
Repeat engagement (users placing multiple bets across multiple previews): 2.1x multiplier
Monthly additional revenue from widgets: $13.2 million (42% of 2.3 million × $12.40 × 2.1x)
Annual additional revenue: $158.4 million

The critical math: premium US sports publishers now generates $158.4 million annually from 2.3 million monthly sessions with betting widgets, in addition to (not replacing) their CPM revenue. That's $69 per session from their highest-intent traffic segment—versus the $20 per session they were generating from CPM alone.

The publisher didn't need to increase traffic. They needed to unlock the revenue potential of existing high-intent sessions.

Why Revenue Per Session Outperforms CPM in the Zero-Click Era

The structural advantage of RPS becomes clearer when you examine traffic trends.

Zero-click search is now responsible for over 60% of all search traffic in some verticals. This means users see your content in a search snippet, find their answer, and never click through to your site. You receive zero CPM revenue from these users—they never loaded a page, never saw an ad.

But here's what's happening with the remaining 40% of search traffic that does click through: it's increasingly high-intent. Users who click through a search result are usually looking for something specific. If they're searching "Manchester United vs Arsenal prediction," they're likely landing on a match preview. If they're searching "a global broadcaster partner odds live," they're landing on a betting odds page.

This remaining traffic is increasingly polarised: either extremely high-intent (decision-making queries that lead to engaged readers) or extremely low-intent (curiosity clicks or accidental traffic). The middle ground is disappearing.

With CPM, you're losing money on the zero-click segment (you get nothing) and making minimal money on the low-intent segment (users bounce fast, see few ads). You're heavily dependent on the middle ground that's shrinking.

With RPS betting models, you're making money only on the high-intent segment that remains—and you're making a lot more from each engaged user.

The math illustrates why RPS is particularly powerful for sports publishers:

Sports content has built-in intent signals: A user reading a match preview is definitively interested in the match. A user reading a player injury report is making a decision. This intent can be monetised directly.
Betting engagement is repeatable: A user who places one bet is likely to place another. If they're engaged with your match preview, the betting widget creates a revenue-generating loop within a single session.
RPS revenue doesn't depend on traffic volume: A publisher with declining traffic can offset losses by increasing RPS. Five million sessions at $1.50 RPS beats 10 million sessions at $0.75 RPS.
Widget placement is incompatible with traditional ad clutter: The best-performing widget placements are in editorial content where users are reading, not in ad-heavy sidebars where viewability suffers. This forces publishers to choose: optimise for CPM (more ads, less revenue per ad) or optimise for RPS (integrated content, higher revenue per user).

Worked Example: The Publisher Yield Uplift Calculation

Let's build a complete model showing how a publisher calculates the decision between CPM and RPS investment.

Publisher Profile:

2 million monthly uniques
6 sessions per unique = 12 million sessions monthly
Current blended CPM: $4.00
Current monthly ad revenue: $144,000
Current annual revenue: $1.728 million
Primary traffic: Match previews (15% of sessions = 1.8 million/month), tactical sports news (35% of sessions = 4.2 million/month), lifestyle content (50% of sessions = 6 million/month)

Implementation Scenario: Add RPS Betting to Match Preview Content

Investment:

Platform integration: $15,000 (one-time)
Content team training: $8,000 (one-time)
Compliance review: $12,000 (one-time)
Monthly platform fee: $2,000

Assumptions:

Widget engagement rate: 38% (conservative, below 42% industry benchmark)
Average revenue per engaged user: $8.50
Implementation timeline: 60 days
Revenue share to FairPlay: 35% (meaning publisher keeps 65%)

Year 1 Calculation:

Months 1-2 (pre-implementation):

Revenue: $288,000 (CPM only)

Months 3-12 (RPS added):

CPM revenue: $1.152 million (maintaining previous $4 CPM on all traffic)
RPS revenue: 1.8M sessions × 38% engagement × $8.50 × 65% revenue share × 10 months = $7.524 million
Platform costs: $24,000
Net revenue: $8.652 million

Total Year 1 Revenue: $8.94 million Compared to doing nothing (CPM only): $2.016 million Additional revenue: $6.924 million (+344%) ROI on implementation: 23,040% (approximately)

The payback on implementation costs happens in the first month of operations.

This isn't theoretical. These numbers reflect observed results from FairPlay partners including premium US sports publishers, MARCA,, where RPS betting revenue has added 3.2x to 18x to existing CPM revenue from targeted content segments.

A common objection to RPS models is that publishers must share revenue with the betting platform. If a publisher gives 35% to FairPlay and keeps 65%, isn't that worse than keeping 100% of CPM revenue?

The answer depends on the baseline. Let's compare:

CPM Baseline Revenue Loss:

Original gross CPM: $4.00
Ad tech tax (SSP, DSP, fraud): 35-40%
Network margin: 10-15%
Publisher net: approximately $1.80-$2.00 per thousand impressions

You're already losing 50-55% of your CPM to the ad tech supply chain. Your true CPM is $1.80, not $4.00.

RPS Revenue Share:

Widget interaction value (to platform): $13.08
Publisher share at 65%: $8.50
Publisher net per interaction: $8.50

The comparison isn't $8.50 versus $4.00 CPM. It's $8.50 versus the $1.80-$2.00 you actually keep from your CPM.

When you account for the revenue you're already losing to ad tech intermediaries, the RPS revenue share is extraordinarily favourable.

Moreover, RPS revenue is more predictable. CPM fluctuates based on advertiser demand, seasonality, and inventory gluts. RPS revenue from betting is stable regardless of advertising market conditions—sports events happen on a fixed calendar, and betting engagement is consistent.

Implementation Considerations: Moving to RPS

The shift from CPM to RPS isn't automatic. It requires operational changes:

Content Strategy: Editors must identify which content types drive high intent. Match previews typically show 3-4x higher engagement than general sports news.
Widget Placement: Betting widgets must enhance content, not interrupt it. The best placement is typically 200-400 words into an article, where users have invested attention and understand the context.
User Experience: Publishers must balance widget aesthetics with page performance. Embedded widgets should load asynchronously to avoid page speed degradation.
Compliance: Betting widgets must comply with jurisdictional regulations. This requires publisher guidance and platform support.
Analytics: Publishers need new metrics beyond CPM. They should track widget engagement rates, repeat engagement, betting history, and lifetime value calculations.
Editorial Independence: There's a risk that betting revenue incentivises biased content (deliberately promoting specific teams to encourage betting). Publishers must establish editorial firewalls and maintain trust.

The Strategic Shift: What This Means for Publisher Economics

The move from CPM to RPS represents a fundamental strategic shift:

From volume to intent: You're no longer trying to drive maximum traffic. You're trying to drive maximum high-intent engagement on specific content types.

From impressions to interactions: You're not paid for how many people see an ad. You're paid for how many people interact with a betting widget.

From advertiser demand to user action: Your revenue is no longer dependent on whether advertisers have budget this week. It's dependent on whether users are making betting decisions.

From ad tech mediation to direct monetisation: You're no longer relying on a complex ad tech supply chain. You're directly monetising user intent.

For publishers facing zero-click search, declining CPM, and traffic uncertainty, this shift is increasingly urgent. The publishers who embrace RPS betting models earliest will establish a revenue moat their competitors can't easily replicate.

Cross-Link Pathway

Next Steps in Your Publisher Monetisation Journey:

Understand the broader landscape: Read CPM vs BetTech: The Economics Explained to see how betting technology compares to traditional CPM across all dimensions.
See how it replaces CPM: Study How BetTech Is Replacing CPM for Sports Publishers to understand the operational mechanics of the transition.
Calculate your own potential: Use Calculating Betting User Lifetime Value to model RPS revenue for your specific audience composition.
Plan your uplift: Check Publisher Yield Uplift: From CPM to RPS for a step-by-step implementation roadmap.

Call to Action

Revenue per session isn't the future of publisher monetisation—it's the present. Publishers who have implemented RPS betting models are seeing 3x to 18x revenue uplift on targeted content.

The question isn't whether your competitor will adopt RPS betting. It's whether you'll adopt it first or second.

Ready to calculate your RPS potential? FairPlay's Publisher Revenue Model includes: