Our slots are wired up, can I build and launch a new experience myself without filing an eng ticket?
Our developers integrated the slots a few weeks ago, and now I would like to run campaigns on my own schedule instead of queuing behind the eng backlog.
So the practical question: once the slots are in place, can I create a new experience with its variants, target an audience, and publish it, all from the dashboard? Or does spinning up a new experience still need a developer each time?
2 answers
Once the slots are integrated, a new experience is entirely yours. The flow is three steps and none of them touch code:
- Define the audience. This is who should see it, built from conditions like location, campaign source, behavior, or device.
- Specify the content for each slot, including the variants you want.
- Preview it, then publish.
That is the whole loop, and it is designed for non-developers to run start to finish. Launching, pausing, and rolling out experiences and experiments all happen in the dashboard with no deploy. Our marketing team ships variants now without opening a ticket, which was the entire reason we moved to this setup.
The developers only ever come back in when you need a brand-new slot in a place they have not wired yet. For everything within the slots you already have, you are self-serve.
That settles it, exactly the answer I was hoping for. Appreciate the clear breakdown of where the dev line sits.
confirming from our side too. devs touched the slot wiring once at the start and have not been involved in a single experience since. audience, content, preview, publish, all in the dashboard. the only time we pulled one back in was to add a new slot on a page that did not have one yet.