Can our marketing team run Storyblok experiments without a dev each time?
I work in growth marketing. Our dev team runs two-week sprints and the backlog is what it is, so any test I want to run today realistically ships in a month. We are on Storyblok and I keep reading that after some initial setup the experiments can be run by marketing directly.
Can someone confirm what that actually means in practice? Once a developer has done the block-to-slot linking, can I create an experiment, publish it, watch it, and stop it entirely on my own? Or is there still a code change hiding somewhere in the loop, like when I want to roll out the winner.
1 answer
Once the blocks are linked to slots, the loop you described is fully yours. That linking is the only developer step, and it happens once per block, not once per test.
From there you work inside Storyblok's interface. Each experience follows the same three-step flow: define the audience, specify the content for the slot, then preview and publish. Publishing can also be scheduled if you want a test to start on a specific date.
To your last question: publishing, pausing, and rolling out a winner are all no-code actions. When an experiment finishes you promote the winning variant yourself, no release train involved. The one thing I would flag is to avoid changing traffic allocation or adding and removing variants while an experiment is running, since that invalidates the statistics. Stop it and start a new one instead.
Teams in your situation usually feel the difference in cadence more than anything else: the dev dependency moves from every test to only the moments when you want to personalize a block that was never linked.
That is exactly what I needed, especially the winner rollout part. Taking this to our tech lead, thank you!