> ## Documentation Index
> Fetch the complete documentation index at: https://docs.funeli.top/llms.txt
> Use this file to discover all available pages before exploring further.

# Build, preview and publish a funnel

> How Funeli drafts, revisions, themes, validation, preview and share links and publishing work, in the editor or with an AI agent, from first draft to live funnel.

Every Funeli funnel has a draft that you, your team and your agents edit, and published versions that ad traffic sees. This page explains that cycle from the first draft to a live funnel, and how each stage looks in the editor and with an agent.

## Drafts and revisions

All edits, from the editor or from an agent, go to the funnel's **draft**. Each change is validated before it is saved, and each save becomes a **revision**. To undo, use undo in the editor, restore a revision from **History**, or ask an agent to restore the previous revision.

The draft is never visible to ad traffic. Edit it as much as you like.

## Steps and components

A funnel is a list of steps. The step kind tells Funeli what the step is for:

| Step kind | Use it for |
| - | - |
| Question and info steps | Quiz questions, explanations, social proof, email capture |
| Paywall | Plans and the checkout button; checkout analytics start here |
| Success | The end of the purchase |
| Upsell | Offers after the purchase |

Steps are built from library components. In the editor, add components to a step and set them in the inspector; see [Edit funnels in the editor](https://docs.funeli.top/guides/editor.md). With an agent, describe the result ("add a testimonial under the question", "show the yearly plan first") and it picks the components and their settings.

> [!NOTE]
>
> A paywall needs a plan selector, a checkout button and legal text with the plan terms, including trial and renewal disclosure. Validation reports a paywall that lacks them.

## Themes

Themes live in the project and control colours, fonts and corner radius. A project starts with a set of starter themes for different verticals and moods. Pick one for a funnel, change it, or create your own, in **Themes** or with an agent.

> [!WARNING]
>
> Changing a theme changes every funnel that uses it right away, live funnels included. Check which funnels use a theme before you change it; agents show this and ask first.

Every theme is checked for text contrast and readable type sizes on a phone, and the check suggests fixes for failing colours.

## Preview a draft

Use the device preview in the editor, or open the funnel's preview link on your phone. A preview link opens the current draft and works for signed-in members of your Workspace.

### Share a draft

A share link opens the draft for anyone with the link, for example a client without a Funeli account. It lasts 72 hours by default and up to 30 days, includes later edits and never publishes anything. Ask an agent for a share link, and to turn it off when you no longer need it.

## Validate and publish

**1. Validate**

The editor shows validation warnings in its top bar, and an agent can validate on request. Errors block publishing; warnings, such as long copy or low colour contrast, do not.

**2. Review the changes**

Check what will change compared with the live version. An agent shows the difference between the draft and the published funnel.

**3. Publish**

Use **Publish** in the editor, or ask an agent. Publishing freezes the draft into a new version that visitors see immediately. Because it affects real visitors and payments, agents publish only after you confirm.

A funnel can be published with mock checkout or with a Paddle Sandbox connection; in both cases nobody is charged. Connect a Production payment account before you send real traffic; see [Accept payments with Paddle](https://docs.funeli.top/guides/payments.md).

## After publishing

Open **Analytics** for step drop-offs, paywall to checkout rate, payment success and declines, and results per traffic source or ad creative, or ask an agent to analyse them. Compare versions to see the effect of a change, and use experiments to test bigger changes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.