How a funnel is structured
Pages, blocks, and the two structural rules the runtime enforces.
A funnel is an ordered list of pages. A page is an ordered list of blocks. That is the entire model — there are no sections, columns, or nesting to reason about.
A responder sees exactly one page at a time and moves forward by pressing that page's button. Every responder sees every page, in the order you set, because conditional branching does not exist yet.
Page types
| Type | Purpose |
|---|---|
| Landing | The opening screen. Sets the offer and earns the first click. |
| Registration | A question page. Most of your funnel is these. |
| Signup | The contact page, where you ask for an email address. |
| Thank you | The closing screen shown after a successful submit. |
The type is mostly a label for you, with one exception noted below.
Two rules worth knowing
These are enforced by the public runtime, so a funnel that ignores them will not behave the way it looks in the editor.
- One button per page. The runtime treats the first button on a page as that page's navigation control and ignores any others. If you add a second button it simply will not appear to responders.
- One thank-you page, and it must be last. It is skipped during normal navigation and rendered only after a successful submit.
Working with pages
- Add a page from the left panel, either blank or from a page preset
- Drag pages to reorder them
- Select a page to edit its title and internal description
- Delete a page you no longer need