Finding Thomas Part 2 - The Recognition Engine

Remember Thomas?

In digital landscape, Thomas is the returning visitor who reads everything, opens every email, converts on nothing. In standard reporting, he is invisible — absorbed into aggregate metrics that look healthy, precisely because he keeps showing up.

In Part 1, we talked about the CMS - how Optimizely CMS is not just a publishing platform but an observation post. Every visit Thomas makes generates behavioral data - which content he reads, how deeply he scrolls, which paths he returns through, how his visit frequency is trending over time. The data is there. The problem is that most implementations are not built to read it as a story. The narrative exists. Nobody is assembling it.

In Part 2, Thomas Becomes Visible

This is where ODP takes the raw behavioral events from the CMS, stitches them together across sessions and channels, and builds a persistent, unified profile that can be segmented, scored, and acted upon. This is not a data warehouse exercise. It is a recognition exercise.

Read the full story here on how we put together an engagement trajectory for Thomas in ODP, that then helps your digital estate recognize him.