Design static landing pages

Although landing pages has its advantages, it cannot be accessed via a URL. From version 12.1.5, you can use Deliver to assign and publish landing pages as static landing pages.

A static landing page has its own URL making it accessible directly without having to embed it an email built using Message Editor or Quick Builder.Upon publishing the landing page as a static landing page, you can share the URL via Email (by embedding the URL using Message Editor or Quick Builder), SMS, or WhatsApp communication.

Creating static landing pages is similar to creating landing pages. For the procedure, see Design landing pages via Quick Builder. The only difference is that within the View properties panel, you must select Enable landing page access via static URL.When you select Enable landing page access via static URL, a Domain dropdown box appears. Select the domain in which you want to publish the static landing page.

Since static landing pages can be accessed by everyone, you cannot customize it to include personalization fields. The following are some scenarios related to creation of static landing pages or changing existing landing pages to static landing pages:


Created a new landing page	Ensure that you Enable landing page access via static URL within the View properties section and do not add any personalization fields in the landing page.
Created a new landing page with personalization fields.	Remove all personalization fields and Enable landing page access via static URL within the View properties section.
Editing existing landing page without personalization fields	Ensure that you Enable landing page access via static URL within the View properties section and do not add any personalization fields in the landing page.
Editing existing landing page with personalization fields	Remove all personalization fields and Enable landing page access via static URL within the View properties section.

As a best practice, when you are creating a new landing page, decide whether you are creating a normal landing or a static landing page. If you are creating a static landing page, select the Enable landing page access via static URL within the View properties section before you add any components. If you select Enable landing page access via static URL at the beginning, you cannot add any personalization field in the components. If you select Enable landing page access via static URL after creating the landing page, you have to remove all personalization fields from all components before you save and publish the static landing page.

In case of existing landing pages with personalization fields, if you want to convert it to static landing pages, check the following components to remove personalization fields (if it exists in those components):

Text with custom fields
Text with custom links
Text with custome rules
Textarea with default value
Input label with default value
Button with links
Images with links

You can add a submit form in static Landing Page. On submission of this form, data is captured by RCT and data is sent to UCC_RESPONSE and UCC_RESPONSEATTR tables.

Just like in landing pages, where you can link one landing page to another, in case of static landing pages, you can link a link a static landing page only to another static landing page.

A static landing page will not work if you do not publish the page in the domain. Ensure that you Save & Publish the page after creating the static landing page to get the static landing page URL to access it.

After publishing, a static landing page can be accessed in the following ways:

Using direct URL provided by Deliver. In this case response is associated with landing page key and it does not contain any container/envelope/audience association.
If landing page is included in an email and sent to customer, it will behave as a regular landing page and user can associate it with a mailing and contact/audience based on data in UCC_Response table.

With the static landing page URL, you can get useful information like customer account name and landing page name.