Managing Rules

Edits to a rule's body — its targeting, variations, traffic split, name, order, and the act of declaring an A/B test winner — flow through the draft pipeline and require Publish changes to go live. Turning a rule on or off uses the separate Run and Pause controls and goes live immediately. See Rule Statuses for the operational flow.

Reordering rules

Each rule card has a grip handle on the left edge. Drag a card by its handle and drop it where you want it in the list. The new order is staged in the draft and shows up in the bottom bar's change count as one pending change, regardless of how many cards moved.

• The handle responds to mouse, trackpad, touch, and keyboard input. Use Tab to focus a handle and Space to start a keyboard reorder.
• The change appears in the Review changes panel as a singleReordered N rules entry that lists the new order.
• Save & publish persists the new sortOrder values to every affected rule in one transactional bulk save.

Opening a deleted rule by URL

If you (or another editor on the shared draft) have queued a rule for deletion, the rule no longer appears in the list. But a deep link with?rule=<id> still resolves — opening the rule detail panel with a yellow banner instead of silently doing nothing.

The banner gives you two options:

• Undo delete— Restores the rule in your draft. The rule reappears in the list, marked Edited so you remember it was touched. Save & publish keeps it.
• Close — Closes the panel and leaves the deletion queued. The rule still goes away on the next publish.

The rule's form fields are read-only while the banner is showing. Native inputs are disabled, and every custom control inside the panel — chip pickers for audiences and metrics, the drag-to-reorder primary-goal list, the Manual / Allocate Equally toggle on the traffic allocation card, and lock buttons on the variation sliders — renders a faded, non-interactive state so it's obvious at a glance the form is currently a tombstone. Restore the rule first if you want to edit it.

Concluding an A/B test

Declaring a winner used to write directly to the live tables and force a page reload. It now goes through the draft like every other edit:

1. Open the kebab menu on a running A/B test rule and chooseConclude.
2. Pick the winning variation. Optionally checkStopped early under the Frequentist engine and add a one-line reason.
3. Confirm. The modal closes and the bottom bar's change count increases by one. The rule shows theConcluded badge in the list.
4. Click Save & publish to commit. The winning variation gets pinned to 100%, concludedAt is set, and (if you marked early stop) the early-stop fields are persisted.

Concluded rules can no longer be edited — only duplicated or deleted — and they don't move with drag-to-reorder, since their order doesn't affect bucket assignment any more.