Content management systems (CMS) have evolved beyond simple content delivery to meet the growing demands for dynamic, personalized digital experiences.

Storyblok is one of the leading headless CMS platforms used by developers and marketers alike. However, it has significant shortcomings when it comes to website personalization and AB testing.

When you're starting a website from scratch, your goal is probably to build one that gives your content team the autonomy to work without relying on developers. The main requirements at this moment usually are:

• It needs to be fast to load
• It needs to be indexed by search engines
• It needs to be scalable
• It needs to provide a good experience for content managers

But what about those things that come right after the website launch? You are about to make a decision for many, many years, so you need to think about what's to come.

The marketing team starts driving traffic to the website. Soon enough, they start analyzing data to understand user behavior, which leads them to uncover optimization opportunities and the need to test some hypotheses. As the next step, they need to personalize content for some user segments to increase conversions.

In the blink of an eye, you'll see yourself in the same situation again: the marketing team will become dependent on developers for everything. In this post, we'll explore Storyblok CMS, its limitations, and your alternatives for experimentation.

What Storyblok CMS is good for

Storyblok is a headless CMS that allows developers to build flexible, scalable websites while giving non-technical users a user-friendly interface to manage content.

They're slightly focused on some industries like retail, SaaS, financial services, and education, but most of their applications are for static content, like:

• Static websites, like corporate, publishing, or editorial websites
• E-commerce
• Mobile apps
• Industry-specific virtual and augmented reality applications

Storyblok is ideal for content-rich websites that need flexibility and scalability without being tied to a traditional monolithic CMS structure.

What Storyblok offers natively for personalization and AB testing

Storyblok has expanded well beyond pure content delivery. Understanding exactly where its native capabilities end is what tells you whether you need anything else.

Native AB testing

In June 2026, Storyblok launched native AB testing as part of Storyblok Labs. It gives content editors a genuinely good interface for defining experiments, creating story variants, and assigning traffic weights directly in the Visual Editor.

It is a content-only feature by design. Storyblok defines which variants exist, while your engineering team builds everything that makes an experiment actually run:

• Variant assignment and bucketing logic
• Same-device and cross-device stickiness, including cookie management
• Conversion tracking and goal instrumentation
• Statistical analysis, via an external analytics platform, with results pushed back through the Management API

It's also limited to customers on Premium and Elite plans.

The VWO plugin

Storyblok and VWO launched an official plugin in August 2025, letting marketers run VWO experiments from inside the Visual Editor. VWO handles setup and analysis, which closes the pipeline gap that the native feature leaves open.

The requirement is two subscriptions: the plugin is included for Storyblok Premium and Elite customers, and running experiments requires a VWO Enterprise account or a VWO plan with the Developer Plus add-on.

Website personalization

Storyblok's native experimentation is scoped to AB testing story variants. Real-time behavioral personalization (targeting based on what a visitor is doing in the current session, firmographic data, or custom profile attributes) still requires either a dedicated engine or a personalization layer you build and maintain yourself.

Storyblok publishes guidance on personalization patterns, but implementing them means building the engine that collects user data, evaluates segments, and resolves content against them.

What this means

If you're on Premium or Elite, have engineering bandwidth to build a decision engine, and only need AB testing on story variants, Storyblok's native feature is a strong foundation. If you need the full pipeline without building it, need to run on a lower Storyblok plan, or want to move from AB testing into real-time personalization, you'll want a dedicated engine.

Alternative for personalization and AB testing

The Optimize app is designed specifically to address the challenges of personalization and AB testing. Here's why it stands out:

• Gradual integration

  You can connect block by block based on your needs without significantly modifying your existing infrastructure or relying on developers.

• Unified solution

  Instead of relying on multiple tools for personalization and AB testing, it provides an all-in-one platform that integrates smoothly with Storyblok, saving you time and effort. It also provides built-in CDP and analytics capabilities.

• Real-time personalization

  It lets you easily segment users based on their behavior and preferences, and then serve personalized content in real time. You don’t need to build complex logic or custom integrations, as it takes care of this automatically.

• Bayesian AB testing

  It includes native AB testing capabilities using Bayesian statistics, enabling more efficient tests with greater confidence and statistically significant results. This helps you optimize your website or app more quickly and with less traffic.

• Developer-friendly

  With first-class developer support, it offers intuitive APIs and SDKs that simplify personalization and testing workflows, reducing the need for manual implementation.

Keep using your existing blocks

That's right, you don't have to reimplement anything.

This app adds dynamic content for experimentation and optimization directly to your existing blocks, so you can use it only for the elements and components you want to experiment with.

Let's say you have a website where the top menu, main banners, and forms are the most important for conversion. These could be dynamic elements integrated with Croct for AB testing or personalized communication, while the rest of the website could still live in Storyblok.

You can gradually connect elements and components between Storyblok and Croct without relying on developers, giving the content and the growth team the autonomy they need.

If your goal is to create dynamic, user-specific experiences and optimize conversions, take the first step by exploring the integration.