Landing pages

User guide › Apps › Landing pages

Where it lives

Landing Pages is its own installable app and opens at /landing-pages. It is also one of the marketing channels bundled by Omni Marketing — installing Omni installs it along with the other channels, so you may already have it.

Decide where leads land first

A landing-page form writes a record onto a real entity. Which entity is settled in two places, in this order:

• The page's own pick — Capture into (entity) in the page's Settings panel.
• The Landing Leads role — bind a CRM entity to it under Settings → Entity roles and every page that hasn't picked its own uses that one. In the editor this option reads Default — Landing Leads role.

The role ships with a default Leads entity carrying Name, Email, Phone and Source. Because captures land on a normal entity, they are immediately visible to Audiences and to journeys — nothing extra to wire.

Building a page

1. New page Landing Pages → Pages → New page opens the gallery: Start from a template — pick a professional template or start from scratch. Choose Blank page or one of the presets (Lead Magnet, Webinar Registration, SaaS Product, Coming Soon, Book a Call), then Use template. A template just seeds the canvas with blocks; everything stays editable.
2. Name it The title field sits in the editor's top bar. It's required — saving without one says Give the page a title. The title also generates the page's URL slug.
3. Add blocks The Blocks palette runs down the left. Click one to append it to the canvas.
4. Arrange them Drag a block up or down the canvas to reorder. Click a block to select it — the right panel becomes its config. The trash icon on a block removes it.
5. Configure the page Settings in the top bar swaps the right panel to page-level options: theme colour, SEO, capture entity, thank-you URL and funnel placement.
6. Save or publish Save keeps it as a draft. Publish saves and takes it live in one press. Both return you to the Pages list.

An empty canvas prompts Add blocks from the left to build your page. With nothing selected the right panel reads Select a block to edit it.

The blocks

Most blocks also take a Section background colour, which paints a full-width band behind them; Clear puts it back to none.

Page settings

The panel also shows the page's URL slug and current status once it has been saved at least once.

Publishing and the public URL

A page is Draft until you publish it. Publishing needs the Publish pages permission — without it the button simply isn't there.

1. Publish Either Publish in the editor's top bar, or the globe icon on the row in the Pages list. The status chip flips to Published.
2. Get the link The copy icon next to a page's URL is Copy public URL. The external-link icon (published pages only) is Open public page.
3. Share it The URL is a first-party address on your own workspace domain, in the shape /__public/page/<workspace>/<page-slug>. Put it in an ad, an email or a QR code.
4. Take it down Unpublish returns the page to draft. The public URL stops resolving immediately.

The published page is a self-contained HTML document — no app shell, no login. A draft or unpublished page answers Not found at the same URL, so the safest way to check your work is to publish, open the public link, and unpublish again if it isn't ready.

Capturing leads from the form

Add a Form block, then in its config give the block a heading, a Submit button label, and one row per field under Fields. Each field has a label, a type (text, email, tel, textarea, select) and a Required tick.

Once the page has a capture entity, each field also gets a mapping dropdown: Map to the entity field it should fill, or Don't map to a field. Mapping is what makes the created record readable rather than a bag of anonymous answers — set it deliberately for anything you intend to filter or segment on later.

When someone submits, four things happen in one go:

• The submission is stored and appears under Submissions with the contact, the submitted data, the page and the date.
• A record is created on the capture entity. The Submissions row marks it with a Record tick when one was created.
• A conversion signal fires for that contact, which is what enrols them into engagement-triggered journeys and reports the conversion back to your ad platforms.
• The visitor is redirected — to the Thank-you URL if you set one, otherwise to the next step of the funnel if the page is in one.

Funnels

A funnel is an ordered sequence of pages: submitting the form on one step sends the visitor to the next.

1. Create the funnel Funnels tab → type a Funnel name → Add.
2. Add steps Use Add a page as the next step… on the funnel. Only pages not already assigned to a funnel appear; with none free you get No unassigned pages — create one first.
3. Order them Reorder with the arrows. You can also set Funnel and Step order from a page's own Settings panel.

The advance only jumps to published later steps, and a page's explicit thank-you URL always wins over the funnel hop. Deleting a funnel unassigns its pages rather than deleting them.

What's actually measured

The Analytics tab is one row per page with four columns: Title, Views, Submissions and Conversion. Conversion is submissions divided by views, as a percentage.

That's the whole model — page-level counts, no per-visitor session tracking and no time-range picker on this screen. Every load counts, including your own, so open a fresh page a dozen times while testing and the conversion rate will look terrible until real traffic arrives.

What a page open does elsewhere

• Retargeting — because the URL is first-party, opening it is a tracked open on a link you own. Those opens are selectable as a source when you build a retargeting audience, with no arbitrary URL field to fill in. See Audiences.
• Journeys — a submission's conversion signal enrols the contact into journeys triggered on engagement. See Omni Marketing.
• Ad platforms — the same conversion is uploaded to the ad accounts you've connected. Connecting them is covered in Integrations.
• Audiences — the created record is a normal record, so any shared audience built on that entity picks the contact up on its next resolve.

End to end — ad, page, capture, journey — is walked through in Campaign lifecycle.

Who can do what

Opening the app needs access to Landing Pages. Two further permissions are granted per role under Settings → Module Access. Admins pass everything.

The buttons are hidden or disabled in the app and the server refuses the action, so the split is real rather than cosmetic. Background on the two permission systems is in Permissions & access.

When something goes wrong