Drafts & Live Pages
Where work waits before it launches, and where it lives once it has.
Overview
Drafts and Live Pages are two halves of one lifecycle. Everything Tailor builds starts as a draft, whoever or whatever built it, and becomes a live page only when a person starts it.
That boundary is the whole safety model. An approved test idea, an agent-built page, and something created over MCP all land in the same place and all wait for the same click.
The Three Page Types
Both screens are split by page type, and the three behave differently enough that the distinction matters more than it first looks.
Tailored pages
Your page, with Tailor applying changes in the visitor's browser. Can be targeted to an audience and split across variants, which makes this the type you run experiments on. See A/B Testing.
Hosted pages
A frozen copy that Tailor serves at its own URL on your domain, with edits built into the HTML. Reachable by crawlers and AI assistants. See Hosted Pages.
Managed pages
Pages in your own CMS that Tailor edits at the source. Changes save as a draft in your CMS and reach every visitor once your team publishes there, so they are not tests and take no targeting.
A managed-page edit is not a test
Editing a page in your CMS changes it for everyone, so it cannot be shown to one audience and cannot be split. Tailor also cannot publish it for you: the change waits as a draft in your CMS until your team publishes it there. If you want a change measured, use a tailored page instead.
Drafts
Drafts holds everything built and not yet started, split into approved ideas, tailored pages, and hosted pages. Each row shows where it came from, so an idea you approved from Test Ideas is traceable back to it, and pages built by the agent or over MCP carry their own labels.
A row that is ready tells you how many changes it makes and offers a single action to start the test. Nothing here is receiving traffic.
Drafts accumulate, which is normal and mostly harmless: a queue of built-but-unlaunched work is cheaper than a queue of ideas nobody has built. It is still worth a periodic clear-out, because a draft built against a page that has since been redesigned may no longer apply cleanly.
Live Pages
Live Pages is everything currently serving, split by the same three types. This is the screen to open when you want to know what a visitor could actually be seeing right now, which is a different question from what is currently being tested.
A fully ramped page is no longer a test. It is the page, shown to everyone who matches its targeting. Both screens can be sorted, grouped, filtered by creator, searched, and exported to CSV, which is the usual way to get a list into a review doc.
Reading A Row
Rows carry the same information on both screens.
- Name and path. The path is where it applies, and a trailing wildcard means it covers everything under that path rather than one URL.
- Result. Ramp state plus what it has seen so far. A page live for days with no visitors usually means the targeting matches nobody, not that the page is broken.
- Targeting. Who it applies to: all visitors with a traffic split, a URL parameter match, or a tailored link. See the Targeting Guide.
- Preview. Opens the page as that audience would see it, without needing to match the targeting yourself. See QA & Preview.
If a live page reports no visitors after a day, check its targeting before you check anything else. That is the cause almost every time.