---
title: "Publisher Ad Inventory: Turn Session Depth Into Sellable Impressions"
description: "Each article the Platform serves renders a fresh set of ad slots inside your existing GAM setup — refresh and viewability within your policy. Measured: +46% multi-page sessions on enabled titles vs −16% on comparisons."
url: https://preview.artificialpoets.com/use-cases/ad-inventory/
site: Artificial Poets
type: page
date: 2026-08-09T19:46:31+00:00
modified: 2026-08-18T02:10:14+00:00
---
# New Impressions on Inventory You Already Own

**Measured on live deployments**

"If sessions get deeper, how does that become sellable impressions in my existing ad stack?" Mechanically. Every article the Platform serves is a full article page rendered inside your CMS and your ad stack, carrying its own slots: a session extended to a third article monetises three pages instead of one, on the inventory, floors and demand you already own.

[See it on my numbers](/request-a-demo/)

Horse & Rider · Ride TV · Equine Network · Equus Magazine · The Score · Equine Network Lockup

## Where the impressions come from

One session on a timeline: article one shows its slots, and each served article renders fresh ones. Those impressions did not exist before the session got deeper. Served articles use your existing ad units, so there are no new placements to sell and no changes to your direct or programmatic setup.

- **Article 1 · landing** — The page the reader arrived on, rendering your ad slots.
- **Served article 2** — A full article page, chosen for this reader — fresh slots.
- **Served article 3** — The session continues, and so does the inventory — fresh slots.

## Inside your GAM setup, not around it

- **The Platform integrates with Google Ad Manager or equivalent** — served articles render your existing ad units
- **Refresh** — on served articles runs within the policy you set — frequency, triggers and eligibility stay your call
- **Viewability** — rules are unchanged: slots load as the reader reaches them, on pages the reader chose to continue into
- **Your floors, your direct deals, your demand partners** — nothing is auctioned outside your stack

## The measured base

We publish no revenue claims — the revenue arithmetic runs on your RPM. The Session RPM Calculator runs it for you against the published lift range.

- **Multi-page sessions** — +46% on enabled titles (10.3% → 15.1%) vs −16% on comparison titles (12.0% → 10.1%), over nine months
- **Mobile — where most impressions are served** — moved +48% against a −23% comparison decline
- **Largest single-title result** — +19.1% first quarter → +4.0% steady state; both published, plan on the second
- **Continuation past the fourth served article runs 70–82%** — readers keep choosing the next page, which is what keeps the impressions viewable

The economics behind those added impressions: [You Can't Get the Traffic Back. You Can Get the Session Back.](/resources/traffic-back/)

**Introducing**

## Artificial Poets Platform

One engine behind every solution on this site. It learns your archive and your readers, then acts inside your CMS, your templates and your ad stack.

- It learns your archive: **Every story you have published, current again** — The engine understands each piece by what it is about, not when it ran or where it was filed. A feature from 2019 competes for the next slot on merit with one from this morning.
- It reads the visit: **What a reader wants, without asking** — Interest builds from what someone actually does in the session. No login, no third-party cookies, nothing leaving your domain. Useful on the second pageview, not the tenth visit.
- It chooses: **The right next read, not the popular one** — Someone comparing products and someone following a running story want different things. A most-read list gives both the same five links and serves neither.
- It serves: **There before the reader leaves** — The feed, the recommendations, the search answer and the signup ask all run on the same engine, in your templates and your ad stack. Any slot that arrives with them is yours to sell.
- It proves: **A lift you can defend, or we say so** — Every deployment runs beside titles that did not get it, plus a serving pause. That is how a result becomes a number you can take to a board instead of a vendor claim.

## FAQ

### Will buyers treat this inventory differently?

The slots are your standard units on standard article pages, in your own GAM. There is no separate inventory class, no made-for-advertising pattern — a served article is your journalism with your templates.

### Could engineered depth read as made-for-advertising?

MFA classifiers look for forced pagination and impressions a reader never chose. The behaviour here is the opposite and it is measured: continuation past the fourth served article runs 70 to 82%, with roughly 19 seconds of reading each. Full article pages, your templates, your density policy. Forced pageviews do not produce that curve.

### Does refresh on served articles risk viewability scores?

Refresh runs inside your policy, and slots load only as the reader reaches them. The behavioural evidence — 70–82% continuation past the fourth served article, around 19 seconds of attention per served article — is a reader who is present, not a tab left open.

### What do we have to re-declare to demand partners?

Nothing new. Served articles render your existing ad units inside your existing setup, at your floors, under the refresh and viewability policy you already declared. No new placements, no new formats, and no third-party demand introduced.

### How much more inventory should I model?

Take the published pages-per-session range (+4% steady state to +19% launch quarter) and multiply by your own session volume and RPM — the calculator does exactly this arithmetic on your numbers.

### Does the tag slow the pages the ads sit on?

On the measured deployments mobile page experience improved over the same window; we claim that as not harmed rather than as caused. Serving happens below the content being read, as the reader scrolls, and the baseline month exists so your own vitals data can arbitrate.

### Does this introduce another party into our stack?

No. Nothing is auctioned outside your stack and no third-party demand is added. The engine decides which of your articles loads next; every impression that results is sold by you, in your own setup.

## Related

- [Session RPM Calculator](https://preview.artificialpoets.com/resources/session-rpm-calculator/) — What a measured session-depth lift is worth on your own inventory, from the +4% steady state to the +19% launch quarter.
- [Defend the Ad Line](https://preview.artificialpoets.com/solutions/ad-revenue/) — "Impressions are down and CPMs are soft — how do I defend ad revenue without more traffic?"
- [Mobile Multi-Page Sessions Rose 48%. The Comparison Titles Fell 23%.](https://preview.artificialpoets.com/customers/equine-network-segments/) — Mobile readers are the hardest to keep. Six of seven segments improved. The one that didn't is printed.
- [The Second Pageview Is the Last Metric You Still Control](https://preview.artificialpoets.com/blog/second-pageview-metric/) — Session depth is the share of your sessions that reach more than one page — and in 2026 it is the only major publisher metric whose fate is still decided on your own site. You cannot make search send the readers it used to send. You cannot reprice a programmatic market that is shedding volume. What you can decide is what happens in the thirty seconds after a reader lands.

## See how this works on your titles

Thirty minutes on your analytics. We tell you what share of your sessions stop at the first page, and what this would realistically move first for a setup like yours. You leave with the annotated read. No deck.

[See it on my numbers](/request-a-demo/)

How these numbers are made: [the measurement method](/solutions/measurement/). Figures from a multi-title publisher network measured continuously, August 2025 to May 2026. Last updated August 15, 2026.

## Questions this page answers

### How does session depth create new ad inventory?

Every article the Platform serves is a full article page rendered inside your CMS and your ad stack, carrying its own slots. A session that stops at one page monetises one page; a session extended to a third article monetises three. On the network we measure, multi-page sessions rose 46% while comparison titles fell 16%.

### How does it work inside our ad stack?

Served articles render your existing ad units, so there are no new placements to sell and no new formats to spec. Refresh policy, viewability and floors stay inside the GAM setup you already run, nothing is auctioned outside your stack, and no third-party demand is introduced.

### How much does it cost, and what is the revenue math?

There is no public price list, and we publish no revenue figures because we hold none of your revenue data. What we publish is the measured depth change; the Session RPM Calculator turns it into your own arithmetic against the measured range, from the 4% steady state to the 19% launch quarter.

### Who is it for?

Revenue and ad ops teams watching impressions fall while CPMs stay soft. If your traffic is flat or declining and your fill is already optimised, depth is the remaining lever that adds impressions to sessions you have already paid to acquire.

### What are the alternatives?

Raising ad density trades reader attrition for short-term impressions. Buying traffic raises cost faster than revenue. Exit-monetising widgets pay for the slot but send the reader away. Depth adds article pages inside your own stack, and the behaviour is voluntary: continuation past the fourth served article runs 70 to 82%.

### How do I get started?

Nothing in your ad stack changes to begin. Authorization, CMS access and infrastructure access are the requirements, four weeks of measurement-only baseline record your current session depth and impressions per session, then enablement on a named day. Eight weeks to a measurable effect.