The Landing Page request requires a title, slug, and block array. The server validates the page before saving. If the submission contains invalid information, PROS returns validation errors so the affected fields can be corrected.
Use Save draft when the page is not ready for public distribution. Draft mode is appropriate for internal review, copy editing, design work, link testing, or waiting for campaign approval.
Use Publish when the page is ready for public visitors. Publishing stores the published status and the application records a publication timestamp for the page.
Important: A public Landing Page route only serves pages whose status is published. Confirm publication before distributing the URL.
Open an existing Landing Page from the listing and use Update after making changes. Recheck the page status whenever you edit a live page so you do not unintentionally leave it in the wrong state.
The Landing Page save workflow can generate a matching Short Link when requested and when no Short Link is already attached. The generated Short Link points to the public Landing Page URL and is tagged for its Landing Page source.
A linked Short Link provides a compact address for email, SMS, social posts, print materials, or other digital distribution.
The save workflow can also generate a matching QR Code that points to the public Landing Page. This allows the same page to be distributed through printed or physical materials without creating a separate destination manually.
The Landing Page request also accepts an existing Short Link ID and QR Code ID. Use existing relationships when the campaign already has the appropriate asset and you want the page associated with it rather than generating a new one.
The Landing Page listing provides management actions for saved pages. Source-confirmed actions include:
The listing also identifies whether a page is Published or Draft and can display view-related analytics summaries.
Use the public/open action to inspect the published experience. Check the page as a visitor would see it rather than relying only on the builder preview.
Use the Analytics action to review activity associated with the page. Public Landing Page views are tracked as landing_page_view events and can contribute to PROS Analytics.
A major advantage of a managed Landing Page is that you can update content without creating a completely different campaign destination, provided you keep the same published slug.
Caution: When editing a live page, test the updated page immediately after saving because visitors may see the changes as soon as the published version is available.
The Landing Page listing includes a delete action for authorized users. The controller explicitly prevents users with the editor role from deleting Landing Pages.
Delete only when the page is no longer needed. If a public page has been widely distributed, consider the effect on existing links and QR Codes before removing it.
Access to Landing Page operations depends on workspace permissions. A user may be able to edit content while lacking permission for destructive actions. If an expected action is missing or blocked, review the user role and permissions.