Ritu Madan
OMVPOpal Administrator CertificationPaaS CMS Administrator Certification +4
May 28, 2026
visibility 632
star star star star star
(0 votes)

Finding Thomas Part 1 - The Observation Post

Meet Thomas

Thomas is the returning visitor who has been to your site forty times but has never filled out a form. He opens every newsletter but rarely clicks through. He reads your long-form content to the end while your analytics records him as just another session. He has a deep, genuine interest in the topics you cover — and an equally deep invisibility in the metrics your team reviews every week.

He does not bounce. He does not unsubscribe with a parting comment. He does not leave a one-star review. He just quietly, incrementally, recalibrates whether your experience is worth his time. And when he decides it is not — when the accumulated weight of feeling unseen finally tips the balance — he stops coming. Without a word. Without a signal.

We call this a recognition failure. And it's the most expensive problem in digital experiences that almost nobody is actively measuring.

About This Series

Finding Thomas is a five-part series about understanding and solving this problem using the Optimizely platform. Across these posts, we follow Thomas through the full digital experience layer — what your CMS can reveal about him, what ODP can connect across his behavioral history, how Personalization can respond in ways that make him feel known, and how Opal helps teams move from insight to action at scale.

Each post covers one layer of the stack. Together they trace a complete, closed-loop recognition system — one that finds Thomas before he finishes leaving, and makes him feel, for the first time, like someone noticed he was there.

In Part 1 of our Finding Thomas series, we trace where this starts — and why the CMS most teams treat purely as a publishing tool is actually the first place Thomas's story can be caught before it ends.

Read the full story here.

 

May 28, 2026

Comments

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026