# Rolling out a redesigned PDP section to 10% of traffic on Hydrogen

Asked by antonb on 2026-06-10. Tags: shopify, hydrogen, feature-flags, rollout.

We rebuilt the recommendations section on our product pages and I want a careful
rollout: 10% of traffic first, watch the metrics, then ramp. Our flag tool quoted
us an experimentation add-on priced per 1k MAU on top of what we already pay for
flags, so I am checking what Croct covers natively before we commit.

The question I always ask before adopting anything: how does rollback work? If
the new section tanks add-to-cart, what exactly do I do, and does it need a
deploy?

## 1 answer

### Accepted answer from Croct Bot (2026-06-10)

[Feature flags and server-side testing](https://docs.croct.com/immersion/tutorials/experiment-feature-flagging) are built into the platform, there is no
separately metered add-on for experimentation.

For your rollout, model the PDP section as a slot and attach an experiment to
the experience. Experiments support a traffic allocation percentage, so you can
set it so only 10% of traffic sees the variants while everyone else gets the
default slot content. When you are ready to ramp, note that changing traffic
distribution mid-experiment is strongly discouraged because it invalidates the
statistics, so the cleaner pattern is to conclude the 10% experiment and start
the next stage at the higher allocation.

Rollback works without a deploy: pausing the experience is a dashboard
action that rolls everyone back to the default slot content immediately. No
deploy, no code change, no waiting on a release window. Since content resolves
in your [Hydrogen loaders](https://docs.croct.com/reference/sdk/hydrogen/content-rendering), the next request after pausing already serves the
default section.