Measured on live deployments
How We Measure
"How do I know any of this is real — and how do I prove it to my board?"
The measurement stack
Five design layers between a dashboard delta and a number we publish, plus an observed off-period. This is how our own published numbers were made; every line is one your analyst can check.
- Baseline
- four weeks, collection and indexing only, zero serving
- Enablement
- a named day, on named titles; the series breaks cleanly
- Comparison group
- the entire eligible set of unchanged titles
- Window sweep
- the result holds when the start and end dates move
- Segment cut
- every device and channel, casualties printed
- Off-period (observed)
- serving paused four weeks, zero renders; the metric returned to baseline
The evidence, at its honest tier
- Multi-page sessions
- +46% on enabled titles (10.3% → 15.1%) vs −16% on comparison titles (12.0% → 10.1%) over nine months, on a multi-title publisher network we measure continuously
- Launch vs run rate, side by side
- +19.1% first quarter → +4.0% steady state on the largest title; +12.2% → +6.9% on the second
- The off-period is published
- across a four-week pause in serving — zero renders — the second title read +12.2% → −2.7% → +6.9%. The metric returned to baseline and recovered on resume
- The segment cut is published with its casualty
- mobile +48% vs −23% comparison; direct fell on enabled titles too (−19%, vs −35% on comparison) — and we print it
- No revenue figures and no traffic claims
- sessions and users were flat to slightly down. Depth is the measured result; revenue is your own RPM arithmetic
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.
Ranked
#1
for this
reader
today
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.
Anonymous
Programmatic
Ad tech
Retail media
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.
Next read
The winter feeding mistake that costs you condition
Next read
Six saddle-fit checks before you blame the horse
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.
multi-page sessions
FAQ
See it running on your own numbers
We'll walk you through what the Platform does on titles like yours.