Overview
Landing pages are the secure, online destination for your communications — typically linked from an email or SMS so recipients can view a richer, more interactive version of their message. Think personalised statements, account summaries, or any content that's too sensitive to send in full over email.
When you open a landing page template, you'll see three tabs across the top: Content, Images / Resources, and Settings. Content is where you design the page itself — using the same Visual Editor and Advanced HTML Editor you already know from building email templates. Settings is where you configure how the page behaves, and it's what this guide covers.
There are two cards to work through: Basic Settings (giving your landing page an identifier so you can link to it) and Authentication (deciding whether viewers need to log in first).
Add a new landing page template
Every landing page starts life in the Add new channel template modal. This is where you tell the platform what kind of template you're creating, pick a design tool, and give it a code so it can be linked from elsewhere. If you haven't done this already you can learn how to do it here - Add a new draft landing page.
You'll set three things:
Channel — for a landing page, leave this as Online. (Other channels like Email, SMS, and Print sit alongside, but they're handled in their own templates.)
Type — choose the design tool you want to use. Simple - Visual Email/HTML design opens the drag-and-drop Visual Editor, the same one you'll be familiar with from building emails. If you'd rather hand-code, the Advanced HTML option is there too.
Code — a unique name that identifies this landing page so other templates can link to it. For most custom pages you can use anything that makes sense to you, like OnlineStatement or WelcomeOnline.
Reserved codes for system-wide pages
Three codes have special meaning. Use them and your template will replace the platform's default page for that scenario:
- login — the login page shown when authentication is required.
- archived — the page shown when the underlying data has been archived.
- unsubscribe — the confirmation page shown after someone unsubscribes.
If you're building a custom page, steer clear of these three so you don't accidentally override a system default.
Basic Settings
This is where you give your landing page an identity. The Code is the most important field — it's a unique name that lets you reference and link to this landing page from elsewhere, like an email template that includes a "View online version" link.
The Description is optional, but worth filling in if you're working in a team. It's purely for internal reference and helps anyone else opening the template understand what it's for at a glance.
That's it — your landing page now has a unique identifier you can reference from any other template that needs to link to it.
Authentication
Authentication controls whether someone needs to log in before they can view your landing page. If the content is sensitive — personal statements, account details, anything you wouldn't want shared with the wrong person — this is the setting that protects it.
Tick the box and any recipient clicking through to this landing page will be prompted to log in first. Leave it unticked and the page is open to anyone with the link.
Where the authentication fields live
The fields recipients actually enter when logging in (like surname and date of birth) aren't set here in the template settings — they're configured at the Application level. Head to your Application's Security / data retention tab and tick the fields you want to use under Authentication Fields. Whatever you select there becomes the login prompt for any authenticated landing page in this Application. You'll still need to add the input fields and HTML to your template. This is covered in the Add an Authentication Layer guide.
To enable authentication on a landing page:
- On your landing page template, click the Settings tab.
- In the Authentication card, tick the Require authentication to view checkbox.
- Scroll to the bottom of the page and click Save.
Your landing page is now protected. Anyone clicking through from an email or SMS will be asked to log in using the authentication fields you've set at the Application level before they can see the content.
What's next
Once your settings are sorted, jump back to the Content tab to design the page itself — the editors work the same way as your email templates, so you can drag in blocks, drop in personalisation tokens, and preview as you go. And if you're new to authentication, it's worth taking a quick look at the Security / data retention tab on your Application to confirm your authentication fields are configured the way you want them.