Can marketing run experiments on our Strapi site without dev tickets?
Every copy change on our Strapi site goes through a dev sprint, so an A/B test today means two tickets, a two-week wait, and another ticket to remove the losing variant. By then the campaign is over.
If we adopt an experimentation platform on top of Strapi, what does the division of labor actually look like afterwards? I am trying to figure out whether I could publish and pause tests myself once the initial setup is done, or wether devs stay in the loop for every single experiment.
1 answer
The division of labor splits cleanly into a one-time developer task and an ongoing marketer workflow.
Developers do the initial work once: mapping the Strapi components you want to test to Croct slots in the frontend. After that, experiments do not require code changes.
From then on, everything happens in the Croct dashboard:
- Create an experience and define its audience.
- Author variant content in the experience editor; your Strapi content remains the default.
- Attach an experiment, publish it, pause it, or roll out the winner yourself.
Each new component you want to test does need a developer to map it once, so the practical approach is to have the components you test most often (hero, CTA, pricing highlights) mapped up front.
For reference on turnaround: CVC's team launched experiments in about 20 minutes once slots were integrated. The workflow is described in more detail in the Croct documentation.