How do Storyblok releases interact with scheduled Croct experiences?
Our team plans content in two calendars now and I want to make sure they do not fight each other:
- Storyblok releases for scheduled content updates
- Croct scheduled experiences for campaign personalization
The scenario I worry about is a release going live mid-campaign that changes a block an active experience also targets. Who wins, and what does each group of visitors see? I would rather understand the layering now than debug it during a campaign
1 answer
The two calendars layer rather than fight, once you see what each one controls.
Storyblok content is the default fallback. When a release goes live mid-campaign, it updates what non-matched visitors see, meaning everyone the experience does not apply to. Visitors matched by the active experience keep seeing the experience content, because the experience overrides the default for its audience. So a release never accidentally interrupts a running campaign, and a campaign never blocks your regular content schedule.
On the Croct side, experiences support scheduling too, and the status model makes the calendar readable at a glance: an experience is Draft, Active, Paused, Scheduled, or Archived. Your campaign personalization sits as Scheduled until its window opens, then flips to Active on its own. Worth noting for planning: scheduled publishing is a Scale plan feature on the Croct side.
The practical convention we use is that releases own the baseline and experiences own the exceptions. Documented that one sentence for our editors and the confusion stopped.