Overview
Landing pages in CX Platform are the web pages your recipients land on when they click a link in one of your communications. They're the bridge between an email or SMS and a richer, browser-based view — whether that's a digital version of a letter, a secure login screen, or a confirmation page.
Every CX Platform tenant ships with a set of global landing pages that cover the most common scenarios out of the box. You don't need to do anything to use them — they're already there, doing their job. But when you need something more branded, more specific, or tied to a particular Application, you can build a custom landing page that overrides the global default.
This guide walks you through the two main use cases you'll come across, and the reserved codes that tell CX Platform which page to use, when.
Digital versions of correspondence
The first and most common use case is hosting a digital version of a piece of correspondence. When you send an email containing a statement, letter, or notification, the recipient often clicks through to view the full document in their browser — and that view is a landing page.
Each Application can have its own custom landing page that wraps the correspondence in your branding, layout, and any supporting content you want around it. Think of it as the web equivalent of letterhead and envelope — it gives the document context, makes it feel like part of your brand, and gives you room to add things like help links, contact details, or related actions.
Because the landing page sits at the Application level, you can have different looks for different communication types. Your monthly statement Application might use a clean, data-focused page, while a welcome-series Application might use something warmer and more visual.
Override global pages for login and authentication
The second use case is overriding the global landing pages that CX Platform uses for system-level events — things like prompting a recipient to log in before viewing secure content, showing a page when archived content is requested, or confirming an unsubscribe.
These pages exist by default, so most teams never need to touch them. But if you want the login prompt for a particular Application to match the look of that Application's correspondence — same logo, same colours, same tone — you can build a custom landing page using a reserved code. CX Platform recognises the code and uses your custom page instead of the global one, automatically.
Heads up
Reserved codes only work when used at the Application level. If a reserved code isn't found in the Application, CX Platform falls back to the global landing page — so you can override only the pages you need to, and leave the rest as they are.
Reserved landing page codes
The codes below are the ones CX Platform watches for. To override a global page, create a landing page in your Application and give it the matching code.
What's next
Now that you've got the use cases mapped out, the next step is building the landing pages themselves. Each Application has its own Templates section where you can create, edit, and assign landing pages (Online) — including ones that use the reserved codes above.