Editor updated a Storyblok block but some visitors still see different content
Trying to reconstruct what happened here. One of our editors opened the homepage story in Storyblok, rewrote the hero block copy, clicked Publish, and verified it live in an incognito window. All good. Then QA reported that some visitors still see completely different hero copy, not the old version, a different one.
Nobody on the content team remembered that an experience might be running on that slot, and it turns out one was set up months ago by someone who left. My question is how do I see, for a given slot, what overrides what? I want a way to check this before edits, not after QA catches it
1 answer
What you saw is the system working as designed, just undocumented inside your team. The Storyblok block is only the default fallback. Any active experience on that slot overrides the default for the audience it matches, so visitors in that audience got the experience content while everyone else got the new hero copy. That is why QA saw a third version.
To audit a slot, open it in the Croct dashboard and look at the experiences targeting it. Two things to check:
- Which experiences are Active. Each one serves its own content to its matched audience instead of the Storyblok default.
- The priority. When several experiences target the same slot, each has a unique numeric rank and the higher priority wins for visitors matching more than one audience.
If the orphaned experience should not run anymore, pause it. Once paused, all visitors see the default slot content again, meaning your editor's new copy. There is more detail on that behavior in what visitors see when an experiment is paused.
For prevention, add "check the slot's experience list" to your publishing checklist for any block that is connected to a Croct slot.
Found it, one Active experience from last year targeting returning visitors. Paused it and QA confirms everyone sees the new copy now. The checklist idea is going straight into our editor handbook, thanks.