Preview, publish, and roll back

Preview: your store, your browser, nobody else

Every change can be previewed on the real storefront before any visitor sees it. A preview link opens your own store with the pending changes applied and a QA badge confirming you are in preview mode. When the preview belongs to an experiment, the badge carries a variant selector, so you can switch between variants in place instead of minting one link per look.

Two properties make previews safe:

• A preview session lives only in the browser tab that opened it. It dies with the tab and never affects a real visitor.
• No measurement events are ever emitted in preview. If you are testing through a preview link and see no numbers, that is the design, not a fault.

Publish: seconds, not deploys

Publishing takes everything pending — content changes, experiment configuration, settings such as authorized hosts and telemetry — and makes it the live version. Publishes propagate to visitors globally in under a minute, and there is no theme deploy involved at any point.

If two people publish at the same time, the operations cannot interleave: one lands, the other is asked to retry on top of it. What you approve is exactly what ships.

Roll back: the undo button, always loaded

Every publish keeps a permanent point of return. From the dashboard you can:

• Roll back to the previous published version: one click, live in under a minute.
• Kill switch: stop everything Proa is doing on the storefront at once. The store returns to exactly what the theme serves on its own.

Both are content operations, not deploys, so they are as fast and as safe as publishing. This is the property the rest of Proa leans on: experiments are only cheap to run because undoing one is cheaper still.