Create a Page

Pages are the visual surfaces your customers actually interact with — the storefront where they pick a plan, the checkout where they enter details, the payment page where they pay, and the portal where they self-serve. Building them in Content → Pages keeps design, copy, and metadata in one place and lets you reuse the same page across multiple journeys instead of rebuilding it each time.

The page designer — drag components from the palette onto the canvas and configure each block's properties on the right.

Page types

The Pages list groups every page by type and shows its slug, tags, and status:

• Storefront — plan and product discovery; the entry point a buyer browses.

• Checkout — collects the details needed to place an order.

• Payment — captures a payment method or pays an invoice (see External & Hosted Payment Pages).

• Portal — authenticated self-service surfaces for existing customers.

Add a page

1. Go to Content → Pages.

2. Click New Page to start from scratch, or From Template to start from a prebuilt layout.

3. Give the page a name and choose its type.

4. Build the page in the editor by dragging components onto the canvas and configuring each block.

5. Set the page's SEO metadata (title tag and meta description) so it surfaces well in search.

6. Publish the page. Each published page gets a public slug (for example /s/signup); the slug is unique within your tenant.

Bind a published page to a journey step to use it inside a guided flow.

Key concepts

• Draft vs. published. A page only serves publicly once published; the slug is what a journey step (or a direct link) resolves to. Edits are versioned, so you can revert a page to an earlier saved state.

• Reuse over duplication. Because pages are bound to steps rather than owned by one journey, the same checkout or payment page can back several journeys.

Gotchas

• A page that isn't Active/published won't resolve — a journey step pointed at a draft or unpublished slug renders nothing or 404s. Publish before you wire it up.

• Slugs must be unique per tenant; reusing a slug from another page will conflict.

• To translate a page's copy per market, see Localizing Pages.