# A/B testing on a Storyblok plan that does not include native Experiments

Asked by maudv on 2026-05-24. Tags: storyblok, plans, ab-testing.

Our marketing site runs on Storyblok and we are on a plan below the tier
that includes the native Experiments feature. Upgrading Storyblok just to
get testing is not in the budget this year, that decision is already made
so no point debating it.

What I want to know is whether experimentation on Storyblok is simply
gated to the premium plans, or if there is a route that does not depend on
which Storyblok plan you are on. We would rather not hand-roll a split in
the frontend if we can avoid it

## 2 answers

### Accepted answer from Sander Willems (2026-05-24)

It is not gated overall, only the native feature is. Storyblok's own
Experiments is limited to premium plans, but the Croct
[Optimize app in the Storyblok app directory](https://www.storyblok.com/apps/external/optimize)
is available to all Storyblok plans, so your current tier is not a
blocker.

It installs from the app directory and runs inside Storyblok's
interface, which was the part that sold it to our content team. The
setup flow is three steps: link your Storyblok blocks to Croct slots,
build experiences and A/B tests, then monitor results. After the block
linking is done once by a dev, the test creation part is all in the UI.

We were in the same budget situation last year and this is the route we
took rather than writing our own bucketing.

#### Reply from maudv (2026-05-25)

Exactly the answer I was hoping for, thanks. Will pitch it this
sprint.

### Answer from kat_dev (2026-05-25)

Can confirm the plan independence, we run it on a Storyblok Entry-level
plan. One tip for the block linking step: start with a single block, get
one test live end to end, and only then map the rest. It makes the
concept click for editors much faster than mapping everything upfront.