Visual editor
Edit a variant on your live page: what can be changed, how changes are stored and kept safe, and how editor sessions work.
Editing on the real page#
The visual editor opens on your own site, on top of the page as visitors see it. You click an element, change it, and the change is saved as part of a variant. There is nothing to install beyond the snippet and no browser extension.
What you produce is not a copy of the page. A variant is a short list of precise changes — “replace the text of this heading”, “hide this banner” — that the snippet applies to the live page for visitors assigned to it. The rest of the page stays whatever your site serves that day.
Opening the editor#
Open a variant in the dashboard and choose to edit it visually
You need the member role or higher. The editor opens the page the experiment targets; you can also give it any other URL on one of the site's domains.
Your page loads with the editor on top
The dashboard adds a
lift_editorparameter carrying a short-lived token to the URL. The snippet on the page recognises it, removes it from the address bar and loads the editor. While the editor is open the page shows no experiments and records nothing.Edit, save, exit
Changes are previewed on the page as you make them and stored when you save. Leaving with unsaved changes asks first.
The snippet has to be on the page
What you can change#
The toolbar switches between edit mode, where clicking selects an element, and navigate mode, where the page behaves normally so you can open a menu or move to a state you want to edit. Undo and redo cover every change since the editor was opened.
- Text
- Edit copy in place on the page or in the panel.
- HTML
- Replace the content of an element with markup. Only safe elements and attributes are kept.
- Links and images
- Change the destination of a link, the source of an image, its alt text.
- Style and classes
- Set style properties, add or remove class names from your own stylesheet.
- Hide
- Remove an element from view.
- Insert and move
- Add new content before or after an element, or move an element elsewhere.
- Rewrite with AI
- Ask for alternative copy for the selected element, with an instruction such as “shorter, benefit first”. Suggestions follow the site's brand context and count toward the plan's AI generations. Shown when AI is available for the organization.
- Track clicks
- Create a click goal for the selected element without leaving the page.
The toolbar also lets you look at the other variants of the experiment on the same page, to compare them or start from one of them.
How changes are stored#
Each change is a mutation: a small JSON object with a kind, usually a CSS selector, and the new value. A variant is an ordered list of them. The same format is used by AI-written variants and by the REST API.
[
{ "kind": "text", "selector": "h1.hero-title", "value": "A dry roof by Friday" },
{ "kind": "style", "selector": ".hero .cta", "styles": { "background-color": "#0b6e4f" } },
{ "kind": "attr", "selector": ".hero .cta", "name": "href", "value": "/book" },
{ "kind": "hide", "selector": ".promo-banner" },
{ "kind": "insert", "selector": ".hero .cta", "position": "afterend",
"html": "<p class=\"note\">No call-out fee.</p>" }
]| Kind | Fields | Effect |
|---|---|---|
| text | selector, value | Replace the text of every matching element. |
| html | selector, value | Replace the inner HTML of every match. Sanitized when saved and again when inserted. |
| attr | selector, name, value | Set one attribute, or remove it with a null value. Event-handler attributes and unsafe URLs are rejected. |
| style | selector, styles | Set inline style properties, written in kebab-case (background-color). |
| class | selector, add, remove | Add and remove class names. |
| hide | selector | Hide every match (display: none). |
| insert | selector, position, html | Insert sanitized HTML before, inside or after the first match (beforebegin, afterbegin, beforeend, afterend). |
| move | selector, target, position | Move the first match to a position relative to the first element matching target. |
| css | css | Inject a stylesheet. @import, expression() and non-https url() are rejected. |
| redirect | url, preserveQuery | Send the visitor to another page of the same site (split-URL test). The query string is carried over unless preserveQuery is false. |
Selectors are generated for you from the element you click. Prefer elements with a stable id or class: a selector that depends on position breaks when the page layout changes. If a selector stops matching, the change simply does not apply; it is reported in the debug panel and the rest of the variant still works.
What a variant can never do#
There is no mutation that runs JavaScript, and there never will be. That rule is what makes it reasonable to let an AI write variants and to let them go live on a production site.
- HTML is sanitized on the server when a variant is saved, and inserted through an allow-list in the browser. Scripts, event-handler attributes and
javascript:URLs do not survive either step. When saving removes something, the editor tells you what. - Attribute changes cannot set event handlers or unsafe URLs. Stylesheets cannot import other files or load from non-HTTPS URLs.
- Redirects only go to pages of the same site.
- Every change is reversible: the snippet remembers the original state and restores it when a variant is switched off or consent is withdrawn.
Editor sessions#
The editor runs on your site's origin, where your Avenue Lift login does not exist. It authenticates with a short-lived token instead:
- A token is valid for 1 hour and only for the one variant it was created for. Open the editor again from the dashboard when it expires.
- It is kept in the tab's session storage and removed from the URL as soon as it is read, so it is not bookmarked, shared or sent to other sites as a referrer.
- If someone else saved the same variant while you were editing, your save is refused and you choose between loading their version and overwriting it.