© 2026 ContentWise. All rights reserved.
EBOOK
What Works, What Doesn’t, and When
Written by Renato Bonomini, VP Sales Engineering, ContentWise. Foreword by Paolo Cremonesi, Co-founder and CTO. With Gianluca Leucci, Paolo Romano and Matteo Fabiano.
Twenty-five years ago the hard problem in television was distribution. Today it is attention.
From the foreword by Paolo Cremonesi, Co-founder and CTO, ContentWise by Moviri
WHAT'S INSIDE
Seven parts, one per stage of the subscriber lifecycle, plus the foundations that set the language and a playbook that turns the rest into a build order. Every chapter opens with the question a product leader actually asks, and answers it in the first paragraph.
| Part | Stage | The question it answers | The KPI it moves |
|---|---|---|---|
| 01 | Acquisition | How do we convert a non-subscriber? | Cost per acquisition |
| 02 | Onboarding | Does the new user reach value before they doubt? | Time to first value |
| 03 | Conversion | Does the surface turn interest into action? | Conversion to play |
| 04 | Engagement | Do they keep finding things worth watching? | Streaming minutes, take-rate |
| 05 | Satisfaction | Did the experience build trust, or only minutes? | Return frequency, NPS |
| 06 | Monetization | Can we grow value per user without breaking trust? | ARPU, upsell take-rate |
| 07 | Retention | Do we keep the subscribers the product can hold? | Churn, LTV |
Before the seven parts, the foundations: what personalization actually is as distinct from recommendations, why metadata is what makes any of it work, how to place your own service on the maturity curve, and the sequencing that decides what to build first. After them, the implementation playbook, which turns 99 use cases into an order of operations.
ANATOMY OF A USE CASE CARD
Most lists of personalization features name the feature and stop. Each of the ninety-nine entries tells you where it fits in the subscriber lifecycle, what business case funds it, which KPI it moves, the conditions under which it fails, and what has to exist before you build it.
ALL 99 USE CASES
Nobody had catalogued them, so we did. Once you see all ninety-nine in one place the useful question is not how many you run. It is whether the ones you run map to the correct lifecycle stage, and whether they move your KPIs.
The viewer asks. Lean forward, goal-directed.
The system proposes. Lean backward, and where most personalization earns its keep.
Understanding and believing the system, rather than finding content.
Reaching the viewer when they are not in the app at all.
THE KEY ARGUMENT
The systems that lift retention and LTV are the ones that align personalization to where the user is in their journey. Aggression in the algorithm is not the variable. A new user, a trialist, a power viewer, and a subscriber halfway out the door need different things, and the same recommendation row serves none of them well. Every part of this book serves that single thesis.That is the right instinct pointed at the wrong target.
Too many options, not enough guidance, the same friction every night. A good system answers it before the user feels the fatigue. That is the job. This book is about doing it at every stage, not just on the home page.
WHO THIS IS FOR
This is the reference I wished existed. Every personalization use case that matters to a streaming operator, organized by where it pays off in the subscriber lifecycle, with real benchmarks and the counter-narratives most vendors will not print.
I wrote it for the leader who already runs personalization and owns the engagement, conversion and retention numbers. It assumes you have a recommender in production, an editorial strategy you can defend, and retention targets someone is measuring you against.
Two choices shaped it. Running the catalogue along the subscriber journey rather than down a feature list forces every use case to answer a question you actually have: who is this for, at what moment, and what number should move. And it prints the use cases that do not work, the ones that lift a click and move nothing that matters, along with the conditions under which the good ones fail.
EBOOK FAQ
ContentWise catalogued 99, grouped by what the viewer is doing: discovery, search, trust and explanation, and off-platform. Each one is placed at the subscriber lifecycle stage where it pays, with the KPI it moves, the effort it takes, and the build phase it belongs to.
Seven: acquisition, onboarding, conversion, engagement, satisfaction, monetization, and retention. Each stage has its own KPI, and a use case that works in engagement can be the wrong instrument in onboarding.
Recommendation is one use case: ranking titles inside a single carousel against a single objective. Personalization adapts the whole experience, page plus search plus collections, to the viewer's journey, device, and context, which means deciding which rails exist and in what order before deciding what goes in them.
Neither, exclusively. Every rail carries a dial between hand-picked and machine-ranked: editors define the blocks and priorities, the algorithm fills and ranks them per profile, and the blend covers both failure modes, an algorithm's popularity bias and editorial's inability to scale to thousands of micro-segments.
Because algorithms only know what the metadata tells them, and bad metadata is the most common reason personalization efforts fail. The book gives a four-metric self-diagnostic you can run this quarter: coverage, distribution, number of values per item, and consistency.
The experience. Most content is ubiquitous and operator catalogs are largely undifferentiated, so the durable differentiator is the experience aligned to where the viewer is in the journey, not the one running the loudest algorithm.
Maturity runs on two axes: how much you know about the viewer, and how much of the page you act on. The sequencing rule that wins is content first, community second, full UX personalization last, because content-based and statistics rails work on day one with zero behavioral history.
Click-through and take-rate are local, short-term wins that do not guarantee retention, satisfaction, or monetization. The book names the use cases where that gap appears and the conditions under which the reliable ones fail.
We are at IBC in Amsterdam from 11 to 14 September, Hall 5, Stand 5.G50.
[Or email info@contentwise.com]
© 2026 ContentWise. All rights reserved.