# Can our marketing team run Storyblok experiments without a dev ticket each time?

Asked by Larissa Fontes on 2026-07-26. Tags: storyblok, marketers, ab-testing.

Our site runs on Storyblok and right now every content variation we want to
test means filing a ticket and waiting on the dev queue, which usually
pushes a small copy change out by a couple of weeks.

I just came across the Croct Optimize app and it sounds like the promise is
that marketing can actually launch and manage experiments on its own once
everything is wired up. Before I get my team excited about it, can someone
who is using it confirm what marketers can genuinely do without a developer
in the loop, and where the one dev step actually sits? Thanks in advance.

## 2 answers

### Accepted answer from kenji_tada (2026-07-27)

Yes, that maps to how it works in practice. The one developer step is the
initial wiring: someone adds a Croct field to the blocks you want to test
and connects each one to a matching Croct slot. That happens once per
block, not once per test. There is a walkthrough in
[linking a Storyblok block to a slot](/answers/storyblok-link-block-to-slot)
if you want to see the shape of it.

After that the loop is yours. The Optimize app runs inside the Storyblok
interface, so your team builds the audience, sets the variant content,
previews it, and publishes without touching code. Pausing and rolling out
the winner are the same, no deploy. The only thing to hand back to a dev is
when you want to personalize a brand new block that was never linked.

### Answer from Marta Ruiz (2026-07-27)

One detail that made my team comfortable: the blocks you already have in
Storyblok stay put and serve as the default fallback. So anyone outside an
experiment, or if you pause everything, just sees the original block. You
are layering variants on top rather than replacing your content, which
means there is very little to break if you want to back out.