Minesh Shah (Netcel)
+7
Feb 12, 2026
visibility 1188
star star star star star
(1 votes)

Personalisation in CMS 13 Using Audiences

One of the common questions around CMS 13 is whether it still supports personalisation without requiring additional products. The short answer is yes.

CMS 13 includes built in personalisation using what were previously known as Visitor Groups. In CMS 13 these have been renamed to Audiences (Correction they changed to Audiences in latter versions of CMS12 which somehow I missed, Thanks Scott for pointing this out), but the core concept remains the same. You can define audiences based on visitor behaviour and use them to tailor content across your site.

Audiences are managed directly within the CMS interface. For example, you might create an audience made up of visitors who have viewed pages with a specific category more than a set number of times. Once an audience is defined, it can be used to control how content is displayed.

Personalisation is applied at the content level using standard content areas. Editors can choose to show or hide individual components such as a hero or jumbotron based on the selected audience. This allows targeted experiences without introducing additional complexity for editors.

CMS 13 also supports previewing content as a specific audience. This makes it easy to validate personalisation rules and understand exactly what different users will see before changes are published.

This approach provides traditional, rules based personalisation out of the box and offers a clear path to more advanced personalisation in the future if needed. For many organisations, it delivers exactly the right level of capability from day one.

A short video walkthrough is included below to demonstrate this in action.

Feb 12, 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 |