# Can marketers publish experiments themselves without touching the codebase?

Asked by Vera Kostova on 2025-06-25. Tags: workflow, roles, collaboration.

Right now every banner change I want goes into a ticket, waits two sprints, and
ships about two weeks after the moment it mattered. I am evaluating Croct
specifically to break that cycle.

So the direct question: once our devs do the initial integration, what can I
actually do on my own? Can I create an A/B test, publish it, pause it, and roll
out the winner without filing a single ticket? And where exactly does the dev
dependency end, because I have been promised "no-code" before and it turned out
to mean no-code except for everything I actually wanted to change

## 1 answer

### Accepted answer from Hollis Grant (2025-06-26)

I run this exact split with our marketing team, so here is where the line
actually sits.

Dev-owned, one-time per placement: integrating the slots into the codebase and
defining the component schemas. A schema says "a hero has a title, a subtitle,
an image, and a CTA label". That is the contract, and it is the only part that
lives in code.

Everything after that is yours in the dashboard. You build experiences and A/B
tests against those schemas, fill in content and variants, define the audience,
publish, pause, and roll out winners. No code changes, no tickets. Our
marketers have shipped dozens of tests since the initial integration and I have
touched the code maybe twice, both times to add a brand-new slot.

The part that makes this hold up over time is auto-versioning: when devs evolve
a component schema, it creates a new version while old versions keep serving.
So your published experiences do not break when the app changes underneath
them, which is usually where "no-code" promises fall apart.

#### Reply from Vera Kostova (2025-06-26)

The schema-as-contract framing is what I needed to bring to my eng lead. If
the dev work is one ticket per placement instead of one per change, that is
a completely different conversation. Thanks.