A publisher with 40,000 pages is running one monetisation strategy. One set of floor prices. One ad density. One SSP configuration. One format mix. The strategy is either right for most of those pages or wrong for most of those pages. It is almost never both.
This is not a tuning problem. It is a modelling problem. The publisher has treated a collection of different products as though they were one, because they happen to share a domain.
Understanding when that assumption holds and when it breaks is one of the more consequential decisions an established publisher makes. Not because uniform strategies are inherently wrong, but because the circumstances in which they are right are narrower than most publishers assume.
• A domain is an address, not a product. The product is the impression, and impressions differ enormously across a site.
• Four dimensions determine whether pages deserve different treatment: user intent, session position, content format, and user state.
• The cost of treating them uniformly is not just suboptimal revenue. It is that the highest-value inventory effectively subsidises the rest.
• Segmentation has diminishing returns. Most established publishers can manage four to six page archetypes, not forty.
• Once segmentation is the diagnosis, the partner question becomes whether the current demand stack can serve more than one inventory profile.
The default is uniform for good reasons. Most ad technology is designed to be deployed sitewide. A Google Ad Manager tag fires on every page. SSP integrations apply globally. Floor prices are set at the account level and cascade down unless someone intervenes. Ad density is often defined by a template, and templates are shared across content types.
Uniform treatment is also easier to manage. One set of numbers to monitor. One explanation when something goes wrong. One report the sales team can read without a glossary. Publishers who have tried segmentation and abandoned it usually did so for operational reasons, not strategic ones.
The problem is that uniform treatment implicitly assumes the site is one product. On a small site, that assumption is close enough to true. On an established site, it usually is not.
The differences between page types on the same site are not cosmetic. They change the value of the impression, the appropriate ad density, and the kind of demand that will respond.
User intent. A reader on a buying guide is in a materially different state from a reader on a breaking news article. One is researching a purchase, the other is consuming information. Advertisers pay for the first and tolerate the second. In practice, this means commercial-intent pages often command significantly higher CPMs than editorial pages in the same vertical, but publishers who run the same floor prices across both are leaving that difference uncaptured.
Session position. The first pageview of a session is a different product from the fifth. A reader who has arrived from search, found what they needed, and moved on is different from a reader who has navigated four pages deep into the site. Return visitors are different again. News Corp has reported that direct traffic is ten times more valuable to advertisers than social traffic and five times more valuable than search. That gap is not just about traffic source. It is about what direct visitors signal: familiarity with the brand, higher trust, and greater likelihood of being in a session that continues.
Playwire's ecosystem analysis reinforces the point. Across thousands of publisher sites, impressions per session (r=0.60) and impressions per pageview (r=0.57) were the two strongest predictors of revenue performance, outperforming fill rate, viewability, CPM, and session duration. The strongest lever is not what an individual ad earns. It is how many ad opportunities a session produces, which is fundamentally about which pages a reader visits and in what order.
Content format. A 3,000-word analysis supports a different ad density than a 300-word news brief. A category archive behaves differently from an article. A tool or calculator page has different session dynamics than either. Ad density that is appropriate on long-form editorial may be excessive on short news, and insufficient on evergreen resource pages where readers scroll further and stay longer.
The Lumen Research study with Mail Metro Media offers one data point on this. Reducing a simulated page from 15 ads to five lifted the share of readers who viewed an ad from 53% to 78%, with 4.2x higher spontaneous recall and an 8% lift in purchase intent. Fifteen ads was clearly too many. But five ads might be too few on a page with three times the dwell time, and considerably too many on a page a reader glances at for fifteen seconds.
User state. Anonymous visitors, authenticated readers, email subscribers, and paying subscribers are four different audiences. The Reuters Institute's 2025 Digital News Report found that 79% of news publishers now rate first-party data strategy as a top three priority. That priority reflects a real valuation difference. Publishers who have built authenticated audiences hold inventory that commands a premium in the post-cookie market. Serving that inventory through the same floor prices and demand stack as anonymous traffic undercuts the asset.
Consider a mid-sized publisher with four clearly distinct page categories: news articles, evergreen how-to guides, category archive pages, and newsletter landing pages.
The news articles are short, updated frequently, and mostly read by first-time or low-frequency visitors arriving from search and social. Session time is brief. Dwell time is brief. Many readers never scroll past the fold.
The how-to guides are long, evergreen, and mostly found by search. Readers arrive with a specific task in mind and stay longer. They scroll. They click related guides. They return.
The category archives are navigation, not content. They serve readers who are exploring a topic. Their value is in the session they initiate, not the time spent on the page itself.
The newsletter landing pages convert anonymous traffic into authenticated traffic. Their advertising value is low, because the reader is there to complete a specific action. Their strategic value is high, because they generate the authenticated audience that improves monetisation everywhere else.
A uniform strategy treats all four identically. Every page gets the same density, the same formats, the same floors, and the same demand stack. The how-to guides end up under-monetised relative to their dwell time and reader quality. The news articles end up over-monetised relative to their attention economy, which damages the reader relationship and suppresses viewability. The category pages contribute negligible value despite anchoring the sessions that produce the site's most valuable impressions. The newsletter landing pages compete with advertising for the reader's attention at exactly the moment the publisher should not be selling it.
None of these pages is being badly managed in isolation. The failure is in treating them as interchangeable.
Not every site needs segmentation. Uniform monetisation remains correct when three conditions hold.
First, page types are genuinely similar in intent, format, and reader state. A site that publishes one kind of content to one kind of audience can often run one strategy without loss.
Second, the operational cost of segmentation is not worth the return. Managing four or five archetypes requires additional reporting, additional floor logic, and additional attention. On smaller sites, the effort often exceeds the gain.
Third, the site's reporting can actually support it. If you cannot see performance by page type, page depth, or session position, you cannot manage segmentation. Many publishers attempt it and fail because the data does not support the decision.
When these conditions hold, uniform treatment is efficient. When any of them breaks, uniform treatment becomes a modelling error that quietly suppresses revenue.
It is tempting to respond to this argument by segmenting everything. That approach fails for predictable reasons.
Publishers who try to manage forty page types end up with forty sets of stale assumptions. Floor prices are set and forgotten. Reporting becomes unreadable. The sales team cannot explain the site's inventory to buyers. The operational overhead consumes the analyst time that would have produced the gains.
The workable target for most established publishers is four to six archetypes. These should map to the site's actual differentiators, not to a theoretical taxonomy. Useful archetype groupings tend to be:
• High-intent commercial pages (buying guides, product reviews, comparison content)
• Editorial content (news, features, analysis)
• Evergreen or reference content (how-to guides, tutorials, resource pages)
• Utility and navigation pages (category archives, tag pages, search results)
• Acquisition pages (newsletter signup, subscription, account creation)
• Authenticated content (subscriber-only or logged-in experiences)
Not every site needs all six. Most sites have two or three that clearly matter and two or three that can be grouped together. The exercise is less about the taxonomy and more about the discipline of asking, for each archetype, whether the current setup reflects the value of the inventory being served.
Three things typically change once a publisher segments its inventory by archetype.
Floor prices differentiate. Commercial-intent pages can justify materially higher floors than editorial. Category pages may benefit from lower floors that maintain high fill rates for session-initiating inventory. Newsletter landing pages may benefit from no advertising at all.
Ad density calibrates to dwell time and scroll depth rather than to a shared template. Long-form content supports more placements than short news. Utility pages support fewer than either. Density becomes a decision about each archetype rather than a sitewide default.
Format mix reflects what each page type actually produces. Video performs differently on evergreen content than on news. Native formats fit editorial contexts better than they fit commercial-intent pages. Sticky units behave differently on mobile than desktop. Segmenting by archetype makes format decisions concrete rather than theoretical.
The result is not dramatically more complexity. It is a smaller number of decisions, each made with better information, replacing a single decision that was being applied to situations where it did not fit.
Once a publisher accepts that its inventory is not uniform, a different question emerges. Can the current demand stack serve more than one inventory profile well?
Many ad networks are built around a single inventory profile. They optimise for a particular content type, a particular geographic mix, or a particular format. On a site with multiple archetypes, these networks typically perform well on some pages and poorly on others. The publisher then faces a choice: accept the mismatch, add partners to cover the gaps, or find a partner whose demand is diversified enough to serve the whole site.
This is where the diagnosis becomes actionable. If segmentation reveals that 20% of the site's pages are producing 60% of the revenue (a common pattern once the analysis is run), the question is not how to make the other 80% earn more. It is whether those high-value pages are getting access to the demand that their actual quality justifies, or whether they are being monetised through a stack that was built for the site's average.
A second source of demand, tested specifically against the highest-value archetype, is often the fastest way to find out whether the ceiling on those pages is the market or the current setup.
Most publishers who run this analysis find that the answer is a mix: some segments improve with tuning, others point to a genuine demand gap that the current stack cannot close. Adstork works with established publishers whose inventory has more than one profile, and who are looking for a second demand source to test against their highest-value segments rather than a replacement for what already works. You can request a segment-level review here if you want a second opinion on which archetypes are being under-served by the current setup.
The uniform default is not a mistake in itself. It is a reasonable simplification that works well under conditions most publishers outgrow without noticing.
The question is not whether to segment. It is whether the pages on your site are still similar enough that treating them identically produces the right outcome. For most established publishers, the honest answer is that some pages have been subsidising others for years, and the pattern has been invisible because the reporting was never built to show it.
The diagnostic is simple. Pull performance by page type, session position, and user state. If the numbers cluster tightly, uniform treatment is fine. If they spread widely, the strategy is doing something that the site's inventory did not ask for.
Growth makes this problem worse over time, not better. Every new content type, every new geography, every new format adds a different inventory profile that a uniform strategy will not distinguish. Recognising when the uniform assumption stopped fitting is one of the more consequential decisions a growing publisher makes.
How do I know whether my site actually needs segmentation? Run a segment-level performance report grouped by page type, session position, and user state. If the spread in eCPM, fill rate, and revenue per session is narrow across those dimensions, uniform treatment is fine. If the spread is wide, the site has multiple inventory profiles being served by one strategy, and the highest-value segments are probably being under-monetised.
What is a reasonable number of page archetypes to manage? Four to six for most established publishers. Fewer than four and the archetypes probably are not capturing real differences. More than six and the operational overhead starts to outweigh the gains. The right number is the smallest set that separates pages with genuinely different intent, format, or reader state from each other.
Should I change ad partners before or after segmenting my inventory? After. Segmentation is a diagnostic. It tells you which pages are under-served and why. Without that diagnosis, evaluating a new partner is guessing. Once segmentation shows a specific demand gap, testing a second source against that specific segment gives you a clean comparison. Testing without the diagnosis usually produces a switch that fixes one segment and breaks another.
Leave a Comment