We have long admired Storyblok for its flexibility and component-based approach. It is a powerful CMS, but as we noted a while ago, it was not built with native personalization or experimentation at its core.
The ecosystem has tried to fill this gap. Late last year, they introduced a VWO plugin to bring content optimization to the platform. While it was a step forward, we noticed that the implementation still required significant coding for each content block, keeping marketing teams dependent on developers for every new block integration.
We spent time listening to Storyblok's solution engineers and partner agencies. They shared a common insight: existing plugins often felt rigid and quite limited, requiring users to constantly switch between Storyblok's UI and external platforms to configure tests or analyze results.
We became partners, learned about Storyblok's architecture, used it ourselves, and realized there was a way to make this better. So, we decided to build the solution they were asking for.
Today, we are launching our native Storyblok integration.
The end of context switching
This is not just a plugin, it is a complete embedding of Croct’s capabilities into your existing workflow. Unlike other solutions, our plugin lets you do everything without ever leaving the Storyblok interface.
- Create personalized experiences and AB tests directly in Storyblok.
- Analyze performance dashboards and metrics right where your content lives.
- Iterate and adapt strategies instantly without tab-switching friction.
Minimal code, maximum performance
We believe implementation should never be a burden.
We have seen tutorials on hand-coding personalization in Storyblok, which often require modifying multiple files, managing cookies manually, and writing extensive logic for each component.
We've recreated this tutorial using Croct, you can check it here.
Even other plugins often require you to manually add fields to every block you want to test.
We took a different approach. You can integrate Croct into your Storyblok project by running a single command line:
croct initOnce installed, we handle the heavy lifting. And if you are concerned about performance, just don't: our integration runs on the server side, ensuring high performance and eliminating the flicker effect often associated with client-side solutions.
Full autonomy for marketers
We designed this to break the dependency cycle. Once a developer runs that single command, the marketing team has full control.
They can run as many AB tests as needed or create complex personalization experiences without touching the source code again. It is the flexibility of a headless CMS combined with the power of a dedicated optimization engine.
Available now
We are thrilled to finally share this with the community. It represents a major leap in how content and data can work together inside Storyblok.
Check our documentation to get started and try it today to see the difference for yourself.