Skip to main content
Saving a draft does not change the live release. Preview it, then publish when it is ready.

​
Before the first release

  • Connect the website and confirm an installation check-in.
  • Review and approve the draft.
  • Set a primary goal and traffic allocation.
  • Complete activation if prompted.
For agents, run check_test, call publish with the current version, then reread the workspace. payment_required means checkout is pending; only live confirms activation.

​
Drafts and live settings

Targets, variants, and components are draft changes. Goals, connectors, pause, and traffic allocation are live settings and can take effect separately.

​
Pause or roll back

Pause to keep new decisions on the original. Use publish with rollbackTo to restore a retained content release. Already-open pages can retain loaded content until their lifecycle updates. Reload a real page and verify the serving revision.
Read the current version, review the saved draft, publish with that version, then reread the published revision. Concurrent writes return conflicts. The server owns release identity and resolved component HTML. Retained release history supports content rollback.Use a stable experiment interval when assessing results. Restarting measurement changes its comparison window; it does not erase historical records or make an old interval comparable to a newly changed population.Rollback restores content, not goals, connectors, billing, experiment allocation, or software/database migrations. Demo workspaces must be connected before live publication.