--- title: "Media Network Audience Platform: One Audience Across a Multi-Brand Portfolio" description: Fewer than 0.2% of readers ever touch a second title on the network we measure. A media network audience platform for the portfolio you already own. url: https://www.artificialpoets.com/solutions/media-networks/ site: Artificial Poets type: page date: 2026-08-09T06:31:06+00:00 modified: 2026-08-25T19:31:57+00:00 --- # One Audience. Every Property. "We own a dozen properties — why does our audience behave like it belongs to strangers?" [See it on my numbers](/request-a-demo/) · [Read the rollout case study](/customers/equine-network-rollout/) Horse & Rider · Ride TV · Equine Network · Equus Magazine · The Score · Equine Network Lockup ## A portfolio that behaves like strangers The problem - **Under 0.2% cross a title line** — On the multi-title network we measure, fewer than two readers in a thousand ever touch a second brand you own. - **Each brand recirculates alone** — Internal traffic is the largest controllable lever a publisher has. Today it is worked one site at a time, never across the group. - **Nothing connects them** — Separate CMSs, separate analytics, separate reader ids. The audience is one set of people; the data says it is a dozen. ## How we make a portfolio behave like one audience - **One reader, every title** An anonymous interest profile follows the reader across every brand you own. No login, no shared CMS, no data migration. - **Cross-title by default** The next read can come from any title in the group, ranked on meaning. Your portfolio becomes the referral network it always was. - **Your data stays yours** Profiles are behavioural fingerprints, not identities. Nothing personal is stored and everything leaves with you. ## Your portfolio is a referral network. Most have never switched it on. One audience A media group with a dozen titles has one audience and a dozen profiles of it. Fewer than 0.2% of readers ever touch a second brand, because nothing on any page knows what they read on another. The Artificial Poets Platform builds one anonymous interest profile per reader and carries it across every title you own. No login, no shared CMS, no data migration: it reads behaviour on the page and matches it against the meaning of every article in the group. The next read can then come from any title, ranked on what this reader is actually interested in, served inside each brand's own templates so the brands stay distinct. Profiles are behavioural fingerprints, not identities, and everything leaves with you if you go. On enabled titles, multi-page sessions rose 46% over nine months.[1] The rollout itself, some titles enabled and their sisters unchanged, is what made that number checkable. **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 ### Our titles share a CMS but not a data layer — is this a data-unification project? No. The Platform does not assemble a graph from your existing data layer — it builds its own from on-site behaviour, per reader, from day one. Each property gets a JavaScript integration; there is no identity-graph procurement or CDP migration ahead of value, and titles come online one at a time. ### How does one profile work across separate domains without third-party cookies? Not with third-party cookies; the Platform does not use them. The fingerprint is anonymous and built from behaviour on properties you own, first-party by construction. And the honest tier holds here: the measured results are within-title depth; cross-title serving is the same engine on a new surface, and we say so first. ### Won't cross-title serving just reshuffle sessions we'd have gotten anyway — and blur our brands? There is almost nothing to reshuffle: cross-title reading on the network we measure is under 0.2% of readers. The measured lift is depth within each enabled title — +46% while unchanged sisters fell 16% — not readers moved between titles. Recommendations render in each host title's own templates, and each title keeps editorial control over what appears on its pages. ### Does a reader's consent on one title cover the others? Treat consent as per property: each title keeps the framework it already operates, and the Platform sits behind it, anonymous and first-party on every site. Scope across your legal entities is a question for your DPO, and the baseline month exists so that review happens before serving. ### Who gets credit when serving moves a reader between brand P&Ls? Each title's record stays its own: recommendations render in the host title's templates and serving events land in that title's analytics. The measured lift is depth within each enabled title, so the number a brand GM answers for is produced on that GM's own pages. ### Do the smaller titles benefit, or does the graph feed the flagships? Each enabled title's depth is measured on its own pages, and both published titles moved: +63% on one, +29% on the other, while unchanged sisters fell. The engine's first job on any title is that title's next read, not traffic donation to the flagship. ### Where does the audience data live, and who owns the graph? On your properties, and you. The fingerprint is anonymous — no PII stored, GDPR/CCPA-compatible. The graph is built from your first-party behaviour, scoped to your portfolio, and never pooled with other customers. Publisher control of audience data is the position the whole market is converging on; it is ours from the start. ## Related - [How Equine Network Grew Multi-Page Sessions 46%](https://www.artificialpoets.com/customers/equine-network-rollout/) — Equine Network enabled the Artificial Poets Platform on two titles and left the rest unchanged. Over nine months the enabled titles grew multi-page sessions 46%; across the comparison titles the same measure fell 16%. - [Get Them to the Second Episode](https://www.artificialpoets.com/use-cases/video-recommendations/) — "Subscribers churn before a second episode — how do I get them watching in the first session?" ## Unlock new revenue with our AI Artificial Poets Platform can help you with [Book a demo](/request-a-demo/) ## Questions this page answers ### Why does a portfolio audience not cross between titles? Because nothing connects the titles: on the multi-title network we measure, fewer than 0.2% of readers ever touch a second title. Each brand acquires and loses its audience alone. Sister titles are the only referral network a portfolio fully controls, and unconnected, it moves almost nobody. ### How does the Artificial Poets Platform connect a portfolio? One anonymous interest fingerprint per reader, built from on-site behavior, carries the reader's interests across the titles you own and orchestrates the next read in each title's own templates. There is no CDP migration or identity-graph procurement ahead of value: each property is a JavaScript integration, and titles come online one at a time. ### How much does a portfolio deployment cost? Pricing follows the portfolio: how many titles, which formats, what order. Titles enable one at a time, so cost tracks the rollout rather than arriving up front, and the unchanged titles double as the comparison group. The four-week baseline and agreed metrics precede serving on every title. ### Who is this for? Operators of multi-brand portfolios: enthusiast networks, roll-ups, media groups whose audience data lives in silos per title. The same connected profile that lifts depth is what advertisers buy against and what acquirers now price: in media M&A, owned audience and first-party data set the multiple. ### What are the alternatives for unifying a portfolio audience? A data-unification project builds the warehouse first and the value later, if ever. Joint ad marketplaces pool audiences for advertisers; this one is built for readers. Building it the way the biggest portfolios did requires the engineering organization they have. The measured contrast: +46% on enabled titles, −16% on unchanged sisters. ### How do I get started across a portfolio? Pick the first titles; the rest stay unchanged and become the comparison group, which is the evidence structure your analytics team will ask for. Four weeks of baseline, enablement on a named day, then the next titles in sequence. Authorization, CMS access, and infrastructure access per title, with integration run by our team.