Version 1.4

Persona started as a way to turn an engagement matrix into something that could work in the real world. Rather than treating audience segments and engagement models as planning artefacts, the idea was to make them part of the website itself, allowing content to be targeted based on what we knew about a visitor and how they interacted with the site.

The original approach used cookie-based tracking and the WordPress database to build that picture over time. It proved the concept, but on larger websites the volume of behavioural data became increasingly burdensome for WordPress. Moving that data into alternative stores with later versions helped with the database problem, but didn’t solve the underlying architectural issue. We were still capturing interactions and writing them somewhere, creating an overhead within the visitor experience simply to maintain the profile.

By early 2026, it was clear that continuing to optimise that architecture wasn’t the answer, and the Persona project was abandoned. The idea wasn’t.

The lessons from Persona led directly to Persona26, which keeps the original ambition of understanding visitor interests and adapting content around them, but approaches the problem differently. Instead of continually building a central server-side behavioural record, Persona26 keeps a lightweight visitor profile in the browser and uses Independent Analytics to connect identity and engagement back into the WordPress experience.