Save and publish
Keep drafts private and publish Pages and Checkouts deliberately.
Updated July 29, 2026On this page
- A Page or Checkout draft
- Permission to change customer-facing content
Pages and Checkouts use deliberate Save, then Publish controls. Funnels do not have a Publish action. This keeps unfinished edits private without requiring operators to publish the same journey twice.
The resource lifecycle
| Action | Result |
|---|---|
| Edit | Changes exist only in the current browser until saved |
| Save | Writes a private draft revision; customer traffic is unchanged |
| Publish | Promotes the exact saved revision for new customer sessions |
| Save Funnel | Stores its graph and settings, then activates or refreshes it when all published dependencies are ready |
Publish a Page or Checkout
Save the draft
Choose Save in the designer. Recurrify does not auto-save, and the Publish action remains unavailable while unsaved browser changes exist.
Review the published state
Preview the saved draft and resolve validation errors. The toolbar distinguishes Not published, Saved draft not published, and Published.
Publish deliberately
Choose Publish. The published revision becomes available to new sessions, and affected Funnels refresh automatically. A session already in progress remains pinned to its starting runtime revision.
Screenshots and Funnel thumbnails
Each Page or Checkout publication queues a screenshot for that exact published revision. Recurrify caches the image and reuses it wherever the resource appears in a Funnel graph. A later publication invalidates the old image and generates a new one. Missing historical screenshots can be backfilled without republishing customer content.
Saving a Funnel updates its graph, router, paths, offers, promotions, and tracking. If its domain, router, and published resources are ready, the Funnel becomes live or refreshes immediately. Otherwise it stays saved and activates after the missing Page or Checkout is published.