Ritu Madan
+4
Jul 20, 2026
visibility 358
star star star star star
(0 votes)

Finding Thomas Part 5 - The Closed Loop

Five weeks. Five layers. One Thomas.

If you've followed this series from the start — thank you. If you're just landing here, the short version: Thomas is the returning visitor who reads everything, opens every email, converts on nothing, and one day quietly stops coming back. No warning. No signal. Just gone.

Over the last four posts we traced exactly how that happens — and how to stop it. The CMS watching Thomas's behavior as it unfolds. ODP turning that behavior into a persistent, scorable profile. Personalization making him feel seen for the first time. Opal scaling that recognition to every Thomas in your audience without a human bottleneck.

Part 5 is the final part where all four connect.

Not as adjacent tools. Not as a martech stack. As a single, continuous loop — one that finds Thomas while he's still Drifting, responds before he reaches At Risk, and gets smarter with every intervention it makes.

It also ends where the whole series began. With Thomas. And with the question worth asking honestly of any Optimizely implementation that has been live for more than a year:

Is your platform pointed at finding Thomas — or is it still primarily pointed at bringing new visitors through the door?

Read the full story here.

Jul 20, 2026

Comments

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |