Funnels overview
The step model, page-type constraints, and how thank-you/error pages snapshot at funnel creation.
A funnel is an ordered sequence of pages that guides a visitor from a landing experience through checkout and post-purchase steps. Every page in a funnel is drawn from the pages you have already created in the deployment.
Funnel structure
Each funnel consists of four logical groups of steps, in order:
- Landing steps (0 or more) — optional pre-checkout pages that warm up the visitor. Each landing step references a page of type
custom. - Checkout step (exactly 1, required) — the payment page. References a page of type
checkout. - Upsell steps (0 or more) — post-checkout offer pages. Each upsell step references a page of type
upsell. - Thank-you and error steps (1 each, auto-bound at creation) — terminal pages after a successful or failed payment. These reference pages of type
thankyouanderrorrespectively.
The navigation order is fixed: landing pages proceed in subOrder sequence, then checkout, then upsells in order, then thank-you. The error page is reached only when a payment attempt fails.
Step-to-page type constraints
Each step in a funnel must point at a page whose type matches the step type:
| Step type | Required page type |
|---|---|
| Landing | custom |
| Checkout | checkout |
| Upsell | upsell |
| Thank-you | thankyou |
| Error | error |
Assigning a page of the wrong type is reported by the funnel validator as an error (see Funnel validation).
You can skip the landing step entirely. A funnel with just a checkout step is valid. If your landing content (hero video, product photos, testimonials, FAQ) can fit on the same page as the checkout form, build it that way — drop the landing components above the checkout components on a single Checkout-type page, and your funnel becomes a one-page flow. Fewer pages, less navigation, sometimes higher conversion.
Many-to-many: sharing a checkout page
A single checkout page can be referenced by multiple funnels. This is common when you run several landing variants that all converge on the same checkout experience. There is no limit on how many funnels can share a checkout page.
Thank-you and error page snapshots
When you create a funnel, autonnel automatically picks the first available thankyou page and the first available error page from your deployment and snapshots their IDs into the funnel’s step configuration.
“Snapshot” means the funnel records which page to use at creation time. After that point:
- Edits to the deployment page (content, slug, settings) are not automatically reflected in the funnel.
- If you delete the deployment page, the funnel step becomes broken — it still holds the old page ID, but the page no longer exists.
- You can replace the snapshotted page at any time from the funnel detail page by choosing a different page from the dropdown on the relevant step row.
This design gives each funnel an independent, stable configuration that does not silently change when shared pages are edited.
Missing thank-you or error page
If your deployment has no thankyou or no error page at the moment a funnel is created, the corresponding step is left unbound. The funnel detail page displays an advisory banner prompting you to go to /pages and create the missing page type. The banner is informational — it does not block saving the funnel or serving traffic.
Caveats
- No built-in versioning. Funnel configurations are not versioned. If you need to roll back a change, you must make the change manually.
- Broken steps from deleted pages. If you delete a deployment page that is referenced by a funnel step, the funnel detail shows the step as broken. Reassign the step to a different page to restore it.
- Snapshot decoupling is one-way. Once a thank-you or error page is snapshotted into a funnel, editing the original deployment page has no effect on the funnel. You must explicitly re-link if you want the funnel to use the updated page.