The visual editor

The visual editor opens your real page in a new tab with the editor panel docked on the right. Nothing is loaded inside a preview frame: cookie banners, logins and anything else that refuses to run inside an iframe work exactly as they do for visitors. Click any element to edit it, and use the collapse arrow on the panel to reach whatever it covers.

A control strip runs along the bottom of the screen and stays there whether the panel is open or collapsed. It holds the test's name and status, and everything that is about the session rather than the selected element: which variation you are editing, adding a variation, the edit/navigate switch, the desktop/tablet/mobile switch, Save and Exit. Renaming the test counts as an unsaved change, so it travels with you and is written on the next save. The panel above it is for the element you have selected.

Editing more than one page

A test can change several pages. Switch the strip from Edit to Navigate and links and buttons work again, so you can walk to the next page; the editor follows you and reopens there with your unsaved edits intact. Turn Navigate off to select elements. Every change is pinned to the page it was made on, and Config → Pages lists every page the test touches — click one to go there. When the test runs, a visitor on any of those pages sees the changes for that page only.

Selecting elements

Hover to highlight, click to select. The sidebar shows the selected element's properties, HTML and attributes.

What you can change

• Text & HTML — edit the inner HTML directly (with formatting).
• Styles — typography, colours, spacing (padding/margin with linked sides), borders and radius, opacity and more, with px/em/rem/% units.
• Attributes — image src/alt, video poster, etc.
• Hide or remove an element.

Responsive editing

Use the device switch in the control strip to move between desktop, tablet and mobile modes, which preview and apply device-specific overrides on top of your base styles. Tablet and mobile show your page at that width in a frame next to the panel — the page's own responsive layout applies — and you keep editing and navigating inside it. The breakpoints used are the ones set on the test (defaults: tablet ≤ 1024px, mobile ≤ 768px).

AI rewrite

Select an element and use AI rewrite to generate alternative copy/markup, preview a before/after comparison, and apply or refine it.

History

Every change is tracked. Use undo/redo in the header, jump to any point in history, or Reset to return the variation to its original state. Click Save in the control strip to persist your changes.

Leaving the editor

Exit always asks before it closes. With unsaved changes you choose between saving them, discarding them, or staying; with everything saved it confirms and then returns the page to how a visitor sees it. There is no undo once the editor is closed, which is why it asks every time.

How edits are matched at runtime

Each edit is stored as a selector plus the change to apply. If your page markup changes later — a redeploy that renames a class, a CMS edit that moves a block — the selector may no longer match and that edit silently stops applying. Re-open the editor after any significant front-end release and confirm your active variations still look right.

The editor session uses a time-limited token; if you see an expiry warning, click Extend session to keep working. A session can be extended for up to 12 hours; after that, open the editor again from the dashboard.