Landing pages: hosted pages for campaigns and opt-in links

Landing pages in Arino One are hosted pages, built with a drag-and-drop block editor or drafted with AI, published at a short /p/<slug> address on your instance — a destination to send customers to from an opt-out link, a QR scan or a campaign call-to-action without setting up separate web hosting.

What they're for

A campaign or automation often needs somewhere to send a click that isn't a chat message — a form to capture more detail, a page explaining a promotion, a confirmation after an opt-in scan. Landing pages fill that gap directly inside the platform: build the page, publish it, and use its address as the link in a template, a short link, or a QR code, all without provisioning a separate site.

Listing and creating pages

Marketing → Landing pages lists every hosted page with its name, address, status, and 30-day performance — views, unique visitors and clicks — at a glance. From there:

• New page opens a blank draft in the block editor.
• Create with AI (shown only when AI is usable on the workspace) opens a prompt box; describe the page and a first draft — name, address, SEO fields and a starting set of blocks — is generated and opened directly in the editor for review.

The block editor

The editor is a drag-and-drop list of blocks with a live preview alongside, built on the same renderer that serves the public page, so nothing changes in appearance between editing and publishing. Available block types:

Alongside the blocks, set the page name, its address (slug), and a theme. SEO title and description are separate fields used for the page's browser title and any link preview, and if left blank fall back sensibly to the page name.

Draft, publish, and why they're separate

Saving a landing page only writes the draft — it never publishes on its own. Publishing is a distinct, explicit action taken once you're happy with the content. This split exists so a page can be built over several sessions, shared internally for review, or left half-finished without any risk of a customer reaching it: the public route at /p/<slug> only serves pages with status published, and anything else — including a page that was once published and reverted to draft — reads back as not found.

Branding

Anything a page leaves unset — logo, primary colour, general look — falls back automatically to your workspace's brand kit. This means a page built quickly still looks consistent with the rest of your customer-facing content, and a client's branding update to the brand kit flows through to every landing page that doesn't override it.

Analytics

Each page tracks views, unique visitors and clicks over a rolling 30-day window, visible both in the page list and on the individual page. Use these numbers as a basic health check: a page with views but no clicks suggests the call-to-action or copy needs work; a page with almost no views suggests the link driving traffic to it needs attention instead.

Where landing pages fit with the rest of the platform

Landing pages are commonly the destination at the end of another Arino One flow rather than a standalone destination:

• An opt-out or preference link in a campaign message can point to a landing page instead of a plain unsubscribe confirmation.
• A QR code — see QR opt-in — can lead to a landing page that explains what scanning does and captures consent.
• A [short link](/docs/guides/link-shortener-and-tracking) used inside a WhatsApp or SMS campaign can resolve to a landing page, giving you click tracking on top of the page's own view analytics.
• [Journeys](/docs/guides/journeys) that install a lifecycle sequence sometimes reference a landing page as a step, such as a survey or confirmation screen.

Costs

Building and publishing landing pages carries no separate fee beyond the standard $50/month Arino Core connection and management fee, which covers the platform tooling. AI-drafted pages are metered per the AI provider configured for the workspace — managed or bring-your-own key — with no Arino markup; see AI and API keys and billing and plans for current detail.

Steps at a glance

1. Open Landing pagesGo to Marketing → Landing pages. The page is gated by the landing_pages feature switch, turned on in Settings → Workspace → Marketing.
2. Start a new pageClick New page for a blank draft, or Create with AI to describe the page you want and have a first draft — content, layout and blocks — generated for review.
3. Build with blocksIn the editor, add and reorder blocks — heading, text, image, button, form, divider — with a live preview alongside, and set the page's theme, name and address (slug).
4. Set SEO fieldsFill in the SEO title and description so the page has a sensible title and preview when shared or indexed.
5. Save as a draftSaving never publishes on its own — the page stays private at draft status until you take the separate publish action, so nothing goes live half-finished.
6. PublishWhen the page is ready, publish it explicitly. It then becomes reachable at its public address and picks up your workspace's brand kit for anything the page itself leaves blank.
7. Track performanceReturn to the page to see views, unique visitors and clicks over the last 30 days, and use those numbers to judge whether the page is doing its job before pointing more traffic at it.

Frequently asked