--- title: Newsletter & Paywall Targeting by Reader Depth description: "Newsletter signup targeting by reader depth: prompt the 3+ article readers most likely to say yes, suppress the leavers, and grow the pool that gets asked." url: https://www.artificialpoets.com/use-cases/depth-triggered-conversion/ site: Artificial Poets type: page date: 2026-08-09T19:46:31+00:00 modified: 2026-08-25T19:31:46+00:00 --- # Ask at the Right Article "I'm showing newsletter popups to readers who were leaving anyway — how do I ask the ones who are ready?" [See it on my numbers](/request-a-demo/) Horse & Rider · Ride TV · Equine Network · Equus Magazine · The Score · Equine Network Lockup ## You are asking at the door The problem - **The popup fires on arrival** — Most publishers trigger the newsletter ask the moment a reader lands. That is the one point in the visit where they have read nothing and owe you nothing. - **Timing is most of the result** — Popups shown after a few seconds convert at 2.4%. Shown instantly, 1.9%. Scroll-triggered asks on long reads beat time-only ones by 18 to 25%. - **Everyone else is interrupted** — A reader who was leaving anyway gets a form in the way. The ask costs you nothing on them and costs you trust on everyone else. ## How we ask at the right moment - **Fires on depth** Your prompt appears when a reader crosses a depth threshold you set. The one-page visitor never sees it. - **Only the ready readers** A reader on their third article has told you they want more. That is who gets the ask, and who converts. - **Your tools, your form** Works with Piano, Zephr or your ESP. The engine decides when; your existing stack does the rest. ## Ask readers to register when they have shown they want more. The mechanism A newsletter prompt on arrival interrupts a reader who has read nothing and owes you nothing. Most leave, and the ones who stay learned that your site opens with a form. The Artificial Poets Platform moves the ask. Your prompt, in your tool, fires when a reader crosses a depth threshold you set: a second article, a third, a fifth. By then the reader has told you they want more, and the conversion rate reflects it. The engine also grows the group it is asking. Sessions reaching three or more articles rose 91% on enabled titles, which is the pool every registration wall and paywall draws from.[1] It does not replace Piano, Zephr or your ESP. It decides when; your existing stack does everything else. **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 ### Does this replace Piano, Zephr, or our ESP? No. Your wall vendor and ESP keep the ask; the Platform supplies what they don't have — a depth state per reader, and a growing pool of readers who reach it. In Salem Reporter's 30-day head-to-head, a registration wall out-signed a newsletter form 16× (Leaky Paywall); that is an argument about where you ask. Depth state is the argument about when, and it feeds the instrument you already run. ### What depth threshold should we set? Start from where your own conversions already cluster rather than from our number. The pattern in the measured data is that the readers most likely to say yes are two states further in than the default arrival popup, and the baseline month exists so that threshold is chosen from your funnel, not ours. ### Does it tell a subscriber from a first-time arrival? It tracks reading-depth state per reader, so your rules can distinguish someone on their fourth article from someone who just landed. What the prompt then says, and whether a subscriber sees anything at all, stays in the tool you already run. ### Are these before/after dashboard numbers, or is there a control? The depth figures run against a comparison group of titles in the same network that changed nothing — where the 3+ pool fell 22% and the 5+ pool −17% over the same nine months. One enabled title ran +12.2%, then a four-week pause in serving during which the Platform did not serve; the metric fell to −2.7% and recovered to +6.9% after serving resumed. Conversion incrementality on your prompts is measured in your own stack, with a design agreed before enablement. ### "The model decided" won't survive my board — and is reader-level targeting a GDPR problem? The targeting rule is a sentence, not a score: ask at the third article, gate at the fifth, never prompt a reader the intent model reads as leaving. Your team sets the thresholds and can read them back. The state is behavioural, anonymous and first-party — no PII stored, GDPR/CCPA-compatible — closer to a meter rule than to propensity-to-subscribe modeling on personal data. ### Where does the depth data live? On your properties. The profile is anonymous and first-party, with no PII, no third-party cookies and nothing leaving your domain, and serving events land in your own analytics stack so the record is yours to query. ### What does integration take? Authorization, CMS access and infrastructure access, then a JavaScript tag carried out by our team. Your prompts, offers and rules stay where they are; what changes is when they fire. ## Related - [Equus Magazine Tripled the Sessions That Reach Five Articles](https://www.artificialpoets.com/customers/equus-magazine-deep-readers/) — Most publishers measure whether a reader gets to a second article. This is what happens after that: sessions reaching three articles nearly doubled, and sessions reaching five tripled. - [Build the Audience That Comes Back](https://www.artificialpoets.com/solutions/direct-audience/) — "My subscriber targets keep rising while my funnel shrinks — where does direct audience actually come from?" ## Unlock new revenue with our AI Artificial Poets Platform can help you with [Book a demo](/request-a-demo/) ## Questions this page answers ### What is depth-triggered conversion? It is firing your newsletter, registration or paywall prompt at a reading-depth threshold instead of on arrival or after a timer. The reader who has read three articles is a different prospect from the one who just landed. On the network we measure, only 6.2% of sessions reached a second article before enablement. ### How does depth targeting work with our existing prompts? Your prompts, rules and offers stay in the tools you already run. The Platform tracks each reader's depth state in real time and fires your prompt at the threshold you set, while growing the pool of readers who reach it: 3+ article sessions rose 91% and 5+ sessions 221% on enabled titles. ### How much does it cost? There is no public price list; pricing follows network size and formats. It does not replace your subscription stack, so nothing already paid for is displaced. The four-week baseline records your current prompt performance first, which is what any depth-triggered result gets compared against. ### Who is it for? Audience and consumer-revenue teams whose prompt interrupts everyone and converts almost nobody. If your popup fires on arrival, it is asking the roughly 94% of readers who were leaving anyway and burying the offer for the few who were not. ### What are the alternatives? Time-on-page and scroll-depth triggers approximate interest with proxies that a slow scroller and a distracted tab both satisfy. Exit-intent fires when the decision is already made. A better-designed popup asks the same wrong audience; changing the trigger changes who is asked. ### How do I get started? Pick the depth threshold and keep your existing prompt and offer. Authorization, CMS access and infrastructure access are the requirements, four weeks of measurement-only baseline record the current conversion behaviour, then enablement on a named day, with your funnel numbers staying in your own stack throughout.