Personalization & A/B Testing

Alokai CMS can serve different content to different visitors. There are two building blocks: audiences (who someone is) and experiences (what they see, and how variants compare).

Audiences

An audience is a named segment of visitors defined by rules — for example a region, device, or a custom attribute passed by your storefront. Audiences have a priority: when a visitor matches more than one, the highest-priority audience wins.

Manage audiences for the active edition; each carries its rule set and priority. Audiences are edition-scoped.

Experiences (A/B tests)

An experience is attached to a page and defines variants of that page’s content. Visitors are bucketed across the variants, and the CMS records impressions so you can compare them.

• Targeted experiences serve a variant to a matching audience.
• A/B experiences split traffic across variants to find the best performer.
• Auto-conclude can pick a winner automatically once each variant has collected enough data (a minimum sample of impressions per variant).

Bucketing is sticky per visitor, so a returning visitor keeps seeing the same variant.

How it fits together

Visitor ──▶ match audiences (by priority) ──▶ experience on the page ──▶ variant served

Experiences live on a page within an edition, so you can trial personalization in a staging edition before promoting it. For the developer-facing model (bucketing, impression tracking, rule evaluation), see the A/B Testing page in the developer documentation.