Build, save and publish a hosted landing page
Use the block editor without confusing the saved draft with the version customers can see.
3 min read
Screenshots show the real application in an isolated demo environment with fictional example data. Setup notices and controls may differ by environment, plan and role. Click an image to view it full-size, and always use the values generated in your own workspace.
A page and a campaign have separate states
A landing page is the presentation around your offer. Its countdown block refers to the connected campaign. Publishing the page does not fix an unpublished, expired or plan-restricted campaign, and publishing the campaign does not automatically publish an unpublished page.
The live page keeps the last published version. Saving later edits updates the draft only until you publish again. This lets you edit without immediately replacing the page customers are using.
Build a page step by step
- 1Open Landing pages and create or edit a page connected to the intended campaign.
- 2Give the page an internal name and choose its address slug. Use a meaningful URL and avoid changing it after distribution.
- 3Add blocks from the block library. Select a block to edit its content and style. Use reorder controls or drag-and-drop to arrange the story of the offer.
- 4Adjust the page font, colors, content width and block spacing. Inspect the countdown block’s saved design.
- 5Save the draft and use the draft preview. When ready, publish the page and open its actual public address.
Editing, undo and local recovery
Use the editor’s undo/redo and block controls to correct editing mistakes, but do not treat browser-local recovery as a permanent server backup. Save meaningful changes before closing the editor or switching devices.
A duplicate block copies that block’s configuration; review its links and text. Deleting a block removes it from the draft, and the change becomes live only after the page is published again.
Buttons and conversion recording
Set button and hero links to your real offer destination. The Count CTA clicks as conversions setting is off by default; turning it on records supported CTA clicks as conversion events.
A click-based conversion is not proof of payment or order completion. If you need confirmed sales reporting, connect your application’s actual completion event through the supported integration workflow.
Unpublish and rename carefully
Before unpublishing or changing a slug, check emails, ads and website links that use the page. Customers may still follow an old address. Prefer a planned replacement and test public links after every publication change.